[zenoss-users] *All* heartbeats failing?!

[Chet Luther]

On Sep 10, 2008, at 10:48 PM, Mike DeGraw-Bertsch wrote:
> I've started to see all of the Zenoss heartbeats fail, even though all
> of the daemons appear to be up and running happily.  zenwin, zenhub,
> zentrap, the list goes on...  I'm not actually noticing anything weird
> on the box, other than the heartbeat events--everything else is
> working swimmingly.
>
> This happened once before and I ended up re-installing Zenoss (thought
> it was a plugin error I made), and while it went away for a bit, it
> started back up again today.  I'm a bit concerned that the box I have
> (some random old desktop-spec machine) can't handle the load of the
> devices I'm monitoring (20-odd boxes), but I'm not seeing unusually
> high loads or memory usage.
>
> I am seeing an error about Zope being unable to install Five in
> events.log, but this only occured after the heartbeat failures
> started. There are no other errors mention in the zenoss/log files.

The error about Five is nothing to be concerned about. It could just  
be that your system thinks its named has changed and is now sending  
heartbeats under a different device name. What does this command return?

mysql -uzenoss -pzenoss events -e "select * from heartbeat order by  
lastTime desc"