---

Subject:	have you restarted zenoss
Author:	[Not Specified]
Posted:	2015-06-18 12:42

have you restarted zenoss after commiting

Also, for a zenpack (wmware esxi monitor), i had to attach to zenhub container, dunno if that might make a difference.

---

Subject:	Yep
Author:	[Not Specified]
Posted:	2015-06-18 13:00

I did it now... I should have come here and posted how to solve it.

Thanks for the time to answer it anyway.

---

Subject:	Same Issue
Author:	[Not Specified]
Posted:	2015-12-28 05:33

Hello Trojahn .I'm facing same issue. Installation is exaclty same as yours. Restarted zenoss. Still getting same error

Executing command
/usr/sbin/fping [args omitted]
against 10.10.254.224
/bin/sh: /usr/sbin/fping: No such file or directory

-----------------------------------------------------------------------------------------------

My Zenoss 5 installation can't execute the command "fping" which is installed on the system.

I understand that the container may not have access to the "outside" but how can I add fping to it

I already did this (as I found on another post):
# serviced service shell -s Fping -i Zope bash
# wget ftp://fr2.rpmfind.net/linux/dag/redhat/el7/en/x86_64/dag/RPMS/fping-3.10...
# rpm -ivh fping-3.10-1.el7.rf.x86_64.rpm
# exit
# serviced snapshot commit Fping
# serviced service shell -i Zope bash
# fping 10.10.254.224
10.10.254.224 is alive

Even though the command is accessible from the container, if I run it from the Zenoss web interface I get the following:
Preparing Command...
Executing command
/usr/sbin/fping [args omitted]
against 10.10.254.224
/bin/sh: /usr/sbin/fping: No such file or directory
DONE in 0 seconds

So, my conclusion is that the command should be installed elsewhere, not in the Zope container...

Where do I install it

---

Subject:	Can't help you... What I did
Author:	[Not Specified]
Posted:	2015-12-28 07:25

Can't help you... What I did is already on my initial post...

After that I completelly gave up on Zenoss 5 and went back to 4x. After a UPS fail, my Zenoss instalation was LOST, docker couldn't find any containers to start and since I wasted too much time trying to figure out this whole Docker thing just to get Zenoss installed I decided to go back to 4x. I think Zenoss and Docker either were a bad move or just too "alpha" for my use... As IT sometimes we are just too busy to add another point of failure to our infrastructure and time is money...

I hope this get more stable, otherwise I'm gonna have to find some other monitoring system since 4x will be dropped eventualy.

---

Subject:	Zenoss v 5.0.9:# serviced
Author:	Jan Garaj
Posted:	2015-12-28 15:08

Zenoss v 5.0.9:
# serviced service shell -s Fping -i Zope yum install -y http://fr2.rpmfind.net/linux/dag/redhat/el7/en/x86_64/dag/RPMS/fping-3.10-1.el7.rf.x86_64.rpm
# serviced snapshot commit Fping
# serviced service restart Zope

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

---

Subject:	Fping finally works!!!!!!!
Author:	[Not Specified]
Posted:	2015-12-29 03:42

Thank you Trojahn and Jan.garaj for your quick reply.Fping works now!!!

What I did is..

First removed Fping zenpack. Then

~$ sudo serviced service shell -s Fping -i Zope

# yum install fping

#exit

~$ sudo serviced snapshot commit Fping

~$ sudo serviced service restart Zope

~$wget http://wiki.zenoss.org/download/zenpacks/ZenPacks.BlakeDrager.fping/1.1/ZenPacks.BlakeDrager.fping-1.1.egg

:~$ sudo serviced service run zope zenpack install ZenPacks.BlakeDrager.fping-1.1.egg

~$sudo apt-get install fping