I have just upgraded our ZenOSS Core installation from 2.3.3 to 2.4.2 and am
having a number of problems that I have worked through but have a couple of
problems remaining. The zenactions daemon won't start up. When I try to start
it by hand, I get the following:
-bash-3.2$ zenactions run
DEBUG:zen.ZenActions:action:remedy-70-89-filesystems for:sapbasis loaded
DEBUG:zen.ZenActions:action:remedy-90-100-filesystems for:sapbasis loaded
DEBUG:zen.ZenActions:action:production-email for:sapbasis loaded
DEBUG:zen.ZenActions:action:productionEmail for:serverteam loaded
DEBUG:zen.ZenActions:action:sms-filesystems-prod for:sms loaded
DEBUG:zen.ZenActions:action:production for:unixteam loaded
DEBUG:zen.ZenActions:action:monitors for:unixteam loaded
DEBUG:zen.ZenActions:action:testdev for:unixteam loaded
DEBUG:zen.ZenActions:action:workstations for:unixteam loaded
DEBUG:zen.ZenActions:action:productionEmail for:unixteam loaded
DEBUG:zen.ZenActions:action:testdevEmail for:unixteam loaded
DEBUG:zen.ZenActions:action:workstationEmail for:unixteam loaded
DEBUG:zen.ZenActions:action:wellviewProdEmail for:unixteam loaded
DEBUG:zen.Events:Found device localhost and adding device-specific rules
DEBUG:zen.Relations:checking relation: location
DEBUG:zen.Relations:checking relation: deviceClass
DEBUG:zen.Events:EventClassInst=Start
DEBUG:zen.DbConnectionPool:Creating a new connection; Pool size: 0
DEBUG:zen.Events:update status set clearid =
'4306b0ff-718f-4df4-9eef-763be7949f3d' where device='localhost' and
component='zenactions' and eventKey='' and (eventClass='/App/Stop' or
eventClass='/App/Start'): --> 0
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
DEBUG:zen.DbConnectionPool:Retrieved a connection; Pool size: 0
DEBUG:zen.DbConnectionPool:Returned a connection; Pool size: 1
Traceback (most recent call last):
File "/opt/zenoss/Products/ZenEvents/zenactions.py", line 672, in ?
za.run()
File "/opt/zenoss/Products/ZenEvents/zenactions.py", line 513, in run
self.schedule.run()
File "/opt/zenoss/Products/ZenEvents/Schedule.py", line 94, in run
self.runEvents()
File "/opt/zenoss/Products/ZenEvents/Schedule.py", line 123, in runEvents
work = self.makeWorkList(now, self.workList)
File "/opt/zenoss/Products/ZenEvents/Schedule.py", line 97, in makeWorkList
work = [(mw.nextEvent(now), mw) for mw in workList]
File "/opt/zenoss/Products/ZenModel/MaintenanceWindow.py", line 282, in
nextEvent
return self.adjustDST(self.started + self.duration * 60 - 1)
File "/opt/zenoss/Products/ZenModel/MaintenanceWindow.py", line 540, in
adjustDST
resultTime = time.localtime(result)
ValueError: timestamp out of range for platform time_t
The zenactions worked fine in the version I am upgrading from. I have tried
setting the server to use the UTC time zone to see if I can at least get it
started. Right now I can't go into the alerting rules to look at anything in
the GUI since the web interface fails when I click on the Users tab under the
Settings (this is my second problem). I thought maybe the two problems were
related in some way. Any advice on how to troubleshoot further? Has anyone
else seen this?
Thanks.
-------------------- m2f --------------------
Read this topic online here:
http://forums.zenoss.com/viewtopic.php?p=37631#37631
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
