I turned the ssh ip service monitor state to 'true' because we need
to monitor that, but noticed that it zenoss hadn't registered sshd
as active on any of the hosts in the environment yet in the first
place. This is when other services like smtp and snmp were detected
but set to 'false'.
I've verified that there is both an sshd process active and a
listing in netstat about it listening on port 22, plus tested a
telnet to the port to make sure the regex was matching the expected
return from the connection.
What's going on? why isn't this picking up properly?
This probably has to do with sshd listening on :::22 instead of the
old IPv4 0.0.0.0:22. Net-SNMP doesn't report on these ports through
the old TCP MIB that Zenoss uses to model devices. Here's another
topic that goes into more detail on the issue: http://community.zenoss.com/forums/viewtopic.php?p=14262
We have an open ticket on the issue as well:
http://dev.zenoss.org/trac/ticket/2486
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users
