---

Subject:	Hate to be the bearer of bad
Author:	[Not Specified]
Posted:	2015-10-07 19:40

Hate to be the bearer of bad news but I had the same experience (going from 5.0.3 -> 5.0.6). Everything was going fine until changing the docker storage driver. Afterwards nothing would start through control center, just hung starting. From looking through the logs it appeared as though control center/docker could no longer find my Zenoss containers.

I tried all sorts of things to try and fix it but eventually came to the conclusion it was dead and had to build a new 5.0.6 instance from scratch. ( http://www.zenoss.org/forum/135491 )

---

Subject:	5.0.6 recovered
Author:	[Not Specified]
Posted:	2015-10-08 08:29

I went to the folder (in my case, was under /root/5.0.x) where the upgrade script was run from. I then saw a txt file called upgrade.txt. When I edited that file, I found the following section:

# Choose image to upgrade to
SVC_USE zenoss/core_5.0:5.0.6
SVC_USE zenoss/hbase:v6.1
SVC_USE zenoss/opentsdb:v13

The opentsdb was remarked out (had a # sign in front of it) as per above. I removed the pound sign and reran the upgrade. Once completed, this recovered my Zenoss 5.0.6 and all services started with success. Hope you find this information helpful.

---

Subject:	5.0.6 recovered
Author:	[Not Specified]
Posted:	2015-10-08 08:40

I went to the folder (in my case, was under /root/5.0.x) where the upgrade script was run from. I then saw a txt file called upgrade.txt. When I edited that file, I found the following section:

# Choose image to upgrade to
SVC_USE zenoss/core_5.0:5.0.6
SVC_USE zenoss/hbase:v6.1
SVC_USE zenoss/opentsdb:v13

The opentsdb was remarked out (had a # sign in front of it) as per above. I removed the pound sign and reran the upgrade. Once completed, this recovered my Zenoss 5.0.6 and all services started with success. Hope you find this information helpful.