Control Center Issues

After stopping the zenoss services to install a zenpack, i was unable to restart the zenoss services successfully. I initiated a reboot of the control center server and after rebooting i was unable to start the serviced service. Docker service shows as started.

Here is the issues that is found in /var/log/upstart/serviced.log:

I0406 23:20:52.232243 04718 container.go:366] Starting isvc elasticsearch-logstash
I0406 23:20:52.232276 04718 container.go:366] Starting isvc logstash
I0406 23:20:52.232255 04718 container.go:366] Starting isvc zookeeper
I0406 23:20:52.232376 04718 container.go:366] Starting isvc opentsdb
I0406 23:20:52.232427 04718 container.go:366] Starting isvc celery
I0406 23:20:52.232429 04718 container.go:366] Starting isvc docker-registry
I0406 23:20:52.232478 04718 container.go:366] Starting isvc elasticsearch-serviced
I0406 23:20:52.234029 04718 container.go:257] Creating a new container for isvc serviced-isvcs_elasticsearch-logstash
I0406 23:20:52.234276 04718 container.go:257] Creating a new container for isvc serviced-isvcs_logstash
I0406 23:20:52.235401 04718 container.go:257] Creating a new container for isvc serviced-isvcs_opentsdb
I0406 23:20:52.236053 04718 container.go:257] Creating a new container for isvc serviced-isvcs_celery
I0406 23:20:52.236074 04718 container.go:257] Creating a new container for isvc serviced-isvcs_docker-registry
I0406 23:20:52.236269 04718 container.go:257] Creating a new container for isvc serviced-isvcs_elasticsearch-serviced
I0406 23:20:52.312773 04718 container.go:244] isvc serviced-isvcs_zookeeper found but not running; removing container cb7154d22cea0b030cc9e55c2d2accc09241fe549cf438ca066702d402e3294e
I0406 23:20:52.500401 04718 container.go:257] Creating a new container for isvc serviced-isvcs_zookeeper
E0406 23:20:53.018342 04718 manager.go:293] Error starting isvc logstash: No such container: e7703a19d9dc5d5f6f4bce59ded20f38a833812ac3c1879d0bdbe355e676f9db
E0406 23:20:53.019116 04718 manager.go:293] Error starting isvc elasticsearch-serviced: No such container: 2c9440c7bf0b7cfa43bdc8983549393f704b631094a23fa266799bd3dc20f1e2
E0406 23:20:53.019735 04718 manager.go:293] Error starting isvc opentsdb: No such container: e3d080b7db93d1b51e2fffe02ce530c17938962c1b250cb34f41fc8992cdc81f
E0406 23:20:53.020349 04718 manager.go:293] Error starting isvc elasticsearch-logstash: No such container: fdfc8959c51198b20804e42740e6dcdcf6fcda8038d2eb6b3b2fab1db7b697a1
E0406 23:20:53.055670 04718 manager.go:293] Error starting isvc docker-registry: No such container: e7a2f91b6eae0eadfec681c1f0ba1cefc4e6a3a4e3a16222fe1db905becb1499
E0406 23:20:53.057837 04718 manager.go:293] Error starting isvc celery: No such container: 06d22feab5c99d1fe1dd770de79ce75b2c14b57cbb4be468af16188d85ac0a92
E0406 23:20:53.404029 04718 manager.go:293] Error starting isvc zookeeper: No such container: 27cd251183906f87bccd33cc67df8a7f8d13017a4d5d884102c4d93e59219d92
F0406 23:20:53.404075 04718 daemon.go:143] Could not start isvcs: manager: could not start 7 isvcs
Mon Apr 6 16:20:53 PDT 2015: post-stopping serviced daemon - waiting for serviced to stop
Mon Apr 6 16:20:53 PDT 2015: waiting for serviced daemon to stop
Mon Apr 6 16:20:53 PDT 2015: waiting for serviced to stop listening
Mon Apr 6 16:20:53 PDT 2015: waiting for serviced isvcs to stop
Mon Apr 6 16:20:53 PDT 2015: serviced is now stopped - done with post-stop

Any help would be appreciated.

Regards,

Stefan