---

Subject:	It's strange that your
Author:	[Not Specified]
Posted:	2014-08-29 00:24

It's strange that your question shows partially in thread list in a popup but is empty here, must be something with forum engine.

Nevertheless I got the same issue - serviced starts and stops immidiately, in serviced.log

I0828 15:49:51.301763 01400 api.go:78] StartServer: [] (0)
I0828 15:49:51.389472 01400 manager.go:170] Looking for /opt/serviced/images/quay.io/zenossinc/isvcs/v10.tar.gz
I0828 15:49:51.389608 01400 manager.go:133] Loading docker image
F0828 15:49:51.422457 01400 daemon.go:111] exit status 1
Thu Aug 28 15:49:51 MSK 2014: waiting for serviced to stop
Thu Aug 28 15:49:51 MSK 2014: serviced is now stopped - done with post-stop

(i don't know where to look for more detailed logs)

So here we have an error - docker container is down and there's nothing to connect to:
could not create a client to the agent: dial tcp x.x.x.x:4979: connection refused

As I get it - something is with docker images.
Could someone confirm it
Should we use appliance download for now or is there a way to fix that error

---

Subject:	Same issue
Author:	[Not Specified]
Posted:	2014-08-29 07:18

This appears to be the same issue I have gotten post template deployment of the CORE. I usually get 20 minutes of up time before the services "crash" and I received that error.

---

Subject:	I am also consistently
Author:	[Not Specified]
Posted:	2014-08-29 19:23

I am also consistently getting this error on the "configuring the Zenoss Control Center master host" step. It worked last week on a different VM but I have been able to reproduce on a few new VMs I have spun up.