Hi,
Its a bug in 2.0.1 version. It missing two files. you need to copy it
manually.
Download a source version and extract it.
Then copy the files (pywintypes.py and pythoncom.py) from source directory
to your installation directory.
For me it is in /tmp/zenoss-2.0.1/build/wmi-0.1.2/pycom/
and copy to /usr/local/zenoss/lib/python/
On 7/5/07, Baird, Josh <[EMAIL PROTECTED]> wrote:
I just performed a RPM upgrade from 2.0 to 2.0.1, but I forgot to stop
the daemons before I installed the new RPM. So, the migration/upgrade
script was triggered when I "stop'd" the services. This has resulted in
zenwin/zenwinmodelor/zeneventlog not starting:
[EMAIL PROTECTED]:~/src$ /etc/rc.d/init.d/zenoss start
Daemon: zeoctl . daemon process started, pid=23610
Daemon: zopectl . daemon process started, pid=23614
Daemon: zenhub starting...
Daemon: zenping starting...
Daemon: zensyslog starting...
Daemon: zenstatus starting...
Daemon: zenactions starting...
Daemon: zentrap starting...
Daemon: zenmodeler starting...
Daemon: zenperfsnmp starting...
Daemon: zencommand starting...
Daemon: zenprocess starting...
Daemon: zenwin starting...
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenWin/zenwin.py", line 18, in ?
import pythoncom
ImportError: No module named pythoncom
Daemon: zeneventlog starting...
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenWin/zeneventlog.py", line 20, in ?
import pywintypes
ImportError: No module named pywintypes
Daemon: zenwinmodeler starting...
/opt/zenoss/bin/zenoss: line 95: 23745 Segmentation fault
$ZENHOME/bin/$cmd "$FUNC"
There are no errors or anything in zenwin.log.
Here is zeneventlog's log.. but these are mostly errors from my old 2.0install
(Python
2.4):
007-07-05 13:56:57 INFO zen.zeneventlog: Com InterfaceCount: 1
2007-07-05 13:56:57 INFO zen.zeneventlog: Com GatewayCount: 1
2007-07-05 13:57:57 INFO zen.zeneventlog: Com InterfaceCount: 1
2007-07-05 13:57:57 INFO zen.zeneventlog: Com GatewayCount: 1
2007-07-05 13:58:57 INFO zen.zeneventlog: Com InterfaceCount: 1
2007-07-05 13:58:57 INFO zen.zeneventlog: Com GatewayCount: 1
2007-07-05 13:59:57 INFO zen.zeneventlog: Com InterfaceCount: 1
2007-07-05 13:59:57 INFO zen.zeneventlog: Com GatewayCount: 1
2007-07-05 14:00:56 ERROR zen.zeneventlog: Error processing main loop
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenWin/WinCollector.py", line 85, in
scanCycle
self.processLoop()
File "/opt/zenoss/Products/ZenWin/zeneventlog.py", line 92, in
processLoop
lrec = w.nextEvent()
File "/opt/zenoss/Products/ZenWin/wmiclient.py", line 118, in nextEvent
return self.event.NextEvent
(timeout).Properties_("TargetInstance").Value
File "/opt/zenoss/lib/python/win32com/client.py", line 80, in NextEvent
o, = pywmi.IEnumWbemClassObject_SmartNext(self.enum, iTimeoutMs, 1)
SystemError: bad format char passed to Py_BuildValue
There are also no errors in zenwinmodelor.log..
Anybody know what could be happening?
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
--
Regards
Venkatesan .T
Tutors World Wide (I) Pvt. Ltd.
Mobile: 9444541280
Website: www.twwi.co.in
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users