TECHZEN Zenoss User Community ARCHIVE  

Devices not registering as down

Subject: Devices not registering as down
Author: [Not Specified]
Posted: 2015-02-26 14:32

I've got a Zenoss Core 4.2.5 (running on CentOS 6.6) installation going to do some evaluation and testing. So far there's a lot of good to report. Getting nice graphical data including some custom graphs which were very easy to create. However, there is a (big) glitch:

I discovered that when I block access to a monitored device, nothing happens. The graphs stop updating of course, but the "Device Status" still shows "Up" with the green power button icon next to it. And no event is generated when I would expect this to be Sev: Critical.

I'm simulating the monitored device going down by blocking its IP via inbound iptables. I've verified that ping and snmpwalk no longer succeed at this point. Yet despite waiting for hours (overnight) there's no change in status.

The original installation of Zenoss was done by someone else before handing it over to me. Is it possible that some basic option is misconfigured Or alternately, that the installation is broken somehow and I'd be better off starting over

Any hints appreciated!

Thanks,
Allen



Subject: Resolved!
Author: [Not Specified]
Posted: 2015-02-26 16:14

This appears to have been the usual "IP address changed and broke my RabbitMQ" issue that others have encountered.

Errors showed up in /var/log/rabbitmq, specifically ones like this:

{handshake_error,starting,0,
{amqp_error,access_refused,
"AMQPLAIN login refused: user 'zenoss' - invalid credentials",
'connection.start_ok'}}

The solution that I found pointed back to here:

http://community.zenoss.org/message/71139#71139

Problem solved and events are being processed.



Subject: AWESOME WAY TO SELF FIX!
Author: Andrew Kirch
Posted: 2015-03-05 09:33

AWESOME WAY TO SELF FIX!

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard



< Previous
Distributed collector best docs?
  Next
RESOLVED: UI throws ZODB.POSException.POSKeyError while findposkeyerror comes u ...
>