#weavenetwork

hi folks

Lawouach_Work: Good morning

after the holiday, time to catch up with all the great things that happened with weave :)

any possible reason to have weave launch stuck ?

What does `weave status` say? (run it from a different shell/window)

where I have to do it ? on the host where I start to start weave or where I run the command (it's for different docker host)

does weave use no_proxy and http_proxy etc variables ?

destiny__: https://github.com/weaveworks/weave/issues/379

We had this issue before, but now all the curl call happen inside the weaveexec container which has its own env so it should be OK

Also which version of weave are you using?

11.2 I think

somehing like that

Any joy running `weave status`?

I can't dl the image (slow connection)

it stucks when i create my second machine of the network

`weave setup` on its own downloads the images

Then `weave launch` etc shouldn't block

I already have images that I use nomaly

weave container is running

but a container with this command

"/home/weave/sigprox

what is his role ?

That's the process inside the weaveexec container running your current weave command

docker logs gives nothing

I think bryanb meant for you to run `weave status` on the same host as the one with the stuck `weave launch`, not on a second host

the second one doesnt succeed to talk to the first one ?

Awaiting consensus

It looks like IPAM hasn't achieved quorum

the first host seems Ok

I started it with initpercount 1, now the second with 2 is stuck

Could you paste the commands you used to launch the two peers?

$WEAVE launch -iprange 10.2.3.0/24 -initpeercount 1

$WEAVE launch-dns "10.9.1.1/24" -debug

$WEAVE launch-proxy --with-dns --with-ipam

and $WEAVE launch -iprange 10.2.3.0/24 -initpeercount 2 on the other host

And then you use `weave connect` to join one to ther other?

yes but after the 3 commands

The -initpeercount should be 2 on both

See if that works

I hadn't to do that before

and it worked

the only one thing I changed is some proxy variables on the hosts

If you specify the IP address of the other peer to `weave launch` it isn't necessary

don't remeber to did that

Could you `weave version` for me just to make sure I'm looking at the right docs?

So it has worked with those settings before?

You may have just got lucky with timing

+ SCRIPT_VERSION=(unreleased version)

ok

I took the latest version on my own registry when it was 0.11.2

so when I start weave-launch I have to put the ip of the master ?

The best explanation is here http://docs.weave.works/weave/0.11.2/head/ipam.... ('Initialisation' section)

Or, if it is not convenient to name all the other hosts at launch time, you can give the number of peers like this:

so I'm not forced to give an IP

That's right

oh sorry

yes I am

hmm, that's strange

Each peer needs to know how many peers there will be in total

Which you can tell it by giving each the complete list of IPs

it's a dynamic cluster

Or with -initpeercount, and then use `weave connect` later

even me I don't know how many there will be

ok so that's what i'm using

so it's not normal that I have a problem

So it's the second launch that hangs

So you can't follow up with `weave connect $HOST1`

yup

Is it still in that stuck state now?

In the pastebin there was a container ID 1f38974edf82148f65b1a721003a89f708e922a2846a280e8f5bdb87353882e8

Was that the weaveexec container?

yup

the one which gives nothing with docker logs

so it is waiting something ?

OK just been chatting with bryanb

When you do `weave launch`, we iterate through all the application containers on the host and find all those who have a weave interface with an IP address inside the IPAM range

strenge cause It worked few days ago, don't able to remeber If i changed something ><

We then feed these into IP

IPAM to claim them

That claim requires quorum

The quorum requires the peers to be connected

So you can either do the second `weave launch` with the IP of HOST1

and not do the connect ?

Or you can do the `weave connect` asynchronously

so it shouldn't stuck

If you're in the 'stuck' state now you should be able to do `weave connect` in another shell on $HOST2 and the launch will complete

I did the weave connect

still stuck

What does `weave status` on $HOST2 say now?

got the peer, but still waiting ? lol

shit

i gave wrong ip

it's ok

weave connect unstucked it

I'll raise an issue for this

We need to the dynamic scenario a bit more thought

^We need to give

destiny__: Do you have a github handle? I'll @mention you in the issue

pacaletx my name on github

Ta