TECHZEN Zenoss User Community ARCHIVE  
FORUMS / Legacy Discussions / DISCUSSION

"Heartbeat Failure" error occurring for Zenoss components

Subject: "Heartbeat Failure" error occurring for Zenoss components
Author: [Not Specified]
Posted: 2014-01-20 01:53

Hi,

I have a question. Can somebody please answer that question

We received the "Heartbeat Failure" error for Zentrap. After analyzing the cause, we understood that conflicts in snmptrapd deamon and zentrap deamon causing this error. We understood that both snmptrapd and zentrap are trap daemon and they are listening on UDP port 162. So by disabling one trap deamon this error can be removed.

Now we are receiving the "Heartbeat Failure" for Zenping and Zensyslog. So are there any other ping deamon and syslog deamon, which are running on same port and creating the conflicts

Thanks & Regards,
Mahendra Kumar Gupta

Subject: It is possible that there is
Author: Jane Curry
Posted: 2014-01-20 11:35

It is possible that there is a clash for UDP/514 if you have both zensyslogd running AND you have your local syslog daemon collecting syslog messages from other devices. syslogd won't do that by default but you may have it configured that way. If so, it is possible to change the port of either the local syslogd or zensyslogd.

Much more likely, especially as you are seeing heartbeat failures from zenping too, is that your Zenoss system is under too much load. If you run the unix top command, are cpu and memory usage high

Are these heartbeat events regular Do they clear sometimes or does the repeat count just go up Are you seeing heartbeat failures for other daemons

Cheers,

Jane

Email: jane.curry@skills-1st.co.uk    Web: https://www.skills-1st.co.uk



< Previous
wmic Security Policy Limitations? 		  Next
Question on how zenoss handles incoming events(Zenoss on Ubuntu) 		>