![]() |
![]() |
Subject: | A very strange occurrence |
Author: | Gregg Hughes |
Posted: | 2014-08-08 15:10 |
Good afternoon, all! We just had a very strange occurrence in our datacenter. We have Nagios Core 3.2.3 and Zenoss on the same server. I was troubleshooting a problem adding devices and followed this posting. After I changed the limits in /etc/security/limits.conf, all the servers tracked in Nagios alarmed that the load was critical. After checking the actual servers and finding normal to very low loads, I figured that the change and restarting Zenoss had somehow triggered the bogus alarms in Nagios.
Has anyone ever heard of something like this happening
Thanks to all!
Gregg
Subject: | Well.. seems more like a |
Author: | Jay Stanley |
Posted: | 2014-08-13 18:58 |
Well.. seems more like a Nagios issue. I would break the servers apart if possible. We have Nagios and Zenoss servers, but keep them separated.
How are you doing Nagios monitoring Has this happened again Does restarting zenoss cause the issue again
< |
Previous Sample code to create an Event Mapping using Python |
Next Alert for Device Status up |
> |