Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"RUNNING HANDLER [handlers : wait for weave to listen]" timeout

See original GitHub issue

I have tried to get this great starting point for a cluster online but I get stuck with Weave not getting online correctly.

This is the console output leading up to the timeout of the ansible step. https://gist.github.com/NinoFloris/89609002e852ce87fb3470320202e215

I don’t exactly know how to debug this, Ssh’ing into a host and running docker ps -a gives this result

CONTAINER ID        IMAGE                        COMMAND             CREATED             STATUS              PORTS               NAMES
b8e1aa9af01c        weaveworks/weaveexec:1.4.4   "/bin/false"        2 minutes ago       Created                                 weavevolumes-1.4.4

So at least docker is running fine but systemctl shows weave and weaveproxy as dead

weave.service                                                   loaded    inactive dead      Weave Network Router
weaveproxy.service                                              loaded    inactive dead      Weave proxy for Docker API

Manually starting weaveproxy.service shows weave as ‘activating’ not ‘active’ (is this because of docker attach that keeps the service connected in the foreground?).

After starting weaveproxy.service my docker ps looks like this

CONTAINER ID        IMAGE                        COMMAND                  CREATED             STATUS              PORTS               NAMES
37b410f490d7        weaveworks/weaveexec:1.4.4   "/home/weave/sigproxy"   20 seconds ago      Up 19 seconds                           amazing_stallman
2406bda553a0        weaveworks/weave:1.4.4       "/home/weave/weaver -"   21 seconds ago      Up 20 seconds                           weave
885176cfe20e        weaveworks/weaveexec:1.4.4   "/home/weave/weavepro"   21 seconds ago      Up 21 seconds                           weaveproxy
b8e1aa9af01c        weaveworks/weaveexec:1.4.4   "/bin/false"             7 minutes ago       Created                                 weavevolumes-1.4.4

I would love some pointers as where to look because this is quite new terrain for me, the project is great though. I had almost started working on something exactly like this.

EDIT: This is on DigitalOcean

Issue Analytics

State:
Created 7 years ago
Comments:9 (6 by maintainers)

Top GitHub Comments

1reaction

NinoFloriscommented, Apr 3, 2016

Ahhh wow, I would have never thought of that angle. I will try this tomorrow. Many thanks!

Would a contribution of better docs be something I could help with once I get a cluster up and running and have a better feeling for all the components involved?

0reactions

dllewellyncommented, Apr 7, 2016

Not sure if this is helpful info, but I’m getting the same problem running the vagrant build (using master branch)

Top Results From Across the Web

Injector does not inject sidecar container · Issue #32 - GitHub

Hello, I'm trying to deploy vault with sidecar injector. I'm using this chart: https://github.com/hashicorp/vault-helm and following this ...

java - How set a timeout for my thread Handler method?

To run a periodic task, you can post a Runnable to a Handler with some delay using postDelayed method. private Handler mHandler =...

Configure Liveness, Readiness and Startup Probes

The initialDelaySeconds field tells the kubelet that it should wait 3 seconds before performing the first probe. To perform a probe, the kubelet ......

Global Configurations | MuleSoft Documentation

Name Type Required Default defaultResponseTimeout string no 10000 defaultTransactionTimeout string no 30000 defaultErrorHandler‑ref string no none

Liveness probe failed connection refused - Rancher Forums

Liveness: http-get http://:80/healthz delay=60s timeout=1s period=30s ... In general, you are running out of resources, did you check the ...