|
|
| Subject: | Daemon heartbeat failure every 12 hours |
| Author: | [Not Specified] |
| Posted: | 2014-04-18 01:22 |
I encountered error Daemon heartbeat failure every 12 hours,like Zenhub Zeneventd etc.
When this happen, I check CPU and Memory, they are not high and actually daemons are all running.
I have changed the model device cycle time to 48 hours, still get failure notice every 12 hours.
check the daemon log, cannot see any clue
my Zenoss servers have 6 logistic CPU,26GB memory.
250 windows system added into Zenoss
Check Collectors -> Performance in Zenoss, only see ZenWin queued task is running high at that time.
Even not enable snmp scanning on device, in DataPoints window, zenperfsnmp keeps high.
I suspect the beartbeat failure notice is related to Watchdog option is enabled.
Any one can give some advice
| Subject: | Hi Support Any idea? |
| Author: | [Not Specified] |
| Posted: | 2014-04-20 23:00 |
Hi Support Any idea
| Subject: | Hi Support Any idea? |
| Author: | [Not Specified] |
| Posted: | 2014-04-25 03:39 |
Hi Support Any idea
| Subject: | Is it all the daemons that |
| Author: | [Not Specified] |
| Posted: | 2014-04-25 09:37 |
Is it all the daemons that report it or just the ones you mentioned
Check the zenhub log file, for the time period where it happens, to see if the log gives you any helpful information. Is this a dedicated zenoss server
Hydruid
| Subject: | no, if not to enable debug |
| Author: | [Not Specified] |
| Posted: | 2014-04-27 22:40 |
no, if not to enable debug mode ,only below error can see.
notification:
Device: localhost
Component: zenhub
Severity: 5
Time: 2014/04/26 20:39:28.000
Message:
localhost zenhub heartbeat failure
zenhub.log:
2014-04-26 20:33:35,631 INFO zen.ZenHub: Worker (18437) reports 2014-04-26 20:33:35,631 INFO zen.zenhubworker: Shutting down
2014-04-26 20:33:35,632 INFO zen.ZenHub: Worker (18437) reports 2014-04-26 20:33:35,631 INFO zen.zenhubworker: Stopping reactor
2014-04-26 20:33:35,632 INFO zen.ZenHub: Worker (18437) reports 2014-04-26 20:33:35,632 INFO zen.zenhubworker: Daemon zenhubworker shutting down
2014-04-26 20:33:35,757 WARNING zen.ZenHub: Worker (18437) exited with status: 0 (Success)
2014-04-26 20:33:35,757 INFO zen.ZenHub: Starting new zenhubworker
2014-04-26 20:39:22,604 INFO zen.ZenHub: Worker (18762) reports 2014-04-26 20:39:22,604 INFO zen.zenhubworker: Shutting down
2014-04-26 20:39:22,604 INFO zen.ZenHub: Worker (18762) reports 2014-04-26 20:39:22,604 INFO zen.zenhubworker: Stopping reactor
2014-04-26 20:39:22,605 INFO zen.ZenHub: Worker (18762) reports 2014-04-26 20:39:22,605 INFO zen.zenhubworker: Daemon zenhubworker shutting down
2014-04-26 20:39:22,730 WARNING zen.ZenHub: Worker (18762) exited with status: 0 (Success)
2014-04-26 20:39:22,730 INFO zen.ZenHub: Starting new zenhubworker
2014-04-26 20:44:48,121 INFO zen.ZenHub: Worker (20437) reports 2014-04-26 20:44:48,121 INFO zen.zenhubworker: Shutting down
2014-04-26 20:44:48,122 INFO zen.ZenHub: Worker (20437) reports 2014-04-26 20:44:48,121 INFO zen.zenhubworker: Stopping reactor
2014-04-26 20:44:48,122 INFO zen.ZenHub: Worker (20437) reports 2014-04-26 20:44:48,122 INFO zen.zenhubworker: Daemon zenhubworker shutting down
2014-04-26 20:44:48,245 WARNING zen.ZenHub: Worker (20437) exited with status: 0 (Success)
2014-04-26 20:44:48,245 INFO zen.ZenHub: Starting new zenhubworker
2014-04-26 20:50:41,314 INFO zen.ZenHub: Worker (20876) reports 2014-04-26 20:50:41,313 INFO zen.zenhubworker: Shutting down
2014-04-26 20:50:41,314 INFO zen.ZenHub: Worker (20876) reports 2014-04-26 20:50:41,314 INFO zen.zenhubworker: Stopping reactor
2014-04-26 20:50:41,314 INFO zen.ZenHub: Worker (20876) reports 2014-04-26 20:50:41,314 INFO zen.zenhubworker: Daemon zenhubworker shutting down
2014-04-26 20:50:41,460 WARNING zen.ZenHub: Worker (20876) exited with status: 0 (Success)
2014-04-26 20:50:41,460 INFO zen.ZenHub: Starting new zenhubworker
2014-04-26 20:57:54,835 INFO zen.ZenHub: Worker (21784) reports 2014-04-26 20:57:54,835 INFO zen.zenhubworker: Shutting down
2014-04-26 20:57:54,836 INFO zen.ZenHub: Worker (21784) reports 2014-04-26 20:57:54,835 INFO zen.zenhubworker: Stopping reactor
2014-04-26 20:57:54,836 INFO zen.zenhubworker: Daemon zenhubworker shutting down
2014-04-26 20:57:54,963 WARNING zen.ZenHub: Worker (21784) exited with status: 0 (Success)
2014-04-26 20:57:54,963 INFO zen.ZenHub: Starting new zenhubworker
| Subject: | Workers |
| Author: | [Not Specified] |
| Posted: | 2014-04-28 08:40 |
Daemons that have "workers" are designed to start/stop, that is completely normal operation.
Are you getting heartbeat failure events
Hydruid
| Subject: | yes, but it is cleared |
| Author: | [Not Specified] |
| Posted: | 2014-04-30 00:25 |
yes, but it is cleared automatically very quickly and only count 1
| Subject: | Ignore |
| Author: | [Not Specified] |
| Posted: | 2014-04-30 07:36 |
It's a little weird that it throws an error but it's most likely safe to ignore. I suggest running ZenUp to patch to the latest version!
Hydruid
| < |
Previous Help with transform |
Next Hard Stop - now all I get is "A Zenoss error has occurred" |
> |