TECHZEN Zenoss User Community ARCHIVE  

Spurious eventkey leaving my alerts on timeout

Subject: Spurious eventkey leaving my alerts on timeout
Author: Joan
Posted: 2016-12-01 09:23

I have create an script run via zencommand that pings the hosts in a low bandwith mode, the script returns the proper data and it has been working properly for a lot of time, but recently it seems that there's a timeout blocking the results to appear in zenoss.

This is what I see in the logs when zencommand is in debug mode, specially the bold part:

2016-12-01 13:47:15,656 DEBUG zen.zencommand: Datasource: slowping Received exit code: 0 Output:
"OK"
2016-12-01 13:47:15,656 DEBUG zen.zencommand: Process slowping/slowping stopped (0), 1.46 seconds elapsed
2016-12-01 13:47:15,657 DEBUG zen.collector.scheduler: Task CT-040 300 Local changing state from FETCH_DATA to PARSING_DATA
2016-12-01 13:47:15,657 DEBUG zen.collector.scheduler: Task CT-040 300 Local changing state from PARSING_DATA to STORE_PERF_DATA
2016-12-01 13:47:15,658 DEBUG zen.RRDUtil: /opt/zenoss/perf/Devices/CT-040/slowping_Up.rrd: 2.0, @ N
2016-12-01 13:47:15,658 DEBUG zen.zencommand: allowduplicateclears dropping clear event {'manager': 'zenoss.bassols-energia.es', 'eventKey': 'Timeout', 'device_guid': '2b4b4a5d-9012-4301-a6
77-14b4a73f0220', 'device': 'CT-040', 'eventClass': '/Status/Ping', 'summary': 'Datasource slowping/slowping command timed out', 'component': '', 'monitor': 'localhost', 'agent': 'zencomman
d', 'severity': 0}
2016-12-01 13:47:15,658 DEBUG zen.zencommand: allowduplicateclears dropping clear event {'severity': 0, 'component': '', 'eventClass': '/Status/Ping', 'summary': 'El host a verificar \xc3\x
a9s 10.64.192.141 -- ara: 2016-12-01 13:47:14.313606', 'manager': 'zenoss.bassols-energia.es', 'eventKey': 'slowping', 'agent': 'zencommand', 'device': 'CT-040', 'message': "OK", 'device_guid': '2b4b4a5d-9012-4301-a677-14b4a73f0220', 'performanceData': [' Up=2'], 'monitor': 'localhost'}
2016-12-01 13:47:15,658 DEBUG zen.zencommand: Collection time for CT-040 was 1.466059 seconds; cycle interval is 300 seconds.
2016-12-01 13:47:15,658 DEBUG zen.collector.scheduler: Task CT-040 300 Local finished, result: [(, ParsedResults
events: [{'component': '',
'device': 'CT-040',
'eventClass': '/Status/Ping',
'eventKey': 'Timeout',
'severity': 0,
'summary': 'Datasource slowping/slowping command timed out'},
{'component': '',
'device': 'CT-040',
'eventClass': '/Status/Ping',
'eventKey': 'slowping',
'message': "OK",
'performanceData': [' Up=2'],
'severity': 0,
'summary': 'OK'}]
values: [(({}, 'Up'), 2.0)]})
]
2016-12-01 13:47:15,662 DEBUG zen.collector.scheduler: Task CT-040 300 Local changing state from STORE_PERF_DATA to IDLE

I am really lost on the cause that makes this Timeout appear, any ideas



Subject: One of the ideas I had is to
Author: Joan
Posted: 2016-12-01 09:26

One of the ideas I had is to use set allowduplicateclears = True, but I don't fully understand what would do, also the reason of the script failing.



< Previous
How to backup MIBs and event map and transform?
  Next
Dashboard Filters on event portlet not sticking for users
>