TECHZEN Zenoss User Community ARCHIVE  

Cycle times not being used

Subject: Cycle times not being used
Author: Joan
Posted: 2016-04-20 08:43

I have a custom python script that is being run by zencommand every 300 seconds, it replaces ping in some hosts that are over a slow line (to minimize traffic)

CTO

GoVanguard Inc.

sscott@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard


Subject: It's a homemade script that
Author: Joan
Posted: 2016-04-21 06:27

It's a homemade script that checks for icmp connectivty after a certain time, (depends on several conditions).
At the end, I finnish the script returning one of the classical nagios values (2 when ther is an error)

    if estat == "OK":
print "Exit 0 OK | Up=2\n"
sys.exit(0)
elif estat == "CRIT":
print "Exit 2 CRIT | Up=0\n"
sys.exit(2)

The problem is that the event is not updated every 300 seconds as I would expect, to fix the wrong state, I use one of these ways:

- Close the event and wait for an automated recheck

- Call the event from the zenoss server with "zencommand run -v 10 --device=devicename --showfullcommand"



< Previous
Ran out of space on / and now Zenoss won't start.
  Next
Startup issues after 5.1.1 upgrade
>