![]() |
![]() |
Subject: | stuck events |
Author: | [Not Specified] |
Posted: | 2015-02-09 06:48 |
hi, i'm getting stuck events with the ping status down, the field 'last seen' gets frozen at a given time, this only happens just after the 'Config Cycle Interval' that runs every 360 minutes. i'm running 3.2.1 because of a script that only works in that version.
can i get any help
2015-02-09 04:49:38,103 INFO zen.ZenPing: Finished pinging 998 jobs in 6.39 seconds
2015-02-09 04:50:19,001 INFO zen.ZenPing: _configCycle fetching configuration
2015-02-09 04:50:19,001 INFO zen.ZenPing: fetching monitor properties
2015-02-09 04:50:19,004 INFO zen.ZenPing: completed "fetching monitoring properties" request in 0.00 seconds
2015-02-09 04:50:19,004 INFO zen.ZenPing: getting threshold classes
2015-02-09 04:50:19,005 INFO zen.ZenPing: completed "getting threshold classes" request in 0.00 seconds
2015-02-09 04:50:19,005 INFO zen.ZenPing: getting collector thresholds
2015-02-09 04:50:19,036 INFO zen.ZenPing: completed "getting collector thresholds" request in 0.03 seconds
2015-02-09 04:50:19,036 INFO zen.ZenPing: fetching default RRDCreateCommand
2015-02-09 04:50:19,037 INFO zen.ZenPing: getting ping tree
2015-02-09 04:50:22,988 INFO zen.ZenPing: completed "getting ping tree" request in 3.95 seconds
2015-02-09 04:50:22,990 INFO zen.ZenPing: Rescheduling configuration check in 21600 seconds
just after this if there was a status ping down event it will stay there even if the device is responding.
If i delete the event manually it gets fixed, also if i restart zenping.
Subject: | for the moment i have changed |
Author: | [Not Specified] |
Posted: | 2015-02-11 13:16 |
for the moment i have changed de collector config:
Config Cycle Interval (mins) 525600
< |
Previous help cisco switch |
Next custom configuration properties |
> |