On 4/25/07, MoreDakka <[EMAIL PROTECTED]> wrote:
Well I've got the two templates that I need for monitoring:

 check_http - /usr/local/zenoss/libexec/check_http -I ${dev/manageIp} -e 
"HTTP/1"
check_tcp - /usr/local/zenoss/libexec/check_tcp ${dev/manageIp} -p 23

However if I force a machine off the network these do not generate any errors.  I've 
tried to run "zenmodeler run -v 10" but no good, no change.  I've left the 
system up for 48+ hours then brought it down and no change in the events on that machine. 
 Here is what I have set for each of them:

Name    check_http
Source Type     COMMAND
Enabled         True
Use SSH         False
Component
Event Class     /Net
Event Key       check_http
Severity        Critical
Cycle Time      60
Command Template:
/usr/local/zenoss/libexec/check_http -I ${dev/manageIp} -e "HTTP/1"


Name    check_tcp 23
Source Type     COMMAND
Enabled         True
Use SSH         False
Component
Event Class     /Cmd/Fail
Event Key       check_tcp
Severity        Critical
Cycle Time      60
Command Template
/usr/local/zenoss/libexec/check_tcp ${dev/manageIp} -p 23


These Performance Templates are under "/Devices/Custom Monitoring/http - 
telnet/PerfConf/Device/"
And I have Four devices that these should be checking on, under each device's 
PerfConf there is:

 RRDTemplate @ /Devices/Custom Monitoring/http - telnet
Template for checking if http and telnet is up

DataSources     Name      Source        Source Type     Enabled
check_http      /usr/local/zenoss/libexec/check_http -I ${dev/manageIp} -e 
"HTTP/1"     COMMAND         True
check_tcp 23    /usr/local/zenoss/libexec/check_tcp ${dev/manageIp} -p 23       
COMMAND         True

(hope that makes sense)

So I'm not sure what I'm missing or what I've done wrong that this isn't 
working.

Thanks again to all that have helped me so far and to those that will hopefully 
be able to help me now.

Josh,

At first glance, it looks like you've done everything correctly. Your
next step should be to look in your $ZENHOME/log/zencommand.log file
to see if anything jumps out at you. If nothing in there looks
suspicious, run "zencommand run -v 10" from the command line as the
zenoss user to run it in the foreground with verbose logging. This
will almost surely give you some useful information.

--
Chet Luther
[EMAIL PROTECTED]
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to