reiz commented on issue #2538: vagrant "hello" script fails URL: https://github.com/apache/incubator-openwhisk/issues/2538#issuecomment-343434172 I tried now a couple things to solve this. Fore example editing the `/etc/sudoers` file like described in this [thread](https://github.com/hashicorp/vagrant/issues/1659), but that didn't solve the problem. I further destroyed the whole Vagrant box and even deleted the `.vagrant` directory and started again `.hello`. But still getting this error message: ``` default: TASK [controller : wait until the Controller in this host is up and running] *** default: Friday 10 November 2017 10:11:09 +0000 (0:01:27.343) 0:03:57.068 ******* default: FAILED - RETRYING: wait until the Controller in this host is up and running (12 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (12 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (11 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (11 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (10 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (10 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (9 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (9 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (8 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (8 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (7 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (7 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (6 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (6 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (5 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (5 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (4 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (4 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (3 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (3 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (2 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (2 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (1 retries left). default: FAILED - RETRYING: wait until the Controller in this host is up and running (1 retries left). default: fatal: [controller1]: FAILED! => {"attempts": 12, "changed": false, "content": "", "failed": true, "msg": "Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://172.17.0.1:10002/ping"} default: fatal: [controller0]: FAILED! => {"attempts": 12, "changed": false, "content": "", "failed": true, "msg": "Status code was not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "http://172.17.0.1:10001/ping"} default: default: PLAY RECAP ********************************************************************* default: 172.17.0.1 : ok=10 changed=9 unreachable=0 failed=0 default: controller0 : ok=10 changed=2 unreachable=0 failed=1 default: controller1 : ok=10 changed=2 unreachable=0 failed=1 default: Friday 10 November 2017 10:12:14 +0000 (0:01:04.302) 0:05:01.370 ******* default: =============================================================================== default: kafka : pull the ches/kafka:0.10.2.1 image ----------------------------- 91.63s default: controller : (re)start controller -------------------------------------- 87.34s default: controller : wait until the Controller in this host is up and running -- 64.30s default: kafka : pull the zookeeper:3.4 image ----------------------------------- 25.54s default: kafka : wait until the Zookeeper in this host is up and running --------- 7.31s default: kafka : wait until the kafka server started up -------------------------- 5.40s default: kafka : create the active-ack topics ------------------------------------ 4.24s default: kafka : create the health and the cacheInvalidation topic --------------- 4.21s default: kafka : create the invoker topics --------------------------------------- 4.00s default: Gathering Facts --------------------------------------------------------- 2.15s default: Gathering Facts --------------------------------------------------------- 2.06s default: kafka : (re)start zookeeper --------------------------------------------- 0.70s default: kafka : (re)start kafka ------------------------------------------------- 0.59s default: controller : check if whisk_local_whisks with CouchDB exists ------------ 0.41s default: controller : create seed nodes list ------------------------------------- 0.32s default: controller : ensure controller log directory is created with permissions --- 0.29s default: controller : check if whisk_local_subjects with CouchDB exists ---------- 0.27s default: controller : check if whisk_local_activations with CouchDB exists ------- 0.26s default: controller : check, that required databases exist ----------------------- 0.18s default: controller : docker login ----------------------------------------------- 0.04s 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. ``` Feedback is welcome.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services
