"RUNNING HANDLER [handlers : wait for weave to listen]" timeout about apollo HOT 9 CLOSED

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?

from apollo.

@NinoFloris if you export ANSIBLE_LOG="-vvvv" before running ansible again it should give you good debug output

from apollo.

I don't really see anything out of the ordinary here...

https://gist.github.com/NinoFloris/5485091483ca132120fce3169ecdac62

Maybe what I would like to know more is if there was a recent sucessful deployment by Capgemini on digitalocean. As it is stated to be project level supported in the docs it should just work right?

from apollo.

@NinoFloris I just tested the master branch on digitalocean and it worked for me. I did notice that the default master_instance_type and slave_instance_type of 512mb isnt enough and I have seen memory issues in some of the software used in the project. I usually use at least the 2GB for master and 4GB for slaves.

from apollo.

Yes please that would be awesome!

from apollo.

It's strange and I don't like that I cannot solve this problem on my own but I still cannot get past this ansible step.

What my exact setup is:

• TF_VAR for region (ams2) but I have also tried the default, lon1.
• TF_VAR for master and slave instance types, as you suggested 2gb and 4gb.
• APOLLO_PROVIDER set to digitalocean.
• TF_VAR_do_token set to a valid token.

I have had runs with TF_VAR_public_key_file set to a correct path and runs where I did not export it as it does not seem to do much?
I see the droplets come up in the DO web interface with the correct region and size.

I have had ANSIBLE_LOG=-vvvv but this did not reveal any insights on this issue.

My Terraform version is v0.6.14, Ansible is 2.0.1.0, and I run this on a normal OSX 10.11
Looking at ref master in my .git directory, the Apollo version I use is commit hash 5ec6257 e.g. current HEAD (5 april 2016)

Are there any variables that I have not set correctly? As this is all that I could find in the docs and code that really required input.

from apollo.

@NinoFloris you are correct, I started getting the same error. Only happens on the first run though. Seems to be a repeat of this #662. When I run ./bootstrap/apollo-launch.sh ansible_playbook_run the second time everything comes up fine.

from apollo.

labelling as bug - think we need to look deeper into this and provide a fix.

from apollo.

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

from apollo.