icmpping update interval Wrong !

[BusteR81]

set simple check icmpping at 30sec update interval

latest data (500 last values) shows 1min update interval

what can be wrong? tail -f /tmp/zabbix_server.log shows NO error.

i am using svn 1.4.5 zabbix and all my 4 zabbix servers are doing icmpping at 1min interval which should be 30sec interval. icmpping trigger still works fine though even @1min interval.....just curious

[Alexei]

Refresh rate for ICMP ping related check is set by ZABBIX server configuration parameter PingerFrequency, which can be found in zabbix_server.conf. Item-level update interval is ignored for icmpping and icmppingsec.

Note that next major release will support different ICMP ping update intervals configurable on item level.

[BusteR81]

cheers

checked my zabbix_server.conf and found

# Frequency of ICMP pings (item keys 'icmpping' and 'icmppingsec'). Defauls is 60 seconds.
#PingerFrequency=60

Thanks for your quick response.

[psmul]

This thread is a bit old, but since i had a problem concerning interval values that were incorrect, i want to post my finding for future reference.

I have 400+ items in my list. Since none of them are running Zabbix agent I only use icmpping to determine if they are 'up'. I set the interval for servers around 15 seconds. When i check the 'latest data' and the 'last 500 results' it keeps giving me values after every 47 seconds. Which does not match the 15 sec I want it to be.

My problem was that my server (or better: my fping service) was overloaded (or somesort) by the 400+ items I have in my lists. By increasing the "pre-forked instances of ICMP pingers" to 8, my problem was solved.

Summary:
If your 'latest result' icmpping interval does not match the one you set on items, increase the "pre-forked instances of ICMP pingers" in the zabbix_server.conf file and restart the service