pulasthi commented on issue #2538: vagrant "hello" script fails
URL: 
https://github.com/apache/incubator-openwhisk/issues/2538#issuecomment-343643930
 
 
   Hi
   I was trying to follow the vagrant setup on my local machine ( ubuntu 16.04 
LTS ) and got the same errors (shown below). I also tried out what @reiz has 
mentioned and created a file at /etc/sudoers.d/vagrant with the given content 
but still got the error. 
   
   After i get the error i can log into the vagrant with ssh but the invoke 
example does not work. I assume that is because the setup processes were not 
completed. Please let me know if you need any futher information from me
   
   
       default: Saturday 11 November 2017  06:00:14 +0000 (0:00:00.254)       
0:07:54.632 ***** 
       default: ok: [controller1] => (item=(0, u'172.17.0.1'))
       default: ok: [controller0] => (item=(0, u'172.17.0.1'))
       default: ok: [controller0] => (item=(1, u'172.17.0.1'))
       default: ok: [controller1] => (item=(1, u'172.17.0.1'))
       default: 
       default: TASK [controller : (re)start controller] 
***************************************
       default: Saturday 11 November 2017  06:00:14 +0000 (0:00:00.287)       
0:07:54.920 ***** 
       default: changed: [controller1]
       default: changed: [controller0]
       default: 
       default: TASK [controller : wait until the Controller in this host is up 
and running] ***
       default: Saturday 11 November 2017  06:03:05 +0000 (0:02:50.690)       
0:10:45.610 ***** 
       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: Saturday 11 November 2017  06:04:08 +0000 (0:01:03.254)       
0:11:48.864 ***** 
       default: 
=============================================================================== 
       default: kafka : pull the ches/kafka:0.10.2.1 image 
---------------------------- 402.20s
       default: controller : (re)start controller 
------------------------------------- 170.69s
       default: controller : wait until the Controller in this host is up and 
running -- 63.25s
       default: kafka : pull the zookeeper:3.4 image 
----------------------------------- 41.66s
       default: kafka : wait until the Zookeeper in this host is up and running 
--------- 7.26s
       default: kafka : wait until the kafka server started up 
-------------------------- 5.32s
       default: kafka : create the health and the cacheInvalidation topic 
--------------- 4.00s
       default: kafka : create the active-ack topics 
------------------------------------ 3.89s
       default: kafka : create the invoker topics 
--------------------------------------- 3.81s
       default: Gathering Facts 
--------------------------------------------------------- 2.04s
       default: Gathering Facts 
--------------------------------------------------------- 1.94s
       default: kafka : (re)start zookeeper 
--------------------------------------------- 0.59s
       default: kafka : (re)start kafka 
------------------------------------------------- 0.45s
       default: controller : check if whisk_local_whisks with CouchDB exists 
------------ 0.36s
       default: controller : create seed nodes list 
------------------------------------- 0.29s
       default: controller : check if whisk_local_subjects with CouchDB exists 
---------- 0.26s
       default: controller : ensure controller log directory is created with 
permissions --- 0.26s
       default: controller : check if whisk_local_activations with CouchDB 
exists ------- 0.25s
       default: controller : check, that required databases exist 
----------------------- 0.17s
       default: controller : pull the latest image of controller 
------------------------ 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.
   
   
   Best Regards,
   Pulasthi
   

----------------------------------------------------------------
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

Reply via email to