Erik,
Thanks for your suggestions.
> First problem is because you don't have a good WMI connection to the
> remote box (authentication is bad). Use wbemtest.exe to test out
> your WMI connection.
I've run wbemtest, and it seems to connect ok. I'm able to view classes such as
"Win32_process". I did not have to provide any authentication for this. I'm
currently logged into Windows as a domain user that has local admin privs. I
agree with you that I'm having WMI issues, but I can't pinpoint it any further
than that. Any help is appreciated on this.
> Second is that you don't have SNMP-Informant installed on the windows
> box.
I've had SNMP Informant (v1.4 standard) installed on this box for a while now.
I just tried reinstalling SNMP Informant with all the SNMP & WMI services
running, but still get the same WMI errors when running the zen*.py commands
afterwards. I've not installed any mibs included w/ Informant, but that
wouldn't cause the WMI errors, would it?
C:\TEMP\Downloads\Zenoss\zenoss-1.0.1-x86\zenwin-1.0.1>python zenwin.py -C etc\z
enwin.cfg
INFO:zen.zenwin:reloading configuration
INFO:zen.SendEvent:SendEvent thread started.
WARNING:zen.StatusTest:MYNODE1 wmi connection failed: User credentials cannot
be used for local connections
WARNING:zen.StatusTest:MYNODE2 wmi connection failed: Access denied
INFO:zen.zenwin:Com InterfaceCount: 6
INFO:zen.zenwin:Com GatewayCount: 0
INFO:zen.zenwin:tested 2 devices in 7.03 seconds
INFO:zen.zenwin:stopping...
INFO:zen.SendEvent:SendEvent thread ended.
---------------------------------------------
Much appreciated,
Derek.
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Erik A. Dahl
Sent: Wednesday, December 06, 2006 6:38 AM
To: General discussion of using zenoss system
Subject: Re: [zenoss-users] zenwin on win xp
First problem is because you don't have a good WMI connection to the
remote box (authentication is bad). Use wbemtest.exe to test out
your WMI connection.
Second is that you don't have SNMP-Informant installed on the windows
box.
-EAD
On Nov 29, 2006, at 12:38 PM, Derek Pham wrote:
> Hi,
> I've loaded Zenoss & ZenWin 1.0.1, and things seem to be working
> better. However, I'm getting this message when running the
> "zeneventlog.py" program:
>
> C:\TEMP\Downloads\Zenoss\zenoss-1.0.1-x86\zenwin-1.0.1>python
> zeneventlog.py -C etc\zeneventlog.cfg
> INFO:zen.zeneventlog:reloading configuration
> INFO:zen.SendEvent:SendEvent thread started.
> ERROR:zen.zeneventlog:wmi connect failed on MYNODE
> Traceback (most recent call last):
> File "zeneventlog.py", line 64, in loadConfig
> self.devices[name] = self.getWatcher(name,user,passwd,sev)
> File "zeneventlog.py", line 80, in getWatcher
> return c.watcher(wql)
> File "C:\TEMP\Downloads\Zenoss\zenoss-1.0.1-x86\zenwin-1.0.1
> \wmiclient.py", li
> ne 98, in watcher
> return _watcher(self._wmi.ExecNotificationQuery(wql))
> File "<COMObject <unknown>>", line 3, in ExecNotificationQuery
> File "C:\Python24\Lib\site-packages\win32com\client\dynamic.py",
> line 258, in
> _ApplyTypes_
> result = self._oleobj_.InvokeTypes(*(dispid, LCID, wFlags,
> retType, argTypes
> ) + args)
> com_error: (-2147352567, 'Exception occurred.', (0,
> 'SWbemServicesEx', 'Access d
> enied ', None, 0, -2147217405), None)
> INFO:zen.zeneventlog:Com InterfaceCount: 6
> INFO:zen.zeneventlog:Com GatewayCount: 0
> INFO:zen.zeneventlog:tested 0 devices in 0.02 seconds
> INFO:zen.zeneventlog:stopping...
> INFO:zen.SendEvent:SendEvent thread ended.
> ---------------------------------------
>
> All of the services are running on the Windows box, including WMI.
> I was able to install the zenwin services w/o errors. However, I'm
> seeing the related warnings in Zenoss about the device:
>
> memoryPagesPerSec /Perf/Snmp Error reading value for
> "memoryPagesPerSec" on MYNODE (oid .1.3.6.1.4.1.9600.1.1.2.10.0 is
> bad) 2006/11/29 08:15:34.852 2006/11/29 09:15:35.392
> 3
>
> memoryAvailableKBytes /Perf/Snmp Error reading value for
> "memoryAvailableKBytes" on MYNODE (oid .1.3.6.1.4.1.9600.1.1.2.2.0
> is bad) 2006/11/29 08:15:34.686 2006/11/29 09:15:35.380
> 3
>
> cpuPercentProcessorTime /Perf/Snmp Error reading value for
> "cpuPercentProcessorTime" on MYNODE (oid .
> 1.3.6.1.4.1.9600.1.1.5.1.5.6.95.84.111.116.97.108 is bad)
> 2006/11/29 08:15:34.372 2006/11/29 09:15:35.241 3
>
> Can someone help me explain the errors and warnings?
>
> Thanks much,
> Derek.
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:zenoss-users-
> [EMAIL PROTECTED] On Behalf Of Erik A. Dahl
> Sent: Monday, November 27, 2006 7:10 AM
> To: General discussion of using zenoss system
> Subject: Re: [zenoss-users] zenwin on win xp
>
> This will be fixed in 1.0.1 release which should post today. The
> actual problem you are having is that zenwin can't connect to the
> event server. In your cfg file set the value "zem" to point to your
> zenoss server and make sure that zenxevent is running.
>
> -EAD
>
> On Nov 27, 2006, at 6:17 AM, DAVID Thomas wrote:
>
>>
>>
>> Hi all,
>> I want to test Zenoss and Zenwin, so I run set the virtual zenoss
>> appliance on a Windows XP SP2 (French) computer. The appliance is
>> running just fine. However, I cannot get zenwin to run correctly on
>> the XP host. Each time I run one of the part of zenwin I get the
>> following messages :
>> C:\zenwin-1.0.0>python zenwin.py -C etc\zenwin.cfg
>> INFO:zen.SendEvent:SendEvent thread started.
>> INFO:zen.zenwin:reloading configuration
>> WARNING:zen.StatusTest:wmi connection failed: AccÞs refusÚ. (Access
>> denied)
>> Exception in thread Thread-1:
>> Traceback (most recent call last):
>> File "C:\Python24\lib\threading.py", line 442, in __bootstrap
>> self.run()
>> File "D:\zenwin-1.0.0\zenutils\SendEvent.py", line 53, in run
>> File "D:\zenwin-1.0.0\zenutils\SendEvent.py", line 66, in
>> _sendEvents
>> NameError: global name 'socket' is not defined
>>
>> INFO:zen.zenwin:Com InterfaceCount: 6
>> INFO:zen.zenwin:Com GatewayCount: 0
>> INFO:zen.zenwin:tested 1 devices in 2.00 seconds
>> INFO:zen.zenwin:stopping...
>>
>> As it was suggested in some previous messages, I did not get any
>> error messages running the following command:
>>
>> C:\zenwin-1.0.0>python
>> Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit
>> (Intel)] on win32
>> Type "help", "copyright", "credits" or "license" for more
>> information.
>>>>> import socket
>>>>>
>>
>> Python install is 2.4.4 and pywin32-210.win32-py2.4.exe for Python
>> extension.
>>
>> Did someone managed to get zenwin working on Windows XP SP2 ? Does
>> someone has any clue to get it working on Windows XP (or why it's
>> not working)?
>>
>> BTW, I test zenwin with no more luck on another Windows XP SP2
>> (English) wich is already used by a VBS script for inventory. The
>> VBS script uses WMI to get information from remote host, which
>> should mean WMI is working fine on this particular host. The VBS
>> script is name winventory (http://winventory.sf.net/)
>>
>> Thomas
>>
>>
>> ICADE s'est dotée d'une nouvelle messagerie et mon ancienne adresse
>> E-mail a pu être modifiée. Si tel est le cas, merci de mettre à
>> jour vos listes de diffusion et/ou contacts.
>>
>> Ce message et toutes les pièces jointes sont confidentiels et
>> établis à l'attention exclusive de ses destinataires.
>> Toute utilisation de ce message non conforme à sa destination,
>> toute diffusion ou toute publication, totale ou partielle,est
>> interdite, sauf
>> autorisation expresse.
>> Si vous recevez ce message par erreur, merci de le détruire et d'en
>> avertir
>> immédiatement l'expéditeur.
>> La Societe ICADE, ses filiales et ses partenaires déclinent toute
>> responsabilité au titre de ce message s'il a été altéré,déformé ou
>> falsifié.
>>
>> This message and all attachments are confidential and intended
>> solely for the addressees.
>> Any use not in accord with its purpose, any dissemination or
>> disclosure, either whole or partial, is prohibited except formal
>> approval.
>> If you receive this message in error, please delete it and
>> immediately notify the sender.
>> Neither ICADE company nor any of its subsidiaries or affiliates
>> shall be liable for the message if altered, changed or falsified.
>> ------------------------
>> _______________________________________________
>> zenoss-users mailing list
>> [email protected]
>> http://lists.zenoss.org/mailman/listinfo/zenoss-users
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
>
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
