![]() |
![]() |
Subject: | heartbeat failure |
Author: | Matthew Smith |
Posted: | 2020-07-20 03:39 |
I orignally had "localhost zenstaus heartbeat failure" consistently as well as 3 oversubscribed instances (zeneventd, MetricConsumer, and Zope) of which I
1. Add the zenoss5 endpoint to my zenoss server's /etc/hosts
2. Increased the Ram requested of the oversubscribed instances from 256M to 512M
That fixed the oversubscribed issue (for now anyway) but the heartbeat failure count was still going up.
Next I restarted Zenoss core (all instances) and that messages looke dlike they stopped however 7-8 hours after the restart and now I have a new heartbeat failure message relating to zenperfsnmp.
Any pointers in the right direction from anyone would be helpful thanks.
< |
Previous Unable to Model Juniper SRX 500 firewall |
Next AttributeError:'NoneType object' has no attribute 'id' |
> |