Skip to content

Instantly share code, notes, and snippets.

@zeevallin
Last active August 29, 2015 14:04
Show Gist options
  • Save zeevallin/3bfaeab64be389db1c3a to your computer and use it in GitHub Desktop.
Save zeevallin/3bfaeab64be389db1c3a to your computer and use it in GitHub Desktop.
Job deis-router@1.service loaded on 9eead0c3.../172.17.8.102
deis-builder-data.service already loaded. Skipping...
deis-database-data.service already loaded. Skipping...
deis-logger-data.service already loaded. Skipping...
deis-registry-data.service already loaded. Skipping...
fleetctl --strict-host-key-checking=false load logger/systemd/deis-logger.service cache/systemd/deis-cache.service database/systemd/deis-database.service
Job deis-cache.service loaded on cd056a02.../172.17.8.100
Job deis-logger.service loaded on 88e364b8.../172.17.8.101
Job deis-database.service loaded on 9eead0c3.../172.17.8.102
fleetctl --strict-host-key-checking=false load registry/systemd/*.service
Job deis-registry.service loaded on 88e364b8.../172.17.8.101
fleetctl --strict-host-key-checking=false load controller/systemd/*.service
Job deis-controller.service loaded on 88e364b8.../172.17.8.101
fleetctl --strict-host-key-checking=false load builder/systemd/*.service
Job deis-builder.service loaded on 88e364b8.../172.17.8.101
Deis components may take a long time to start the first time they are initialized.
Waiting for 1 of 1 deis-routers to start...
fleetctl --strict-host-key-checking=false start -no-block deis-router@1.service;
Triggered job deis-router@1.service start
Waiting for deis-cache to start...
fleetctl --strict-host-key-checking=false start -no-block logger/systemd/deis-logger.service cache/systemd/deis-cache.service database/systemd/deis-database.service
Triggered job deis-logger.service start
Triggered job deis-cache.service start
Triggered job deis-database.service start
Status: active (running)
Waiting for deis-registry to start...
fleetctl --strict-host-key-checking=false start -no-block registry/systemd/*.service
Triggered job deis-registry.service start
Status: activating (start-post)
Waiting for deis-controller to start...
fleetctl --strict-host-key-checking=false start -no-block controller/systemd/*.service
Triggered job deis-controller.service start
Status: active (running)
Waiting for deis-builder to start...
fleetctl --strict-host-key-checking=false start -no-block builder/systemd/*.service
Triggered job deis-builder.service start
One or more services failed! Check which services by running 'make status'
You can get detailed output with 'fleetctl status deis-servicename.service'
This usually indicates an error with Deis - please open an issue on GitHub or ask for help in IRC
● deis-builder.service - deis-builder
Loaded: loaded (/run/fleet/units/deis-builder.service; linked-runtime)
Active: activating (start-post) (Result: exit-code) since Sat 2014-08-02 00:49:36 UTC; 3min 1s ago
Process: 16793 ExecStopPost=/usr/bin/docker stop deis-builder (code=exited, status=1/FAILURE)
Process: 21480 ExecStart=/bin/sh -c IMAGE=`/run/deis/bin/get_image /deis/builder` && docker run --name deis-builder --rm -p 2223:22 -e HTTP_PROXY=$HTTP_PROXY -e http_proxy=$http_proxy -e HTTPS_PROXY=$HTTPS_PROXY -e https_proxy=$https_proxy -e ALL_PROXY=$ALL_PROXY -e all_proxy=$all_proxy -e NO_PROXY=$NO_PROXY -e no_proxy=$no_proxy -e PUBLISH=22 -e HOST=$COREOS_PRIVATE_IPV4 -e PORT=2223 --volumes-from deis-builder-data --privileged $IMAGE (code=exited, status=4)
Process: 21468 ExecStartPre=/bin/sh -c docker inspect deis-builder >/dev/null 2>&1 && docker rm -f deis-builder || true (code=exited, status=0/SUCCESS)
Process: 21444 ExecStartPre=/bin/sh -c IMAGE=`/run/deis/bin/get_image /deis/builder`; docker history $IMAGE >/dev/null 2>&1 || docker pull $IMAGE (code=exited, status=0/SUCCESS)
Main PID: 21480 (code=exited, status=4); : 21481 (sh)
CGroup: /system.slice/deis-builder.service
└─control
├─21481 /bin/sh -c echo 'Waiting for builder on 2223/tcp...' && until cat </dev/null>/dev/tcp/$COREOS_PRIVATE_IPV4/2223; do sleep 1; done
└─23944 sleep 1
Aug 02 00:52:32 deis-2 sh[21481]: /bin/sh: connect: Connection refused
Aug 02 00:52:32 deis-2 sh[21481]: /bin/sh: /dev/tcp/172.17.8.101/2223: Connection refused
Aug 02 00:52:33 deis-2 sh[21481]: /bin/sh: connect: Connection refused
Aug 02 00:52:33 deis-2 sh[21481]: /bin/sh: /dev/tcp/172.17.8.101/2223: Connection refused
Aug 02 00:52:34 deis-2 sh[21481]: /bin/sh: connect: Connection refused
Aug 02 00:52:34 deis-2 sh[21481]: /bin/sh: /dev/tcp/172.17.8.101/2223: Connection refused
Aug 02 00:52:35 deis-2 sh[21481]: /bin/sh: connect: Connection refused
Aug 02 00:52:35 deis-2 sh[21481]: /bin/sh: /dev/tcp/172.17.8.101/2223: Connection refused
Aug 02 00:52:36 deis-2 sh[21481]: /bin/sh: connect: Connection refused
Aug 02 00:52:36 deis-2 sh[21481]: /bin/sh: /dev/tcp/172.17.8.101/2223: Connection refused
fleetctl --strict-host-key-checking=false list-units --fields unit,state,load,active,sub,desc,machine
UNIT STATE LOAD ACTIVE SUB DESC MACHINE
deis-builder-data.service loaded loaded active exited deis-builder-data 88e364b8.../172.17.8.101
deis-builder.service launched loaded activating start-post deis-builder 88e364b8.../172.17.8.101
deis-cache.service launched loaded active running deis-cache cd056a02.../172.17.8.100
deis-controller.service launched loaded active running deis-controller 88e364b8.../172.17.8.101
deis-database-data.service loaded loaded active exited deis-database-data 9eead0c3.../172.17.8.102
deis-database.service launched loaded active running deis-database 9eead0c3.../172.17.8.102
deis-logger-data.service loaded loaded active exited deis-logger-data 88e364b8.../172.17.8.101
deis-logger.service launched loaded active running deis-logger 88e364b8.../172.17.8.101
deis-registry-data.service loaded loaded active exited deis-registry-data 88e364b8.../172.17.8.101
deis-registry.service launched loaded active running deis-registry 88e364b8.../172.17.8.101
deis-router@1.service launched loaded active running deis-router 9eead0c3.../172.17.8.102
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment