---

Subject:	Basic investigation:
Author:	Jan Garaj
Posted:	2015-01-14 02:41

Basic investigation:
1.) Is zenoss running OK
command: /etc/init.d/zenoss status
check log files: /opt/zenoss/logs/*.log
2.) Defining thresholds
How did you define metric thresholds
Guide for Filesystem thresholds - http://wiki.zenoss.org/Filesystem_thresholds
What are collected metric values

Please provide command outputs and images, because it's hard to identify some exact problem from your general problem description.

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

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

---

Subject:	/etc/init.d/zenoss status-->
Author:	[Not Specified]
Posted:	2015-01-14 07:40

/etc/init.d/zenoss status-->
Daemon: zeneventserver program running; pid=4537
Daemon: zopectl program running; pid=4649
Daemon: zenrrdcached program running; pid=4654
Daemon: zenhub program running; pid=4698
Daemon: zenjobs program running; pid=4777
Daemon: zeneventd program running; pid=4649
Daemon: zenping program running; pid=4903
Daemon: zensyslog program running; pid=4996
Daemon: zenstatus program running; pid=4979
Daemon: zenactiond program running; pid=5017
Daemon: zentrap program running; pid=5099
Daemon: zenmodeler program running; pid=5104
Daemon: zenperfsnmp program running; pid=5134
Daemon: zencommand program running; pid=5168
Daemon: zenprocess program running; pid=5198
Daemon: zredis program running; pid=5202
Daemon: zenpython program running; pid=5237
Daemon: zenjmx program running; pid=5272

root@localhost ~]# ls -lhc /opt/zenoss/log/
total 109M
-rw-r--r-- 1 zenoss zenoss 49K Jan 13 19:29 event.log
-rw-r--r-- 1 zenoss zenoss 14K Mar 11 2014 install.log
drwxr-xr-x 2 zenoss zenoss 4.0K Jan 13 19:29 jobs
prw-r--r-- 1 zenoss zenoss 0 Mar 11 2014 logging.fifo
-rw-r--r-- 1 zenoss zenoss 0 Mar 11 2014 main.log
-rw-rw-r-- 1 zenoss zenoss 0 Mar 11 2014 pagestats.log
-rw-r--r-- 1 zenoss zenoss 57 Mar 11 2014 README.txt
-rw-r--r-- 1 zenoss zenoss 39M Jan 14 08:27 Z2.log
-rw-rw-r-- 1 zenoss zenoss 1.6M Jan 14 08:27 zenactiond.log
-rw-rw-r-- 1 zenoss zenoss 587 Mar 11 2014 zenbuild_init.log
-rw-rw-r-- 1 zenoss zenoss 108 Mar 11 2014 zenbuild.log
-rw-rw-r-- 1 zenoss zenoss 1.6M Jan 14 08:24 zencommand.log
-rw-rw-r-- 1 zenoss zenoss 12K Dec 30 12:36 zeneventd.log
-rw-rw-r-- 1 zenoss zenoss 452K Jan 14 07:39 zeneventserver.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 6 19:00 zeneventserver-stdio.2015_01_07.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 7 19:00 zeneventserver-stdio.2015_01_08.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 8 19:00 zeneventserver-stdio.2015_01_09.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 9 19:00 zeneventserver-stdio.2015_01_10.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 10 19:00 zeneventserver-stdio.2015_01_11.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 11 19:00 zeneventserver-stdio.2015_01_12.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 12 19:00 zeneventserver-stdio.2015_01_13.log
-rw-rw-r-- 1 zenoss zenoss 0 Jan 13 19:00 zeneventserver-stdio.2015_01_14.log
-rw-rw-r-- 1 zenoss zenoss 1.4M Jan 14 08:21 zenhub.log
-rw-rw-r-- 1 zenoss zenoss 1.6M Jan 14 08:26 zenjmx.log
-rw-rw-r-- 1 zenoss zenoss 58K Jan 13 19:30 zenjobs.log
-rw-rw-r-- 1 zenoss zenoss 957K Jan 14 00:41 zenmodeler.log
-rw-rw-r-- 1 zenoss zenoss 16K Dec 30 12:48 zenpackcmd.log
-rw-rw-r-- 1 zenoss zenoss 0 Mar 11 2014 zenpackdaemons.log
-rw-rw-r-- 1 zenoss zenoss 1.7M Jan 14 08:24 zenperfsnmp.log
-rw-rw-r-- 1 zenoss zenoss 1.6M Jan 14 08:24 zenping.log
-rw-rw-r-- 1 zenoss zenoss 2.7M Jan 14 08:27 zenprocess.log
-rw-r--r-- 1 zenoss zenoss 6.9M Jan 14 08:26 zenpython.log
-rw-r--r-- 1 zenoss zenoss 11M Jan 10 14:41 zenpython.log.1
-rw-rw-r-- 1 zenoss zenoss 11M Jan 10 14:41 zenpython.log.2
-rw-rw-r-- 1 zenoss zenoss 7.7M Jan 14 08:27 zenstatus.log
-rw-rw-r-- 1 zenoss zenoss 1.6M Jan 14 08:27 zensyslog.log
-rw-rw-r-- 1 zenoss zenoss 1.6M Jan 14 08:24 zentrap.log
-rw-rw-r-- 1 zenoss zenoss 19M Jan 14 08:27 zredis.log

all process and services show running OK
i used a linux host with snmp and the filesystem threshold defined was here.getTotalBlocks() * .2 ( used a value of 20% to artificially try and trigger the threshold)

I bought up several new instances on zenoss and have found the following

1. The appliance did not work for me when i used vmware converter and converted the appliance to a vmware infrastructure virtual machine. This is the scenario that I have described above

2. I used vmware player to run the source machine for the conversion and this instance came up and worked like a champ, i was able to add devices, create triggers and notifications and the system found the exceeded thresholds defined and raised appropriate events and triggers to work correctly.

3. The same machine was converted to a Microsoft Hyper-V machine and did not work again. ping devices were added that did not exist and the system still saw them as up devices. same problems as situation 1 were observed.

continuing to work on this to get more clarity

---

Subject:	an image of the issue
Author:	[Not Specified]
Posted:	2015-01-14 07:43

http://imgur.com/Qm4tKED

---

Subject:	When you convert those VMs
Author:	[Not Specified]
Posted:	2015-01-14 08:19

When you convert those VMs are you changing the hostname/IP address you may need to rebuild your message queues
https://openavenzer.wordpress.com/2014/09/14/i-just-changed-the-host-nam...

---

Subject:	virtual machive version 8 seems to work
Author:	[Not Specified]
Posted:	2015-01-14 13:17

converting the vm guest by using vmware converter set to vmware virtual machine version 8 seems to work too