Zenoss ZenTech Community

Hi Team, Zenoss ServiceD unable to start in centos 7. Here is the output and /var/log/messages. Could you please help us to start the serviceD. Not able to get which is causing the issue

systemctl status serviced
serviced.service - Zenoss ServiceD
Loaded: loaded (/usr/lib/systemd/system/serviced.service; enabled)
Active: failed (Result: exit-code) since Mon 2015-04-20 04:39:44 EDT; 28min ago
Process: 9832 ExecStopPost=/opt/serviced/bin/serviced-systemd.sh post-stop (code=exited, status=0/SUCCESS)
Process: 8969 ExecStart=/opt/serviced/bin/serviced (code=exited, status=255)
Process: 8958 ExecStartPre=/opt/serviced/bin/serviced-systemd.sh pre-start (code=exited, status=0/SUCCESS)
Main PID: 8969 (code=exited, status=255)

Apr 20 04:39:04 hostnameserviced-systemd.sh[9832]: Mon Apr 20 08:39:04 UTC 2015: post-stopping serviced daemon - waiting for serviced to stop
Apr 20 04:39:04 hostnameserviced-systemd.sh[9832]: Mon Apr 20 08:39:04 UTC 2015: waiting for serviced daemon to stop
Apr 20 04:39:04 hostnameserviced-systemd.sh[9832]: Mon Apr 20 08:39:04 UTC 2015: waiting for serviced to stop listening
Apr 20 04:39:04 hostnameserviced-systemd.sh[9832]: Mon Apr 20 08:39:04 UTC 2015: waiting for serviced isvcs to stop
Apr 20 04:39:14 hostnameserviced-systemd.sh[9832]: afeb89b343f6683f4d2e0e0993023e9bc9f05042cca6474ee245f4ec9e9cce5f
Apr 20 04:39:24 hostnameserviced-systemd.sh[9832]: a4516b77282c71da074ad26d98b94e3a5822b7185e2e95d944b1ed77dff31449
Apr 20 04:39:34 hostnameserviced-systemd.sh[9832]: 602f7b35af28b863495a3c08cfe93901166b1c52e7edce9eb49267a4220ae44f
Apr 20 04:39:44 hostnameserviced-systemd.sh[9832]: 329a8e29253aa2d2f53601b8d6fa0e543dc3216726e71bb2b5f6bb7984692ae4
Apr 20 04:39:44 hostnameserviced-systemd.sh[9832]: Mon Apr 20 08:39:44 UTC 2015: serviced is now stopped - done with post-stop
Apr 20 04:39:44 hostnamesystemd[1]: Unit serviced.service entered failed state.

----------------------------------------------------------------------------------------------------------------------

Subject:	Errors from /var/log/messages
Author:	[Not Specified]
Posted:	2015-04-20 04:34

Errors from /var/log/messages

Apr 20 05:15:09 hostname docker: time="2015-04-20T05:15:09-04:00" level="error" msg="Handler for GET /containers/{name:.*}/json returned error: No such container: serviced-isvcs_docker-registry"
Apr 20 05:15:09 hostname docker: time="2015-04-20T05:15:09-04:00" level="error" msg="HTTP Error: statusCode=404 No such container: serviced-isvcs_docker-registry"
Apr 20 05:15:09 hostname docker: time="2015-04-20T05:15:09-04:00" level="error" msg="Handler for GET /containers/{name:.*}/json returned error: No such container: serviced-isvcs_elasticsearch-serviced"
Apr 20 05:15:09 hostname docker: time="2015-04-20T05:15:09-04:00" level="error" msg="HTTP Error: statusCode=404 No such container: serviced-isvcs_elasticsearch-serviced"
Apr 20 05:15:15 hostname NetworkManager[818]: [1429521315.689188] [platform/nm-linux-platform.c:1841] link_change(): Netlink error changing link (invalid link 0x7f50cea14280): No such device
Apr 20 05:15:17 hostname NetworkManager[818]: [1429521317.856940] [platform/nm-linux-platform.c:1841] link_change(): Netlink error changing link (invalid link 0x7f50cea19610): No such device
Apr 20 05:15:18 hostname NetworkManager[818]: [1429521318.348721] [platform/nm-linux-platform.c:1841] link_change(): Netlink error changing link (invalid link 0x7f50cea34620): No such device
Apr 20 05:15:19 hostname NetworkManager[818]: [1429521319.061616] [platform/nm-linux-platform.c:1841] link_change(): Netlink error changing link (invalid link 0x7f50cea4e730): No such device
Apr 20 05:16:31 hostname serviced: E0420 09:16:31.400054 10901 manager.go:293] Error starting isvc docker-registry: could not startup docker-registry container
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Apr 20 05:25:16 hostname docker: time="2015-04-20T05:25:16-04:00" level="info" msg="+job stop(15c85f2a658d51b5c0a4f431a6d35fbf481da2b1aeebcc912a77ed1a2c86ca85)"
Apr 20 05:25:17 hostname docker: time="2015-04-20T05:25:17-04:00" level="info" msg="GET /containers/serviced-isvcs_logstash/json"
Apr 20 05:25:17 hostname docker: time="2015-04-20T05:25:17-04:00" level="info" msg="+job container_inspect(serviced-isvcs_logstash)"
Apr 20 05:25:17 hostname docker: time="2015-04-20T05:25:17-04:00" level="info" msg="-job container_inspect(serviced-isvcs_logstash) = OK (0)"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="GET /containers/serviced-isvcs_opentsdb/json"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="+job container_inspect(serviced-isvcs_opentsdb)"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="-job container_inspect(serviced-isvcs_opentsdb) = OK (0)"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="GET /containers/serviced-isvcs_elasticsearch-logstash/json"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="+job container_inspect(serviced-isvcs_elasticsearch-logstash)"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="-job container_inspect(serviced-isvcs_elasticsearch-logstash) = OK (0)"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="POST /containers/b81152488ba303ef91a8390a154380ac50f8ef7c50f5875009a3e564591
84d56/stopt=45"
Apr 20 05:25:18 hostname docker: time="2015-04-20T05:25:18-04:00" level="info" msg="+job stop(b81152488ba303ef91a8390a154380ac50f8ef7c50f5875009a3e56459184d56)"
Apr 20 05:25:19 hostname docker: time="2015-04-20T05:25:19-04:00" level="info" msg="GET /containers/serviced-isvcs_celery/json"
Apr 20 05:25:19 hostname docker: time="2015-04-20T05:25:19-04:00" level="info" msg="+job container_inspect(serviced-isvcs_celery)"
Apr 20 05:25:19 hostname docker: time="2015-04-20T05:25:19-04:00" level="info" msg="-job container_inspect(serviced-isvcs_celery) = OK (0)"
Apr 20 05:25:21 hostname docker: time="2015-04-20T05:25:21-04:00" level="info" msg="GET /containers/serviced-isvcs_zookeeper/json"
Apr 20 05:25:21 hostname docker: time="2015-04-20T05:25:21-04:00" level="info" msg="+job container_inspect(serviced-isvcs_zookeeper)"
Apr 20 05:25:21 hostname docker: time="2015-04-20T05:25:21-04:00" level="info" msg="-job container_inspect(serviced-isvcs_zookeeper) = OK (0)"
Apr 20 05:25:27 hostname docker: time="2015-04-20T05:25:27-04:00" level="info" msg="GET /containers/serviced-isvcs_logstash/json"
Apr 20 05:25:27 hostname docker: time="2015-04-20T05:25:27-04:00" level="info" msg="+job container_inspect(serviced-isvcs_logstash)"
Apr 20 05:25:27 hostname docker: time="2015-04-20T05:25:27-04:00" level="info" msg="-job container_inspect(serviced-isvcs_logstash) = OK (0)"
Apr 20 05:25:28 hostname docker: time="2015-04-20T05:25:28-04:00" level="info" msg="GET /containers/serviced-isvcs_opentsdb/json"
Apr 20 05:25:28 hostname docker: time="2015-04-20T05:25:28-04:00" level="info" msg="+job container_inspect(serviced-isvcs_opentsdb)"
Apr 20 05:25:28 hostname docker: time="2015-04-20T05:25:28-04:00" level="info" msg="-job container_inspect(serviced-isvcs_opentsdb) = OK (0)"
Apr 20 05:25:29 hostname docker: time="2015-04-20T05:25:29-04:00" level="info" msg="GET /containers/serviced-isvcs_celery/json"
Apr 20 05:25:29 hostname docker: time="2015-04-20T05:25:29-04:00" level="info" msg="+job container_inspect(serviced-isvcs_celery)"
Apr 20 05:25:29 hostname docker: time="2015-04-20T05:25:29-04:00" level="info" msg="-job container_inspect(serviced-isvcs_celery) = OK (0)"
Apr 20 05:25:31 hostname dhclient[12215]: DHCPDISCOVER on veth9a97538 to 255.255.255.255 port 67 interval 16 (xid=0x30f9debb)
Apr 20 05:25:31 hostname NetworkManager: DHCPDISCOVER on veth9a97538 to 255.255.255.255 port 67 interval 16 (xid=0x30f9debb)
Apr 20 05:25:31 hostname docker: time="2015-04-20T05:25:31-04:00" level="info" msg="GET /containers/serviced-isvcs_zookeeper/json"
Apr 20 05:25:31 hostname docker: time="2015-04-20T05:25:31-04:00" level="info" msg="+job container_inspect(serviced-isvcs_zookeeper)"
Apr 20 05:25:31 hostname docker: time="2015-04-20T05:25:31-04:00" level="info" msg="-job container_inspect(serviced-isvcs_zookeeper) = OK (0)"
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): DHCPv4 request timed out.
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): canceled DHCP transaction, DHCP client pid 12215
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 4 of 5 (IPv4 Configure Timeout) started...
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) failed for connection 'Wired connection 2'
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): deactivating device (reason 'none') [0]
Apr 20 05:25:34 hostname NetworkManager[818]: Auto-activating connection 'Wired connection 2'.
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) starting connection 'Wired connection 2'
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 1 of 5 (Device Prepare) scheduled...
Apr 20 05:25:34 hostname avahi-daemon[809]: Withdrawing address record for fe80::742d:49ff:fe4d:a662 on veth9a97538.
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 1 of 5 (Device Prepare) started...
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): device state change: disconnected -> prepare (reason 'none') [30 40 0]
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 2 of 5 (Device Configure) scheduled...
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 1 of 5 (Device Prepare) complete.
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 2 of 5 (Device Configure) starting...
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): device state change: prepare -> config (reason 'none') [40 50 0]
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 2 of 5 (Device Configure) successful.
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 2 of 5 (Device Configure) complete.
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 3 of 5 (IP Configure Start) started...
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): device state change: config -> ip-config (reason 'none') [50 70 0]
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Beginning DHCPv4 transaction (timeout in 45 seconds)
Apr 20 05:25:34 hostname NetworkManager[818]: dhclient started with pid 12586
Apr 20 05:25:34 hostname NetworkManager[818]: Activation (veth9a97538) Stage 3 of 5 (IP Configure Start) complete.
Apr 20 05:25:34 hostname dhclient[12586]: Internet Systems Consortium DHCP Client 4.2.5
Apr 20 05:25:34 hostname dhclient[12586]: Copyright 2004-2013 Internet Systems Consortium.
Apr 20 05:25:34 hostname dhclient[12586]: All rights reserved.
Apr 20 05:25:34 hostname dhclient[12586]: For info, please visit https://www.isc.org/software/dhcp/
Apr 20 05:25:34 hostname dhclient[12586]:
Apr 20 05:25:34 hostname NetworkManager: Internet Systems Consortium DHCP Client 4.2.5
Apr 20 05:25:34 hostname NetworkManager: Copyright 2004-2013 Internet Systems Consortium.
Apr 20 05:25:34 hostname NetworkManager: All rights reserved.
Apr 20 05:25:34 hostname NetworkManager: For info, please visit https://www.isc.org/software/dhcp/
Apr 20 05:25:34 hostname dhclient[12586]: Listening on LPF/veth9a97538/76:2d:49:4d:a6:62
Apr 20 05:25:34 hostname dhclient[12586]: Sending on LPF/veth9a97538/76:2d:49:4d:a6:62
Apr 20 05:25:34 hostname dhclient[12586]: Sending on Socket/fallback
Apr 20 05:25:34 hostname dhclient[12586]: DHCPDISCOVER on veth9a97538 to 255.255.255.255 port 67 interval 4 (xid=0x7c5157b9)
Apr 20 05:25:34 hostname NetworkManager[818]: (veth9a97538): DHCPv4 state changed nbi -> preinit
Apr 20 05:25:34 hostname NetworkManager: Listening on LPF/veth9a97538/76:2d:49:4d:a6:62
Apr 20 05:25:34 hostname NetworkManager: Sending on LPF/veth9a97538/76:2d:49:4d:a6:62
Apr 20 05:25:34 hostname NetworkManager: Sending on Socket/fallback
Apr 20 05:25:34 hostname NetworkManager: DHCPDISCOVER on veth9a97538 to 255.255.255.255 port 67 interval 4 (xid=0x7c5157b9)
Apr 20 05:25:35 hostname ntpd[1239]: Deleting interface #14 veth9a97538, fe80::742d:49ff:fe4d:a662#123, interface stats: received=0, sent=0, dropped=0, active_t
ime=43 secs
Apr 20 05:25:35 hostname avahi-daemon[809]: Registering new address record for fe80::742d:49ff:fe4d:a662 on veth9a97538.*.
Apr 20 05:25:37 hostname ntpd[1239]: Listen normally on 15 veth9a97538 fe80::742d:49ff:fe4d:a662 UDP 123
Apr 20 05:26:13 hostname docker: time="2015-04-20T05:26:13-04:00" level="info" msg="-job release_interface(55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc09
0a6233c73e8) = OK (0)"
Apr 20 05:26:13 hostname docker: time="2015-04-20T05:26:13-04:00" level="info" msg="+job log(stop, 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c7
3e8, zenoss/serviced-isvcs:v26)"
Apr 20 05:26:13 hostname docker: time="2015-04-20T05:26:13-04:00" level="info" msg="-job log(stop, 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c7
3e8, zenoss/serviced-isvcs:v26) = OK (0)"
Apr 20 05:26:13 hostname docker: time="2015-04-20T05:26:13-04:00" level="info" msg="-job stop(55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c73e8)
= OK (0)"
Apr 20 05:26:13 hostname docker: write unix @: broken pipe
Apr 20 05:26:13 hostname docker: time="2015-04-20T05:26:13-04:00" level="info" msg="-job events() = ERR (1)"
Apr 20 05:26:14 hostname docker: time="2015-04-20T05:26:13-04:00" level="error" msg="Handler for GET /events returned error: write unix @: broken pipe"
Apr 20 05:26:14 hostname docker: time="2015-04-20T05:26:13-04:00" level="error" msg="HTTP Error: statusCode=500 write unix @: broken pipe"
Apr 20 05:26:14 hostname docker: 2015/04/20 05:26:13 http: multiple response.WriteHeader calls
Apr 20 05:26:14 hostname serviced-systemd.sh: 55a6695bad2111e294cdc5e49f25dd82fda7b254c24c00841cc090a6233c73e8
Apr 20 05:26:14 hostname docker: time="2015-04-20T05:26:14-04:00" level="info" msg="POST /v1.17/containers/c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb
97892015059/stopt=10"
Apr 20 05:26:14 hostname docker: time="2015-04-20T05:26:14-04:00" level="info" msg="+job stop(c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059)"
Apr 20 05:26:16 hostname dhclient[12586]: DHCPDISCOVER on veth9a97538 to 255.255.255.255 port 67 interval 12 (xid=0x7c5157b9)
Apr 20 05:26:16 hostname NetworkManager: DHCPDISCOVER on veth9a97538 to 255.255.255.255 port 67 interval 12 (xid=0x7c5157b9)
Apr 20 05:26:19 hostname NetworkManager[818]: (veth9a97538): DHCPv4 request timed out.
Apr 20 05:26:19 hostname NetworkManager[818]: (veth9a97538): canceled DHCP transaction, DHCP client pid 12586
Apr 20 05:26:19 hostname NetworkManager[818]: Activation (veth9a97538) Stage 4 of 5 (IPv4 Configure Timeout) scheduled...
Apr 20 05:26:19 hostname NetworkManager[818]: Activation (veth9a97538) Stage 4 of 5 (IPv4 Configure Timeout) started...
Apr 20 05:26:19 hostname NetworkManager[818]: (veth9a97538): device state change: ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
Apr 20 05:26:19 hostname NetworkManager[818]: Disabling autoconnect for connection 'Wired connection 2'.
Apr 20 05:26:19 hostname NetworkManager[818]: Activation (veth9a97538) failed for connection 'Wired connection 2'
Apr 20 05:26:19 hostname NetworkManager[818]: Activation (veth9a97538) Stage 4 of 5 (IPv4 Configure Timeout) complete.
Apr 20 05:26:19 hostname NetworkManager[818]: (veth9a97538): device state change: failed -> disconnected (reason 'none') [120 30 0]
Apr 20 05:26:19 hostname NetworkManager[818]: (veth9a97538): deactivating device (reason 'none') [0]
Apr 20 05:26:19 hostname avahi-daemon[809]: Withdrawing address record for fe80::742d:49ff:fe4d:a662 on veth9a97538.
Apr 20 05:26:20 hostname ntpd[1239]: Deleting interface #15 veth9a97538, fe80::742d:49ff:fe4d:a662#123, interface stats: received=0, sent=0, dropped=0, active_t
ime=43 secs
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="Container c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059 f
ailed to exit within 10 seconds of SIGTERM - using the force"
Apr 20 05:26:24 hostname kernel: docker0: port 3(veth9a97538) entered disabled state
Apr 20 05:26:24 hostname NetworkManager[818]: (veth9a97538): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Apr 20 05:26:24 hostname avahi-daemon[809]: Withdrawing workstation service for veth9a97538.
Apr 20 05:26:24 hostname kernel: device veth9a97538 left promiscuous mode
Apr 20 05:26:24 hostname kernel: docker0: port 3(veth9a97538) entered disabled state
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="+job log(die, c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb978920150
59, zenoss/serviced-isvcs:v26)"

Apr 20 05:26:24 hostname NetworkManager[818]: (docker0): link disconnected (deferring action for 4 seconds)
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="-job release_interface(c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059) = OK (0)"
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="+job log(stop, c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059, zenoss/serviced-isvcs:v26)"
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="-job log(stop, c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059, zenoss/serviced-isvcs:v26) = OK (0)"
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="-job stop(c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059) = OK (0)"
Apr 20 05:26:24 hostname serviced-systemd.sh: c6ee9fd026230a94f22c147dfc8219d931aadac169195c7a89ddb97892015059
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="POST /v1.17/containers/dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab/stopt=10"
Apr 20 05:26:24 hostname docker: time="2015-04-20T05:26:24-04:00" level="info" msg="+job stop(dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab)"
Apr 20 05:26:28 hostname NetworkManager[818]: (docker0): link disconnected (calling deferred action)
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="Container dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab failed to exit within 10 seconds of SIGTERM - using the force"
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="+job log(die, dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab, zenoss/serviced-isvcs:v26)"
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="-job log(die, dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab, zenoss/serviced-isvcs:v26) = OK (0)"
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="+job log(stop, dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab, zenoss/serviced-isvcs:v26)"
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="-job log(stop, dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab, zenoss/serviced-isvcs:v26) = OK (0)"
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="-job stop(dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab) = OK (0)"
Apr 20 05:26:34 hostname serviced-systemd.sh: dc8491bd3f1464fcff5d32abd6833fe9e8bcc7fd8ee80e8530b82ad7a20fd2ab
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="POST /v1.17/containers/006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa/stopt=10"
Apr 20 05:26:34 hostname docker: time="2015-04-20T05:26:34-04:00" level="info" msg="+job stop(006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa)"
Apr 20 05:26:42 hostname docker: time="2015-04-20T05:26:42-04:00" level="info" msg="+job log(die, 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa, zenoss/serviced-isvcs:v26)"
Apr 20 05:26:42 hostname docker: time="2015-04-20T05:26:42-04:00" level="info" msg="-job log(die, 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa, zenoss/serviced-isvcs:v26) = OK (0)"
Apr 20 05:26:42 hostname docker: time="2015-04-20T05:26:42-04:00" level="info" msg="+job log(stop, 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa, zenoss/serviced-isvcs:v26)"
Apr 20 05:26:42 hostname docker: time="2015-04-20T05:26:42-04:00" level="info" msg="-job log(stop, 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa, zenoss/serviced-isvcs:v26) = OK (0)"
Apr 20 05:26:42 hostname docker: time="2015-04-20T05:26:42-04:00" level="info" msg="-job stop(006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa) = OK (0)"
Apr 20 05:26:42 hostname serviced-systemd.sh: 006e2fd3da3e2218f05c88339c7227058008377f0a3120fee32c8efd7045a3fa
Apr 20 05:26:42 hostname serviced-systemd.sh: Mon Apr 20 09:26:42 UTC 2015: serviced is now stopped - done with post-stop
Apr 20 05:26:42 hostname systemd: Unit serviced.service entered failed state.

Subject:	You have provided short log
Author:	Jan Garaj
Posted:	2015-04-20 04:51

Apr 20 05:15:19 hostname NetworkManager[818]: [1429521319.061616] [platform/nm-linux-platform.c:1841] link_change(): Netlink error changing link (invalid link 0x7f50cea4e730): No such device
Apr 20 05:16:31 hostname serviced: E0420 09:16:31.400054 10901 manager.go:293] Error starting isvc docker-registry: could not startup docker-registry container

=> maybe some network issue. Did you follow installation guide

Devops Monitoring Expert advice: Dockerize/automate/monitor all the things.

DevOps stack: Docker / Kubernetes / Mesos / Zabbix / Zenoss / Grafana / Puppet / Ansible / Vagrant / Terraform / Elasticsearch

Subject:	Hi I followed the
Author:	[Not Specified]
Posted:	2015-04-20 06:37

Hi I followed the installation guide. Not sure how to fix this
https://beta.zenoss.io/Core-5-Beta-3/Documentation/Zenoss_Core_Beta_Inst...
when i started serviced its creating the below interfaces.

veth2229db8: flags=67 mtu 1500
ether 22:ab:8f:b8:59:da txqueuelen 0 (Ethernet)
RX packets 8 bytes 648 (648.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 1728 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth38957f3: flags=67 mtu 1500
ether 02:59:f4:4b:7f:8c txqueuelen 0 (Ethernet)
RX packets 8 bytes 648 (648.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 13 bytes 1010 (1010.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth68bcab8: flags=67 mtu 1500
ether 7a:d8:b3:12:f2:7d txqueuelen 0 (Ethernet)
RX packets 12 bytes 840 (840.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 22 bytes 1660 (1.6 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

veth8ab841b: flags=4163 mtu 1500
inet6 fe80::58af:6cff:fe7d:82c1 prefixlen 64 scopeid 0x20
ether 5a:af:6c:7d:82:c1 txqueuelen 0 (Ethernet)
RX packets 8 bytes 648 (648.0 B)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 14 bytes 1884 (1.8 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0

Getting the error incmd : journalctl -u serviced -f
E0420 11:33:31.087346 18872 manager.go:293] Error starting isvc docker-registry: could not start...ontainer
can you help me to fix this

Regards,
Satya

Subject:	I tried to install through
Author:	[Not Specified]
Posted:	2015-04-20 07:27

I tried to install through Autodeploy script. Getting the errors any idea.
Output of Autodeploy script :
3.9 Start the Control Center service
systemctl enable serviced && systemctl start serviced
Done
4 Zenoss Core 5 deployement - (Mon, 20 Apr 2015 08:11:19 -0400)
4.1 Adding current host to the default resource pool
Please be patient, because docker image zenoss/serviced-isvcs must be downloaded before first start.
You can check progress in new console: journalctl -u serviced -f -a
Script is trying to check status every 10s. Timeout for this step is 15 minutes.
serviced host list 2>&1
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#1: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#2: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#3: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#4: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#5: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#6: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
.
.
rpc: can't find service Master.GetHosts
#64: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#65: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
rpc: can't find service Master.GetHosts
#66: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#67: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#68: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#69: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#70: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#71: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused
#72: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
could not create a client to the master: dial tcp X.X.X.X:4979: connection refused

Subject:	Please don't use beta
Author:	Jan Garaj
Posted:	2015-04-20 08:23

Please don't use beta documentation.

Autodeploy script - follow provided instructions - patient is the key.
If you want to report any auto deploy script issue, than pls provide full autodeploy log.

If you have still problem with autodeploy, please follow official installation http://wiki.zenoss.org/Install_Zenoss

Subject:	Hi Here is the output of Auto
Author:	[Not Specified]
Posted:	2015-04-21 01:51

Hi Here is the output of Auto deploy script and journalctl.

Auto deploy script output : http://pastebin.com/xcpAgcz3
Auto deploy script Path : https://github.com/jangaraj/zenoss5-core-autodeploy/blob/master/README.md
journalctl Output : http://pastebin.com/ymGjcu8A

Subject:	>1.4 CPU check
Author:	Jan Garaj
Posted:	2015-04-21 03:08

>1.4 CPU check
>Only 1 CPUs have been detected, but at least 4 are required. Do you want to continue (y/n)
>y
>... continuing
>1.6 / filesystem check
>/ filesystem size is less than required 30GB. Do you want to continue (y/N)
>y
>... continuing
>1.10 /opt/serviced/var/backups filesystem check
>/opt/serviced/var/backups filesystem was not detected
>Do you want to continue (y/n)
>y
>... continuing
Why did you continue

> Apr 21 02:15:31 hostnameserviced[4234]: E0421 06:15:31.122472 04234 manager.go:293] Error starting isvc elasticsearch-serviced: Could not...ut:10m0s
Output is truncated, pls use -a parameter also: journalctl -u systemd -f -a
=> systemd internal services are not able to start

Subject:	journalctl output
Author:	[Not Specified]
Posted:	2015-04-21 04:08

Hi we try to install and check how its working thats why we have continued with Y for hardware while installing.
We want to see the installation process and deployment for testing zenoss 5 version.
Please help me to fix this and continue the installation process forward.

Here is the journalctl output with -a.

journalctl output :
http://pastebin.com/KYZwqPv9

Subject:	Diplomatic note: it's
Author:	Jan Garaj
Posted:	2015-04-21 12:40

Diplomatic note: it's interesting attempt, Zenoss 5 installation on 1vCPU machine
My note: it's a wasting of time to investigate your issue on your current 1CPU machine, start of Zenoss 5 can generate load 50 on 12vCPU machine

Follow the installation manual and you will learn more about Zenoss installation process.

Subject:	issues with installing Zenoss 5.0
Author:	[Not Specified]
Posted:	2015-04-21 12:56

repo doesn't seems to have correct URL..
--------------------------------
http://get.zenoss.io/yum/zenoss/stable/centos/el7/os/x86_64/repodata/rep... [Errno 14] curl#6 - "Could not resolve host: get.zenoss.io; Name or service not known"
Trying other mirror.
---------------------------------

Subject:	@arutovsky it's a problem of
Author:	Jan Garaj
Posted:	2015-04-21 16:05

@arutovsky it's a problem of your DNS config:

-bash-3.2$ nslookup get.zenoss.io
Server: 127.0.0.1
Address: 127.0.0.1#53

Non-authoritative answer:
get.zenoss.io canonical name = get.zenoss.io.s3-website-us-east-1.amazonaws.com.
get.zenoss.io.s3-website-us-east-1.amazonaws.com canonical name = s3-website-us-east-1.amazonaws.com.
Name: s3-website-us-east-1.amazonaws.com
Address: 54.231.17.60

Subject:	DNS issue
Author:	[Not Specified]
Posted:	2015-04-21 22:30

you right for some reason my server would not resolve the domain, but would it be a solution to add it to hosts file beside that have no problems with DNS at all, not sure what exactly is happening..

thank you for your help!!!

Subject:	Yes, you can update your
Author:	Jan Garaj
Posted:	2015-04-22 00:42

Yes, you can update your hosts file. However the better solution is to resolve DNS issue to prevent future problems. It's AWS S3 service and AWS uses (geo) DNS load balancing and TTL is very low - 60 -> AWS can completely change IP in one minute.

"dig s3-website-us-east-1.amazonaws.com" outputs - 4 seconds diff:
s3-website-us-east-1.amazonaws.com. 1 IN A 54.231.9.116
s3-website-us-east-1.amazonaws.com. 3 IN A 54.231.14.252

Subject:	the issue seems to be on my
Author:	[Not Specified]
Posted:	2015-04-22 07:26

the issue seems to be on my ISP provider side as in the second location with same configuration i place no problems..

Subject:	right now I'm getting this:
Author:	[Not Specified]
Posted:	2015-04-22 07:28

right now I'm getting this:
-----------------------------------
#61: This is not a problem, because Control Centre service is not fully started, I'm trying in 10 seconds
-----------------------------------
is this also DNS related issue

Subject:	at the end I got this:
Author:	[Not Specified]
Posted:	2015-04-22 07:53

at the end I got this:
------------------------------
Problem with adding a host - check output from test: could not create a client to the master: dial tcp 10.11.11.165:4979: connection refused
-----------------------------
Firewall is completely disabled and SElinux too..

Subject:	thank you for all your help!
Author:	[Not Specified]
Posted:	2015-04-22 08:29

thank you for all your help! seems like all was DNS related.. got successful install now :)

Subject:	Hi jan i have increased the
Author:	[Not Specified]
Posted:	2015-04-22 09:12

Hi jan i have increased the HW and tried to install but not succeed. Here i am providing the output of script and journalctl.
Please help me what was the cause.
Added the host in DNS entry and host is resolving with out any issue.

script output : http://pastebin.com/AR393hqy
journalctrl output : http://pastebin.com/WwCtpyqx

Manually started the serviced and here is the output for journalctrl:

http://pastebin.com/ciSn9xtU

Subject:	sorry but got something else.
Author:	[Not Specified]
Posted:	2015-04-22 09:45

sorry but got something else.. logs are saying:"Set password for Control Center ccuser user: passwd ccuser. Please visit Control Center https://zenoss/ in your favorite web browser to complete setup, log in with ccuser user" but it does not accept the username and password.. anything I can do with that

Subject:	I was getting this error while trying to start serviced.
Author:	[Not Specified]
Posted:	2015-12-17 16:32

ExecStart=/opt/serviced/bin/serviced (code=exited, status=255).

Subject:	Zenoss 5 : Zenoss ServiceD unable to start in centos 7
Author:	[Not Specified]
Posted:	2015-04-20 04:22

Zenoss 5 : Zenoss ServiceD unable to start in centos 7