ICPM Template Zabbix Appliance 2.2

[tbollig]

grep FpingLocation /etc/zabbix_server.conf
### Option: FpingLocation
# FpingLocation=/usr/sbin/fping

[EnigmA-X]

Hmm. I will try the appliance myself tomorrow to figure out what is going wrong. Did you restart the zabbix-server service (or reboot the appliance) after you've set the new permissions?

Update:

chmod 4710 /usr/sbin/fping

[tbollig]

### Option: FpingLocation
# Location of fping.
# Make sure that fping binary has root ownership and SUID flag set.
#
# Mandatory: no
# Default:
# FpingLocation=/usr/sbin/fping

### Option: Fping6Location
# Location of fping6.
# Make sure that fping6 binary has root ownership and SUID flag set.
# Make empty if your fping utility is capable to process IPv6 addresses.
#
# Mandatory: no
# Default:
# Fping6Location=/usr/sbin/fping6

Here is the info on the zabbix_server.conf

Do I need to uncomment the locations of the fping and fping6

[EnigmA-X]

No, you shouldn't have to. Just run the chmod command from my previous post.

[tbollig]

Alright...some good news here. I re-ran the chmod commands. Rebooted the server and we are rockin! thanks for you help. Great product and help!

[brades98]

fping on appliancd 2.2 doesn't work after all these steps

I've tried every step in this thread and I still cannot get it to work. I have verified every entry mentioned and they all come back correct. If this is an appliance ready to test, why doesn't this thing work out of the box if you will. I've spend days now on this reading, trouble shooting, etc and it still can't do a basic test like pinging an IP address to see if the hardware is up or down.

[EnigmA-X]

What are the symptoms of your issue? Can you paste any logfile(s)? Is your issue exactly the same as OP?

[brades98]

I had all the same results as the above posts by tbollig. I reapplied the chmod multiple times rebooted server, again and again, re-verified settings and rebooted server many times. Finally it seems to work. I'm not sure if the first chmod of 710 was wrong, but the chmod 4710 seemed to resolve it. Here is all I went through, verified, and finally got the system to work.

cat /etc/group
zabbix:x:499

zabbix user doesn't show it is in the group so run the command to add it to the group

# usermod -a -G zabbix zabbix
# cat /etc/group
zabbix:x:499:zabbix

# groups zabbix
zabbix : users zabbix

# ls -la /usr/sbin/fping*
-rws--s--- 1 root zabbix 31400 Jan 31 2013 /usr/sbin/fping
-rws--s--- 1 root zabbix 31408 Jan 31 2013 /usr/sbin/fping6

# grep FpingLocation /etc/zabbix/zabbix_server.conf
as posted, this command is invalid on the 2.2 appliance as it is not in the /etc/zabbix folder. It is:

# grep FpingLocation /etc/zabbix_server.conf
### Option: FpingLocation
# FpingLocation=/usr/sbin/fping
#grep Fping6Location /etc/zabbix_server.conf
### Option: FpingLocation
# FpingLocation=/usr/sbin/fping6

So after verifying all the above steps, which I did a couple times, apparently the real fix, as posted earlier had a typo in it and it should be like this:
shell> chown root:zabbix /usr/sbin/fping
shell> chmod 4710 /usr/sbin/fping
shell> chmod ug+s /usr/sbin/fping

I also applied these same commands to fping6 as it then threw errors complaining about that.
# chown root:zabbix /usr/sbin/fping6
# chmod 4710 /usr/sbin/fping6
# chmod ug+s /usr/sbin/fping6

# ls -la /usr/sbin/fping*
-rws--x--- 1 root zabbix 31400 Jan 31 2013 /usr/sbin/fping
-rws--x--- 1 root zabbix 31408 Jan 31 2013 /usr/sbin/fping6


Hours spent trying to figure out all of this and I would have assumed, being an appliance downloaded as a VHD, the drive would have already been configured and all of these settings to have been correctly enabled for the most basic steps of monitoring an environment. ICMP is critical as an initial tool and this component was broken in the 2.2 appliance as downloaded.

Also there is no swap file space on the appliance as downloaded and the system throws a constant error about is so this also had to be added with help from this link. http://itstickers.besthw.net/en/addi...p-in-opensuse/ I would expect the swap space to also have been configured in the appliance for testing purposes so a user didn't have to figure this out and create one to make the error go away. After first start the error is there and won't go away until a swap file is created.

It is a great monitoring tool now that it is functional. I just wish the appliance was truly ready to test with as is. Maybe someone can fix this and rebuild the VHD and other downloads in the 2.2 appliance so they are truly ready as is after download. Hopefully 2.4 appliance will not have this issue when it becomes available.

Awesome piece of software, keep up the great open source work.

Thank you...

[orxlnk]

For who cant solve that, try:

chmod +x /usr/sbin/fping

[genesearch]

I had all the same results as the above posts by tbollig.

Me too. I tried everything in this thread, and results are the same, sometimes a variation on the error.

I gave up and installed the normal version on some random old VPS that I keep for messing about with, and everything works out of the box.