As I understand them, these issues are usually caused because Zenoss 
thinks there should be a daemon or process running that no longer exists 
because the name changed. This is often caused when you rename the 
Zenoss server from, say, localhost to FQDN.

Zenoss doesn't as far as I know have persistent internal heartbeat 
objects. That is, zenoss doesn't have a list of what should be 
heartbeated hard coded somewhere. If it's received a heartbeat from 
something, it thinks it should again, and if it doesn't, it alerts.

Clearing heartbeats often fixes this issue, as if the daemon is really 
gone or renamed, the old name won't send a heartbeat that then would 
stop coming causing the alerts. So that's why using clear all heartbeats 
often works, it sets Zenoss to assume there is *nothing* to heartbeat 
on, and only builds up the alerting lists as new heartbeats come in from 
daemons.

What's probably happening is that something is causing heartbeats to be 
missed, perhaps an overloading of the heartbeating daemon?
--
James Pulver
Information Technology Area Supervisor
LEPP Computer Group
Cornell University



captn63 wrote, On 1/23/2009 6:51 PM:
> I was able to shut down Zenoss and manually clear the heartbeats out of the 
> MySql database. That solved the problem for a short time. Now, they are back. 
> Mostly in the form of 'zeneventlog heartbeat failures'. 
> 
> You are right, there are a number of posts regarding heartbeat failures, but 
> I cannot find an sound explanation as to what causes them or a fix that 
> prevents them. 
> 
> I had them before my upgrade to 2.3.2 but now there are ore frequent.
> 
> Thanks
> 
> 
> 
> 
> -------------------- m2f --------------------
> 
> Read this topic online here:
> http://forums.zenoss.com/viewtopic.php?p=30466#30466
> 
> -------------------- m2f --------------------
> 
> 
> 
> _______________________________________________
> zenoss-users mailing list
> [email protected]
> http://lists.zenoss.org/mailman/listinfo/zenoss-users
_______________________________________________
zenoss-users mailing list
[email protected]
http://lists.zenoss.org/mailman/listinfo/zenoss-users

Reply via email to