Zenoss ZenTech Community

I have ran into a issue with the ZenPing deamon in my Zenoss 5 test environment.

1. My Zenping is set to ping every 10minutes.
2. 4000 Ping devices
3. 2500 Down devies (Stress testing)

1. 24 CPU Cores (2 X Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz)
2. 32GB RAM (I increased the RAM from 24GB to 32GB to see if it would fix the issue, did not)
3. Control Center 5.0.2
4. Zenoss version 5.0.3

The Zenping deamon works fine, and then it just randomly stops functioning correctly or stops logging the perfdata. Control Center still reports Zenping as functioning. This is the only thing I can see in the logs from this morning:

2015/09/10 08:57:08 200 4.032691ms POST /api/metrics/store
2015/09/10 08:57:13 200 3.909377ms POST /api/metrics/store
2015/09/10 08:57:14 200 4.071406ms POST /api/metrics/store

I monitored a device with tcpdump, and I can see that pings are still being sent by Zenoss, but I am not seeing these data points on my graphs. Picture below:

It seems like it stopped functioning just before 14H00 yesterday. Restarting ZenPing fixes the issue.

Subject:	I'd suggest filing a bug on
Author:	Andrew Kirch
Posted:	2015-09-11 14:05

I'd suggest filing a bug on this. http://jira.zenoss.com. If you reply wtih the bug number I'll make sure everyone can see it.

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

Subject:	Hi Trelane,
Author:	[Not Specified]
Posted:	2015-09-16 04:40

Hi Trelane,

Bug logged: https://jira.zenoss.com/browse/ZEN-19771

Let me know if you want me to perform any other tests.

Subject:	He suggested I increase the
Author:	[Not Specified]
Posted:	2015-09-22 02:28

He suggested I increase the ZenPing instance amount, but it keeps giving me the following error: "number of instances is too small".

Seems like it only accepts 1.

http://imgur.com/7kcYtul

I could increase the amount of ZenHub instances though.

Subject:	I just kicked it back to him
Author:	Andrew Kirch
Posted:	2015-09-23 18:50

I just kicked it back to him for additional followup.

Subject:	Hi Trelane,
Author:	[Not Specified]
Posted:	2015-10-07 08:40

Hi Trelane,

Any feedback on this

I see the last post as:

"Andrew D Kirch added a comment - 23/Sep/15 6:50 PM
reopened as bug appears to be in an incorrect "awaiting verification" disposition since the original filer of the bug answered."

Subject:	the bug is listed as in
Author:	Andrew Kirch
Posted:	2015-10-08 13:21

the bug is listed as in process.

Subject:	Is this still a issue??
Author:	[Not Specified]
Posted:	2016-07-27 04:14

Is this still a issue

Did a fresh install of 5.1.4 and I got the same issue, how is that possible.

http://imgur.com/a/oZk9g

https://jira.zenoss.com/browse/ZEN-19771jql=text%20~%20%22zenping%22

Subject:	This is still occuring even
Author:	[Not Specified]
Posted:	2016-08-18 04:44

This is still occuring even in v5.1.5.

So I take it from no response that ZenPing is very low pritiorty for Zenoss and it's been broken for the whole v5 release cycle. Does no one else use ZenPing

I really don't want to start looking for another monitoring system, and input would be appreciated..

And once again, just restarting ZenPing fixes this issue.

Subject:	For anyone else struggling
Author:	[Not Specified]
Posted:	2016-08-29 01:32

For anyone else struggling with this.

I have changed the default ping daemon to nmap, and for now it seems to have fixed the problem.

Subject:	Another reason I have found
Author:	Jane Curry
Posted:	2016-08-31 09:52

Another reason I have found for zenping gradually failing is that, by default, every 5th ping adds a traceroute request to the default nmap command. Some devices / firewalls / intermediate routers block traceroute requests; this means that those pings never complete and you gradually get more-and-more outstanding requests. Look for high numbers of Missed_Runs and Queued_Tasks in zenping.log.

You can fix this with the traceroute_interval parameter to zenping. Either navigate to ADVANCED -> Daemons -> zenping and click the edit config button or you can simply edit $ZENHOME/etc/zenping.conf; either way, zenping will need restarting. You need to change this parameter to 0.

The negative corollary is that Zenoss will be unable to build its internal topology map which means that automatic suppression of events from device behind a single-point-of-failure, will no longer work.

Cheers,

Jane

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

Subject:	Hi Jane,
Author:	[Not Specified]
Posted:	2016-09-14 04:45

Hi Jane,

I tried that as well, and even with the trace interval changed to 0 zenping still crashes.

The only way to fix this is by changing the backend to nmap ping.

How this canstill be broken from v5.0.0 to v5.1.5 amazes me, but owell.

Subject:	Zenoss 5 ZenPing Issue
Author:	[Not Specified]
Posted:	2015-09-10 04:05

Zenoss 5 ZenPing Issue