Trigger stopped working after 1.6->1.8 upgrade.

[Firm]

I use 'icmpping' from 'Simple checks' to be aware of host availability every 5 seconds. Also I have trigger '{Isp:icmpping.count(30,1)}<1' which sends alert if consecutive pings within 30 last seconds return 0 state. In 1.6 it worked. In 1.8 - not. Any ideas?

[RonikBeast]

FPING missing?

This happened to me the same, but looking at the cause of the error, the description of the item that I saw marked "Not supported" and that was because the error icon.

Putting the error over the icon I saw that told me I was missing the command "fping". The error was this:

/ usr / sbin / fping: [2] No such file or directory

See if you feel the same, at least in the server version of Ubuntu do not install the program by default, you have to install a post and make sure the program path is correct, or modify the file Zabbix configuration to tell the new location.

[Firm]

Well, data get collected as usual (0 - down, 1 - up). But trigger stopped to react. I've re-created it - no luck. Think about changing it to {Isp:icmpping.count(#5,1)}<1 (last 5 values are zeroes). Will check if it helps.

[Firm]

Good news. Changing trigger from '{Isp:icmpping.count(30,1)}<1' to '{Isp:icmpping.count(#5,1)}<1' helped.

[cionfolinet]

I have the same problem.
My trigger is {Isp:icmpping.count(400,0)}>6 (Number of retrived values 0 for period of time 400 > 6).

In 1.6.7 works fine.

Now if i change my trigger in {Isp:icmpping.count(#5,1)}<1 works.

I think this is a bug.

[zabbix_zen]

I'll only update to 1.8 next week but this looks like a bug indeed.

Can you file a bug in : https://support.zabbix.com/browse/ZBX?

[cionfolinet]

I'll only update to 1.8 next week but this looks like a bug indeed.

Can you file a bug in : https://support.zabbix.com/browse/ZBX?

Of course!

#ZBX-1730

[Spectroman]

fping option failure

After updating from Zabbix 1.6.6 -> 1.8, fping failed.

Raising the debug level on the log I received the following:

32282:20100111:152641.336 /usr/sbin/fping -q -C3 -S10.3.0.151 2>&1 </tmp/zabbix_server_32282.pinger
32282:20100111:152641.343 Update IP [/usr/sbin/fping: invalid option -- S]
32282:20100111:152641.343 Update IP [Usage: /usr/sbin/fping [options] [targets...]]
32282:20100111:152641.344 Update IP [ (ex. /usr/sbin/fping -g 192.168.1.0 192.168.1.255 or /usr/sbin/fping -g 192.168.1.0/24)]

Is that my fping is too old (it is the latest), or the option is not supposed to be there?

Fping information follows:

xx151:/data/install/sources # fping -v
fping: Version 2.4b2_to $Date: 2001/01/25 11:25:04 $
fping: comments to [email protected]

xx151:/data/install/sources # fping -h

Usage: fping [options] [targets...]
-a show targets that are alive
-A show targets by address
-b n amount of ping data to send, in bytes (default 68)
-B f set exponential backoff factor to f
-c n count of pings to send to each target (default 1)
-C n same as -c, report results in verbose format
-e show elapsed time on return packets
-f file read list of targets from a file ( - means stdin) (only if no -g specified)
-g generate target list (only if no -f specified)
(specify the start and end IP in the target list, or supply a IP netmask)
(ex. fping -g 192.168.1.0 192.168.1.255 or fping -g 192.168.1.0/24)
-i n interval between sending ping packets (in millisec) (default 25)
-l loop sending pings forever
-m ping multiple interfaces on target host
-n show targets by name (-d is equivalent)
-p n interval between ping packets to one target (in millisec)
(in looping and counting modes, default 1000)
-q quiet (don't show per-target/per-ping results)
-Q n same as -q, but show summary every n seconds
-r n number of retries (default 3)
-s print final stats
-t n individual target initial timeout (in millisec) (default 500)
-u show targets that are unreachable
-v show version
targets list of targets to check (if no -f specified)
------
** notice no such option -S **

Using the fping from original source: http://fping.sourceforge.net/

** solution follows **

[Spectroman]

fping option failure - ** solution **

Hello,

Something strange has happened after I did the Zabbix update between 1.6.6 -> 1.8, the problem that I could figure out properly now is:

- During the change of versions, I noticed some new options on the new zabbix_server.conf , so I opt to use the new version, and I configured the whole new file accordingly the older conf options and using some new ones;

- Among these options I enabled : SourceIP - source ip address for outgoing connections;

- When I put the server up, he was failing in all the ICMP tests, and raising the debug level (to 4) I could see an error on the fping usage, something very weird;

- After investigating a little further, I figure out that, even if I fix the exceeding option (-S) for fping, in the source code of [ /zabbix-1.8/src/libs/zbxicmpping/icmpping.c -- line 58 ] which corresponds to the configuration option of "Source IP", it does not work at all, any of the ICMP work -- probably because this options affect more lines of code and actions of the system;

- Later on, disabling the option Source IP from the configuration file, almost magically, everything went back to normal.

I believe I stumble in a couple of bugs, isn't?

- I also noticed that with the SourceIP enabled, he conflicts with the zabbix_agent port, if both are configured with the defaults.

I hope this could help others to figure out this erratic behavior with fping / source ip option.

[davidpe]

Using version 1.8.1, I removed lines 57 and 58 in that file, recompiled, and has been working just fine.