|
|
| Subject: | Device status of "UP" is inaccurate |
| Author: | [Not Specified] |
| Posted: | 2016-11-19 13:27 |
Hello everyone,
Our team conducted routine maintenance on our servers and we noticed that Zenoss never sent a notification when a specific server was down once we would reboot. We intentionally shut some servers down and have the same issue. I've used the ping and snmpwalk commands, which fail of course, but the device status is still listed as UP. There was another post in the community where someone had a similar issue and seemed to have been able to find the fix (http://www.zenoss.org/forum/4231). It states that the issue may have something to do with an IP address being changed which could have broken something within RabbitMQ. A link to a solution was posted ( http://community.zenoss.org/message/71139#71139 ), but the page is no longer available.
If someone could help me pinpoint this issue I'd appreciate it greatly.
Thanks
| Subject: | Hello |
| Author: | [Not Specified] |
| Posted: | 2016-11-20 03:02 |
Please check in the configuration properties if the zPingMonitorIgnore is set to True.
| Subject: | With a zillion thanks to Jan |
| Author: | Jane Curry |
| Posted: | 2016-12-02 06:57 |
With a zillion thanks to Jan Garaj, you can access this message at http://monitoringartist.github.io/community.zenoss.org/message/71139.html
Cheers,
Jane
Email: jane.curry@skills-1st.co.uk Web: https://www.skills-1st.co.uk
| Subject: | Hey guys, |
| Author: | [Not Specified] |
| Posted: | 2016-12-02 10:12 |
Hey guys,
Thanks for your input. I found the solution a little while ago. Apparently it was an issue where our zenoss server did not have permission to perform ping operations. We received alerts when a server went down a few months ago, so I don't know what could've happened to cause the issue. Anywho, I ran the following commands as root user which cleared up the issue:
chown -c root:zenoss /opt/zenoss/bin/pyraw
chown -c root:zenoss /opt/zenoss/bin/zensocket
chown -c root:zenoss /opt/zenoss/bin/nmap
chmod -c 04750 /opt/zenoss/bin/pyraw
chmod -c 04750 /opt/zenoss/bin/zensocket
chmod -c 04750 /opt/zenoss/bin/nmap
Link to post with solution: https://openavenzer.wordpress.com/2014/10/01/nmap-error-with-zenping/
| < |
Previous Predictive TH for DataPoint=FreeMegaBytes_FreeMegabytes |
Next Avamar Transform not matching severity |
> |