---

Subject:	With the help of "Jan_Garaj"
Author:	[Not Specified]
Posted:	2015-09-23 16:19

With the help of "Jan_Garaj" at IRC I have solved the problem.

We didn't really found out what the root cause was since all we did was just to restart Zenoss.

Thanks to Jan_Garaj I 've also learned that it is useful to check the RRD files and see if they change. For each device there are located at /opt/zenoss/perf/DEVICE_ID/

They can be easily transformed into XML using the command rrdtool dump file.rrd > file.xml

Getting two XML files at different times can really show if they are different from one another (using diff command).

If they differ graphs should be generated.

Lastly it is also useful to watch the /opt/zenoss/log/zencommand.log to see if the devices are checked for new data.

Many thanks especially to Jan_Garaj

Best,

G.

---

Subject:	which version of Zenoss?
Author:	Andrew Kirch
Posted:	2015-09-23 18:40

which version of Zenoss What's in $ZENHOME/perf if it's 4.x, if it's 5.x are all your health checks passing in control center

Andrew Kirch

akirch@gvit.com

Need Zenoss support, consulting or custom development Look no further. Email or PM me!

Ready for Distributed Topology (collectors) for Zenoss 5 Coming May 1st from GoVanguard

---

Subject:	I am using v.4.2.5
Author:	[Not Specified]
Posted:	2015-09-24 01:00

I am using v.4.2.5

These are the contents of $ZENHOME/perf

drwxr-xr-x. 3 zenoss zenoss 4096 Sep 20 00:39 Daemons
drwxr-x--- 13 zenoss zenoss 4096 Sep 24 05:39 Devices
-rw-r--r-- 1 zenoss zenoss 1024 Sep 20 21:15 empty_empty.rrd
-rw-r--r-- 1 zenoss zenoss 1024 Sep 22 15:16 empty.rrd

When the problem was happening "zenoss status" was reporting that all services were running

Best,

G.