Closed matthiasg closed 8 years ago
just had the idea of running sdc-healthcheck again .. previously it always showed everything as status online, now it says cloudapi error, vmampi error,docker svc-err. these mostly vanished upon rebooting though.
that undoubtedly plays a part, just how to proceed ?
Ok docker has issues because svc:/manta/application/registrar:default is not running
[root@headnode (coal-1) ~]# svcs -x -z $(sdc-vmname docker)
svc:/smartdc/mdata:execute (Joyent SDC metadata handler)
Zone: 628f47a8-1e2a-473a-8262-15d50847e1ef
Alias: docker0
State: maintenance since January 22, 2016 06:54:54 AM UTC
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://illumos.org/msg/SMF-8000-KS
See: /zones/628f47a8-1e2a-473a-8262-15d50847e1ef/root/var/svc/log/smartdc-mdata:execute.log
Impact: 1 dependent service is not running. (Use -v for list.)
[root@headnode (coal-1) ~]# svcs -x -z $(sdc-vmname docker) -v
svc:/smartdc/mdata:execute (Joyent SDC metadata handler)
Zone: 628f47a8-1e2a-473a-8262-15d50847e1ef
Alias: docker0
State: maintenance since January 22, 2016 06:54:54 AM UTC
Reason: Start method exited with $SMF_EXIT_ERR_FATAL.
See: http://illumos.org/msg/SMF-8000-KS
See: /zones/628f47a8-1e2a-473a-8262-15d50847e1ef/root/var/svc/log/smartdc-mdata:execute.log
Impact: 1 dependent service is not running:
svc:/manta/application/registrar:default
in the docker zone it says:
2016-01-22T08:40:31Z] /opt/smartdc/boot/lib/util.sh:225: _sdc_enable_cron(): svccfg import /lib/svc/manifest/system/cron.xml
[2016-01-22T08:40:31Z] /opt/smartdc/boot/lib/util.sh:226: _sdc_enable_cron(): svcadm enable cron
[[2016-01-22T08:40:31Z] /opt/smartdc/boot/setup.sh:41: zonename
[2016-01-22T08:40:31Z] /opt/smartdc/boot/setup.sh:41: zfs set mountpoint=/data zones/628f47a8-1e2a-473a-8262-15d50847e1ef/data
cannot open 'zones/628f47a8-1e2a-473a-8262-15d50847e1ef/data': dataset does not exist
+ '[' 1 -gt 0 ']'
+ user_script_exit=95
+ exit 95
[ Jan 22 08:40:31 Method "start" exited with status 95. ]
zones/628f47a8-1e2a-473a-8262-15d50847e1ef
is the docker zone itself and in the global zone it does show the zones/628f47a8-1e2a-473a-8262-15d50847e1ef/data
folder (empty).
so now what ?
ok. had to run sdcadm experimental update-docker --servers cns,headnode
again (was already done more than once). this time it added the missing dataset for the mountpoint script. after rebooting the docker zone all services come up, the sdc-docker-setup.sh
script runs through correctly, the env.sh script exists and docker info
finally works ! yeah :)
i am going to repeat this setup procedure a few times on different machines because it seemed to me that there were a number of little issues which were only solved with retrying,re-running or rebooting the machine. hopefully the overall stability and reproducibility is not actually that bad.
i am trying to get Triton CoaL working but its quite the hassle :)
right now i am stuck at getting a connection to Docker.
At first i was just following https://www.joyent.com/blog/test-drive-joyents-elastic-container-infrastructure-for-docker but after the step
./docker-client-env root@10.88.88.200
i get this:export shows:
Then i followed the README in https://github.com/joyent/sdc-docker which i had used successfully on my other machines to connect to the joyent public cloud.
So i ran:
But the env file is not created (Edit: Its not created because an error is swallowed into /dev/null again in the script).
One more thing, the commands
return
unkown command
Can anybody tell me what steps to actually follow today ? or what i can diagnose to get this up ?