errordeveloper / weave-demos

Weave Demos
http://blog.weave.works/author/errordeveloper/
Other
61 stars 12 forks source link

weave-demos/coreos-azure: CoreOS Failed Units #9

Closed v1k0d3n closed 8 years ago

v1k0d3n commented 8 years ago

I'm receiving an error after following the instructions about failed units on the master (3) and on the minion/nodes (1); just wanted to give you a heads up, and determine if this is just on my end, or if there's another deeper issue occurring.

For the master (with first login):

Last login: Mon Dec  7 06:36:18 2015 from 172.72.12.150
CoreOS stable (557.2.0)
Failed Units: 3
  docker.service
  weave-create-bridge.service
  docker.socket

Digging further into the issue:

core@kube-00 ~ $ sudo su -
kube-00 ~ # systemctl status weave
● weave.service - Weave Network Router
   Loaded: loaded (/etc/systemd/system/weave.service; enabled; vendor preset: disabled)
   Active: inactive (dead) (Result: exit-code) since Mon 2015-12-07 06:03:05 UTC; 10h ago
     Docs: http://zettio.github.io/weave/
  Process: 830 ExecStartPre=/usr/bin/docker pull zettio/weave:latest (code=exited, status=1/FAILURE)

Dec 07 06:03:05 kube-00 systemd[1]: Dependency failed for Weave Network Router.
Dec 07 06:03:05 kube-00 systemd[1]: Job weave.service/start failed with result 'dependency'.
Dec 07 06:03:05 kube-00 systemd[1]: weave.service: control process exited, code=exited status=1
Dec 07 06:03:05 kube-00 systemd[1]: Unit weave.service entered failed state.
Dec 07 06:03:05 kube-00 systemd[1]: weave.service failed.
Dec 07 06:03:05 kube-00 docker[830]: time="2015-12-07T06:03:05Z" level="fatal" msg="Post http:///var/run/docker.sock/v1.16/images/create?fromImage=zettio%2Fweave%3Alatest: read unix /var/run/docker.sock: connection reset by peer"
Dec 07 06:03:05 kube-00 systemd[1]: weave.service holdoff time over, scheduling restart.
Dec 07 06:03:05 kube-00 systemd[1]: Stopping Weave Network Router...
Dec 07 06:03:05 kube-00 systemd[1]: Dependency failed for Weave Network Router.
Dec 07 06:03:05 kube-00 systemd[1]: Job weave.service/start failed with result 'dependency'.
kube-00 ~ #

After a bit of review...it looks like it's related to Docker:

kube-00 ~ # journalctl -u weave
-- Logs begin at Mon 2015-12-07 06:02:14 UTC, end at Mon 2015-12-07 16:36:12 UTC. --
Dec 07 06:03:04 kube-00 systemd[1]: Starting Weave Network Router...
Dec 07 06:03:05 kube-00 systemd[1]: Dependency failed for Weave Network Router.
Dec 07 06:03:05 kube-00 systemd[1]: Job weave.service/start failed with result 'dependency'.
Dec 07 06:03:05 kube-00 systemd[1]: weave.service: control process exited, code=exited status=1
Dec 07 06:03:05 kube-00 systemd[1]: Unit weave.service entered failed state.
Dec 07 06:03:05 kube-00 systemd[1]: weave.service failed.
Dec 07 06:03:05 kube-00 docker[830]: time="2015-12-07T06:03:05Z" level="fatal" msg="Post http:///var/run/docker.sock/v1.16/images/create?fromImage=zettio%2Fweave%3Alatest: read unix /var/run/docker.sock: connection reset by peer"
Dec 07 06:03:05 kube-00 systemd[1]: weave.service holdoff time over, scheduling restart.
Dec 07 06:03:05 kube-00 systemd[1]: Stopping Weave Network Router...
Dec 07 06:03:05 kube-00 systemd[1]: Dependency failed for Weave Network Router.
Dec 07 06:03:05 kube-00 systemd[1]: Job weave.service/start failed with result 'dependency'.
kube-00 ~ # journalctl -au weave
-- Logs begin at Mon 2015-12-07 06:02:14 UTC, end at Mon 2015-12-07 16:36:23 UTC. --
Dec 07 06:03:04 kube-00 systemd[1]: Starting Weave Network Router...
Dec 07 06:03:05 kube-00 systemd[1]: Dependency failed for Weave Network Router.
Dec 07 06:03:05 kube-00 systemd[1]: Job weave.service/start failed with result 'dependency'.
Dec 07 06:03:05 kube-00 systemd[1]: weave.service: control process exited, code=exited status=1
Dec 07 06:03:05 kube-00 systemd[1]: Unit weave.service entered failed state.
Dec 07 06:03:05 kube-00 systemd[1]: weave.service failed.
Dec 07 06:03:05 kube-00 docker[830]: time="2015-12-07T06:03:05Z" level="fatal" msg="Post http:///var/run/docker.sock/v1.16/images/create?fromImage=zettio%2Fweave%3Alatest: read unix /var/run/docker.sock: connection reset by peer"
Dec 07 06:03:05 kube-00 systemd[1]: weave.service holdoff time over, scheduling restart.
Dec 07 06:03:05 kube-00 systemd[1]: Stopping Weave Network Router...
Dec 07 06:03:05 kube-00 systemd[1]: Dependency failed for Weave Network Router.
Dec 07 06:03:05 kube-00 systemd[1]: Job weave.service/start failed with result 'dependency'.
kube-00 ~ # journalctl -au docker
-- Logs begin at Mon 2015-12-07 06:02:14 UTC, end at Mon 2015-12-07 16:36:33 UTC. --
Dec 07 06:02:57 kube-00 systemd[1]: [/etc/systemd/system/docker.service.d/50-weave-kubernetes.conf:2] Invalid environment assignment, ignoring: DOCKER_OPTS='--bridge="weave" -r="false"'
Dec 07 06:03:04 kube-00 systemd[1]: Starting Docker Application Container Engine...
Dec 07 06:03:04 kube-00 systemd[1]: Started Docker Application Container Engine.
Dec 07 06:03:05 kube-00 dockerd[829]: time="2015-12-07T06:03:05Z" level="info" msg="+job serveapi(fd://)"
Dec 07 06:03:05 kube-00 dockerd[829]: time="2015-12-07T06:03:05Z" level="info" msg="Listening for HTTP on fd ()"
Dec 07 06:03:05 kube-00 dockerd[829]: time="2015-12-07T06:03:05Z" level="info" msg="+job init_networkdriver()"
Dec 07 06:03:05 kube-00 dockerd[829]: no such network interface
Dec 07 06:03:05 kube-00 dockerd[829]: time="2015-12-07T06:03:05Z" level="info" msg="-job init_networkdriver() = ERR (1)"
Dec 07 06:03:05 kube-00 dockerd[829]: time="2015-12-07T06:03:05Z" level="fatal" msg="no such network interface"

Your thoughts? Am I missing something, or is there more I can help provide?

v1k

errordeveloper commented 8 years ago

Thank you for reporting this, @v1k0d3n! I am afraid this repo contains very old code, which I just forgot to delete. Please look here instead.

v1k0d3n commented 8 years ago

thanks for the redirect @errordeveloper...i thought something was strange, and that makes so much more sense now!