so if I understand correctly, you just want to know if the socket is in a LISTEN state, but you don't want to actually connect to it? You can certainly do that by setting zenoss to run a script that sshs into the host and runs a netstat -an |grep LISTEN |grep $PORT, but I would suggest against this as it won't catch a multitude of issues. The problem is rarely one of "is the port open" and is usually "is the service functioning". It's rare on my hosts for example for apache to go down and close out port 80, but getting overloaded and taking 30 seconds to respond to a port open request, now that's becoming increasingly common.
On 12/19/07, jim <[EMAIL PROTECTED]> wrote: > > Hi, i want to monitor several listening sockets on a host. Normally i > would use a service rule in Zenoss and monitor the availability of the given > sockets. > > However, this involves opening and closing of a TCP connection to the > sockets which should be monitored. Is there a host only solution which > checks ie. the output of nmap, greps for LISTENING sockets and sends the > results to Zenoss? > > Advantage would be that no socket connetion to the service is made. > > > > > -------------------- m2f -------------------- > > Read this topic online here: > http://community.zenoss.com/forums/viewtopic.php?p=14512#14512 > > -------------------- m2f -------------------- > > > > _______________________________________________ > zenoss-users mailing list > [email protected] > http://lists.zenoss.org/mailman/listinfo/zenoss-users > -- Jason Luck favors the prepared.
_______________________________________________ zenoss-users mailing list [email protected] http://lists.zenoss.org/mailman/listinfo/zenoss-users
