---

Subject:	collectorredis issue
Author:	[Not Specified]
Posted:	2015-06-10 11:52

I am finding some other issues which may be related. The Zenoss 5.03 GUI was showing I was using Zenoss.Microsoft.Windows 2.40 but from the command line I see the following - note the Microsoft version is represented different version. In the upgrade logs I saw that this egg failed as per below. I see 2.44 is out but will not install as it says previous version exists. Is there a way I can force remove the egg I tried removing old and new versions with no success. Still digging but thought I would ask.

INFO:zen.ZenPackCmd:looking for /opt/zenoss/.ZenPacks/ZenPacks.zenoss.Microsoft.Windows-2.4.0-*
INFO:zen.ZenPackCmd:looking for /opt/zenoss/packs/ZenPacks.zenoss.Microsoft.Windows-2.4.0-*
INFO:zen.ZenPackCmd:could not find install candidate for ZenPacks.zenoss.Microsoft.Windows 2.4.0

ZenPacks.zenoss.ApacheMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.ApacheMonitor-2.1.4-py2.7.egg)
ZenPacks.zenoss.Dashboard (/opt/zenoss/ZenPacks/ZenPacks.zenoss.Dashboard-1.0.5-py2.7.egg)
ZenPacks.zenoss.DellMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.DellMonitor-2.2.0-py2.7.egg)
ZenPacks.zenoss.DeviceSearch (/opt/zenoss/ZenPacks/ZenPacks.zenoss.DeviceSearch-1.2.0-py2.7.egg)
ZenPacks.zenoss.DigMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.DigMonitor-1.1.0-py2.7.egg)
ZenPacks.zenoss.DnsMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.DnsMonitor-2.1.0-py2.7.egg)
ZenPacks.zenoss.FtpMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.FtpMonitor-1.1.0-py2.7.egg)
ZenPacks.zenoss.HPMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.HPMonitor-2.1.0-py2.7.egg)
ZenPacks.zenoss.HttpMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.HttpMonitor-2.1.0-py2.7.egg)
ZenPacks.zenoss.LDAPMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.LDAPMonitor-1.4.1-py2.7.egg)
ZenPacks.zenoss.LinuxMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.LinuxMonitor-1.3.0-py2.7.egg)
ZenPacks.zenoss.Microsoft.Windows (/opt/zenoss/ZenPacks/ZenPacks.zenoss.Microsoft.Windows-2.3.1-py2.7.egg)
ZenPacks.zenoss.MySqlMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.MySqlMonitor-3.0.5-py2.7.egg)
ZenPacks.zenoss.NtpMonitor (/opt/zenoss/ZenPacks/ZenPacks.zenoss.NtpMonitor-2.2.1-py2.7.egg)
ZenPacks.zenoss.PythonCollector (/opt/zenoss/ZenPacks/ZenPacks.zenoss.PythonCollector-1.6.4-py2.7.egg)
ZenPacks.zenoss.ZenJMX (/opt/zenoss/ZenPacks/ZenPacks.zenoss.ZenJMX-3.11.0-py2.7.egg)

---

Subject:	found issue
Author:	[Not Specified]
Posted:	2015-06-10 12:33

I found the dump.rdb under /opt/serviced/var/volumes/69fv54vci7vkzdrbtw61yr80u/localhost/localhost_collectorredis. I moved it to another folder and restarted the collectorredis successfully. Checking on the Windows update now to see if that remains broken but wanted to update on the fix.

---

Subject:	Redis server failed to start
Author:	[Not Specified]
Posted:	2015-06-17 08:12

HI,

I've a similar problem, but is Redis server that fails to start.
The reason why it doesn't start is about the metrics health check failure.

Below the Redis log:

Connected to logstash server.
2015/06/15 04:32:01.911023 Registrar received 21 events
I0615 04:32:06.934667 00001 controller.go:612] Starting service process.
I0615 04:32:06.934794 00001 instance.go:79] about to execute: /bin/sh , [-c exec /usr/bin/redis-server /etc/redis.conf][2]
I0615 04:32:06.953254 00001 controller.go:606] Restarting service process in 10 seconds.
2015/06/15 04:32:09.410892 Registrar received 21 events
2015/06/15 04:32:11 200 2.104299ms POST /api/metrics/store
W0615 04:32:11.985135 00001 controller.go:777] Health check metrics failed.
I0615 04:32:16.953504 00001 controller.go:612] Starting service process.
I0615 04:32:16.953628 00001 instance.go:79] about to execute: /bin/sh , [-c exec /usr/bin/redis-server /etc/redis.conf][2]
I0615 04:32:16.972532 00001 controller.go:606] Restarting service process in 10 seconds.
2015/06/15 04:32:19.409330 Registrar received 21 events
2015/06/15 04:32:26 200 1.330331ms POST /api/metrics/store
I0615 04:32:26.972726 00001 controller.go:612] Starting service process.
I0615 04:32:26.972838 00001 instance.go:79] about to execute: /bin/sh , [-c exec /usr/bin/redis-server /etc/redis.conf][2]
I0615 04:32:26.982866 00001 controller.go:606] Restarting service process in 10 seconds.
W0615 04:32:26.997902 00001 controller.go:777] Health check metrics failed.
2015/06/15 04:32:29.408732 Registrar received 21 events

Any suggestion

Regards

D.

---

Subject:	Fixed collectorredis issue
Author:	[Not Specified]
Posted:	2015-07-06 23:46

We were having a very similar issue where the collectorredis service started failing seemingly out of nowhere after a fresh 5.0.3 install had been running fine for several weeks. As Danielezenoss posted above, we too were seeing the service failing continually due to the health check failing.

Following the suggestion above in this thread fixed the issue for us though... found the dump.rdb file and moved it out to another directory.... restarted the collectorredis service and viola! Everything was happy. Thanks for posting the fix :)

---

Subject:	Same Issue
Author:	[Not Specified]
Posted:	2015-09-23 10:28

I've been having a similar issue described by Danielezenoss above:

"I've a similar problem, but is Redis server that fails to start.
The reason why it doesn't start is about the metrics health check failure."

Mine keeps failing metrics and doesn't start. The logs just show that it keeps restarting the service procsess every 10 seconds.
Anyone else seen this before and can assist

---

Subject:	Unable to start REDIS (collectorredis) service since 5.03
Author:	[Not Specified]
Posted:	2015-12-10 05:01

Hi ,

Even i am facing the same issue. i have moved the dump file from /opt/serviced/var/volumes/volumeid/localhost_collectorredis and /opt/serviced/var/volumes/volumeid/redis/ and restarted the serviced and docker. But still getting the same issue redis is not starting up.

Looking for some solution.

Thanks,

Sunnybmv