TECHZEN Zenoss User Community ARCHIVE  

Error start serviced Zenoss5.3

Subject: Error start serviced Zenoss5.3
Author: Anderson Alves
Posted: 2018-02-23 08:51

Hello!
I can not start the serviced to proceed with the installation. I researched some posts and made some changes, but I could not solve them. Follows the service startup log.

Feb 23 10:20:32 [localhost] systemd: Starting Zenoss ServiceD...
Feb 23 10:20:32 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:32 UTC 2018: starting serviced daemon for 00000000 - waiting for docker
Feb 23 10:20:32 [localhost] serviced-systemd.sh: CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
Feb 23 10:20:32 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:32 UTC 2018: docker is now ready - done with pre-start
Feb 23 10:20:33 [localhost] serviced-systemd.sh: docker0: flags=4099<UP,BROADCAST,MULTICAST> mtu 1500
Feb 23 10:20:33 [localhost] serviced-systemd.sh: inet 172.17.0.1 netmask 255.255.0.0 broadcast 0.0.0.0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: ether 02:42:f7:33:86:6d txqueuelen 0 (Ethernet)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: RX packets 0 bytes 0 (0.0 B)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: RX errors 0 dropped 0 overruns 0 frame 0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: TX packets 0 bytes 0 (0.0 B)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: eno16777984: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
Feb 23 10:20:33 [localhost] serviced-systemd.sh: inet 10.1.4.62 netmask 255.255.0.0 broadcast 10.1.255.255
Feb 23 10:20:33 [localhost] serviced-systemd.sh: inet6 fe80::250:56ff:fea2:1c95 prefixlen 64 scopeid 0x20<link>
Feb 23 10:20:33 [localhost] serviced-systemd.sh: ether 00:50:56:a2:1c:95 txqueuelen 1000 (Ethernet)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: RX packets 1563264 bytes 120958869 (115.3 MiB)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: RX errors 8 dropped 20 overruns 0 frame 0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: TX packets 13132 bytes 3086778 (2.9 MiB)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
Feb 23 10:20:33 [localhost] serviced-systemd.sh: inet 127.0.0.1 netmask 255.0.0.0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: inet6 ::1 prefixlen 128 scopeid 0x10<host>
Feb 23 10:20:33 [localhost] serviced-systemd.sh: loop txqueuelen 1 (Loopback Local)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: RX packets 120 bytes 8948 (8.7 KiB)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: RX errors 0 dropped 0 overruns 0 frame 0
Feb 23 10:20:33 [localhost] serviced-systemd.sh: TX packets 120 bytes 8948 (8.7 KiB)
Feb 23 10:20:33 [localhost] serviced-systemd.sh: TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Feb 23 10:20:33 [localhost] systemd: Started Zenoss ServiceD.
Feb 23 10:20:33 [localhost] serviced: time="2018-02-23T13:20:33Z" level=warning msg="Using a non-recommended storage driver. Recommended configuration is devicemapper with an LVM thin pool" args= driver=btrfs location="storageoptions.go:90" logger=cli.api
Feb 23 10:20:33 [localhost] serviced: time="2018-02-23T13:20:33Z" level=fatal msg="Invalid host ID" error="not valid hostid: 00000000" hostid=00000000 location="daemon.go:281" logger=cli.api
Feb 23 10:20:33 [localhost] systemd: serviced.service: main process exited, code=exited, status=1/FAILURE
Feb 23 10:20:33 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:33 UTC 2018: post-stopping serviced daemon - waiting for serviced to stop
Feb 23 10:20:33 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:33 UTC 2018: waiting for serviced daemon to stop
Feb 23 10:20:33 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:33 UTC 2018: waiting for serviced to stop listening
Feb 23 10:20:33 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:33 UTC 2018: waiting for serviced isvcs to stop
Feb 23 10:20:33 [localhost] systemd: Unit serviced.service entered failed state.
Feb 23 10:20:33 [localhost] serviced-systemd.sh: Sex Fev 23 13:20:33 UTC 2018: serviced is now stopped - done with post-stop
Feb 23 10:20:33 [localhost] systemd: serviced.service failed.


Thanks.

------------------------------
Anderson Alves
------------------------------


Subject: RE: Error start serviced Zenoss5.3
Author: Arthur
Posted: 2018-02-23 15:43

Hi

The error is pointing to an invalid hostid. Please check/set your hostid. Page 36 step 8.

https://www.zenoss.com/sites/default/files/Control_Center_Installation_Guide_r1.4.2_d1320.17.331.pdf

------------------------------
Arthur
------------------------------


Subject: RE: Error start serviced Zenoss5.3
Author: Anderson Alves
Posted: 2018-02-26 13:53

Thank you very much for the attention, but I made a new installation using ISO and it is working without problems.
Now I'm looking at how to decrease memory consumption, it's too high.

------------------------------
Anderson Alves
------------------------------


Subject: RE: Error start serviced Zenoss5.3
Author: peterson lomotan
Posted: 2018-03-19 05:18

hello,
im having issue with the installation as well. but this time- the installation comes from the .ova file from the zenoss core link.

error="facade: service is missing an address assignment"

i just cant start zenoss v.5.3.0.


hostname: psbzcoremaster
Mar 19 17:02:33 psbzcoremaster serviced: time="2018-03-19T17:02:33Z" level=info msg="Started Facade.ScheduleService" autolaunch=true desiredstate=go location="service.go:1469" logger=facade serviceids=[bl9ev91ubuvz04401ihnc4ye6] synchronous=false tenantid=e98yal9yy48e89v44nuzqbxmp
Mar 19 17:02:33 psbzcoremaster serviced: time="2018-03-19T17:02:33Z" level=warning msg="Service failed validation for start" autolaunch=true desiredstate=go error="facade: service is missing an address assignment" location="service.go:1517" logger=facade serviceid=6gil8wqd8fb976kk7no7n2jy8 serviceids=[bl9ev91ubuvz04401ihnc4ye6] servicename=zensyslog synchronous=false tenantid=e98yal9yy48e89v44nuzqbxmp
Mar 19 17:02:33 psbzcoremaster serviced: time="2018-03-19T17:02:33Z" level=error msg="Could not retrieve service(s) for scheduling" autolaunch=true desiredstate=go error="facade: service is missing an address assignment" location="service.go:1537" logger=facade serviceids=[bl9ev91ubuvz04401ihnc4ye6] synchronous=false tenantid=e98yal9yy48e89v44nuzqbxmp
Mar 19 17:02:33 psbzcoremaster serviced: time="2018-03-19T17:02:33Z" level=warning msg="Starting Service(s)" action=start count=0 ids=bl9ev91ubuvz04401ihnc4ye6 success=false type=service user=ccuser
Mar 19 17:02:33 psbzcoremaster serviced: time="2018-03-19T17:02:33Z" level=error msg="Error starting service" error="facade: service is missing an address assignment" location="resources.go:659" logger=web serviceid=bl9ev91ubuvz04401ihnc4ye6
Mar 19 17:05:07 psbzcoremaster serviced: time="2018-03-19T17:05:07Z" level=info msg="Started Facade.ScheduleService" autolaunch=false desiredstate=go location="service.go:1469" logger=facade serviceids=[e98yal9yy48e89v44nuzqbxmp] synchronous=false tenantid=e98yal9yy48e89v44nuzqbxmp
Mar 19 17:05:07 psbzcoremaster serviced: time="2018-03-19T17:05:07Z" level=info msg="Starting Service(s)" action=start count=1 ids=e98yal9yy48e89v44nuzqbxmp success=true type=service user=ccuser

------------------------------
Best Regards,
Pete
PH
------------------------------


< Previous
API error (404):pull access denied for zenoss
  Next
Backup Zenoss core
>