I followed the example in the admin guide to create an event command that
simply echoes event details to a file in /tmp, and this works. I then created
and tested a script that uses winexe to (optionally kill and then) start a
Windows service. This script works fine as the zenoss user when I run it
manually. However, when I generate an event in Zenoss to get it to run, it
immediately logs the following event:
(at 2007/10/26 08:37:11.000) Timeout running: Generic Windows service start:
command timed out
The thing is, it is executing the script just fine, but it is doing it two
minutes later. I added logging to the script to write to a log file the time it
is executing. The script logging is reporting:
[2007-10-26T08-39-11] zenoss-win-svc-restart: Starting service W3SVC on device
172.17.9.9
I have the following settings on the event command. Any idea why it is doing
this? Do I need to set up the command as a background task?
Default command timeout: 180
Delay (secs): 0
Repeat Time (secs): 0
Command: /usr/local/bin/zenoss-win-svc-restart "${dev/zWinUser}"
"${dev/zWinPassword}" ${dev/manageIp} 1 "${evt/component}"
-------------------- m2f --------------------
Read this topic online here:
http://community.zenoss.com/forums/viewtopic.php?p=12330#12330
-------------------- m2f --------------------
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
