alexanderdean / Unified-Log-Processing

Supporting material (code, schemas etc) for Unified Log Processing (Manning Publications)
http://manning.com/dean/
Apache License 2.0
97 stars 25 forks source link

vagrant fails to provision - http://mirrors.muzzy.org.uk/ not available #31

Closed snowch closed 8 years ago

snowch commented 8 years ago
$ vagrant up
...
==> default: TASK: [thrift | Dependencies | Ensure packages for building Thrift installed] ***
==> default: ok: [127.0.0.1] => (item=curl,vim,make,libboost-dev,libboost-test-dev,libboost-program-options-dev,libevent-dev,automake,libtool,flex,bison,pkg-config,g++,libssl-dev)
==> default:
==> default: TASK: [thrift | Install | Ensure Thrift source downloaded] ********************
==> default: failed: [127.0.0.1] => {"dest": "/var/cache/ansible", "failed": true, "gid": 0, \
     "group": "root", "mode": "0755", "owner": "root", "response": "Request failed: <urlopen error [Errno 111] Connection refused>", \
     "size": 4096, "state": "directory", "status_code": -1, "uid": 0, \
     "url": "http://mirrors.muzzy.org.uk/apache/thrift/0.9.3/thrift-0.9.3.tar.gz"}
==> default: msg: Request failed
==> default:
==> default: FATAL: all hosts have already failed -- aborting
==> default:
==> default: PLAY RECAP ********************************************************************
==> default:            to retry, use: --limit @/home/vagrant/thrift.retry
==> default:
==> default: 127.0.0.1                  : ok=8    changed=1    unreachable=0    failed=1
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Is seems the muzzy site is unavailable. How can I replace this with another download site?

alexanderdean commented 8 years ago

Hi @snowch - hmm, we should have fixed that yesterday:

https://github.com/snowplow/ansible-playbooks/commit/5f9e17cf5e53a539aaf9068527a876899f5c13b5

Can you try blowing away the whole repo (to clear the cache) and retry?

snowch commented 8 years ago

Yep, sorted now.