sven-lange-last commented on issue #4303: Unable to connect to controller0 while running openwhisk.yml (local deployment), Connection refused! URL: https://github.com/apache/incubator-openwhisk/issues/4303#issuecomment-505742706 @reachyunsong the log file you provided above indicates that your controller fails to start up: ``` TASK [controller : wait until the Controller in this host is up and running] ***************************** Tuesday 25 June 2019 21:03:15 -0600 (0:00:03.465) 0:00:55.020 ********** FAILED - RETRYING: wait until the Controller in this host is up and running (12 retries left). ... FAILED - RETRYING: wait until the Controller in this host is up and running (1 retries left). fatal: [controller0]: FAILED! => {"attempts": 12, "changed": false, "content": "", "msg": "Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused>", "redirected": false, "status": -1, "url": "https://172.17.0.1:10001/ping"} Status code was -1 and not [200]: Request failed: <urlopen error [Errno 111] Connection refused> ``` The log output indicates that there was no TCP listening port `172.17.0.1:10001` on the system. Very likely, your controller was not running at all while the Ansible playbook tried to connect. As @rabbah mentioned above, this is very likely a configuration problem. So instead of removing the controller log file, I suggest to re-deploy. If the same error occurs again, have a look at the controller log and check whether it succeeded with starting up. If not search for `ERROR`s and `Exception`s in the log.
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
