You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openwhisk.apache.org by GitBox <gi...@apache.org> on 2018/02/05 16:13:40 UTC
[GitHub] tymanoj opened a new issue #3248: Unable to connect to controller0 while running openwhisk.yml (local deployment)
tymanoj opened a new issue #3248: Unable to connect to controller0 while running openwhisk.yml (local deployment)
URL: https://github.com/apache/incubator-openwhisk/issues/3248
<!--
Do NOT share passwords, credentials or other confidential information.
Before creating a new issue, please check if there is one already open that
fits the defect you are reporting.
If you open an issue and realize later it is a duplicate of a pre-existing
open issue, please close yours and add a comment to the other.
Issues can be created for either defects or enhancement requests. If you are a committer than please add the labels "bug" or "feature". If you are not a committer please make clear in the comments which one it is, so that committers can add these labels later.
If you are reporting a defect, please edit the issue description to include the
information shown below.
If you are reporting an enhancement request, please include information on what you are trying to achieve and why that enhancement would help you.
For more information about reporting issues, see
https://github.com/apache/incubator-openwhisk/blob/master/CONTRIBUTING.md#raising-issues
Use the commands below to provide key information from your environment:
You do not have to include this information if this is a feature request.
-->
## Environment details:
* local deployment
* Docker version 17.12.0-ce, build c97c6d6, ubuntu 16.04 LTS, Vagrant 1.8.1, couchdb 2.1.1
## Steps to reproduce the issue:
1. Follow the steps for local development on Ubuntu
2. Use CouchDB as the database
3. The situation will occur while running openwhisk.yml with ansible-playbook.
4. It waits for the controller for all 12 retries and then gives up. However, I can see a container running controller on 0.0.0.0:10001->8080/tcp.
## Provide the expected results and outputs:
```
The expected result is to run **sudo ansible-playbook openwhisk.yml** command without any failures.
```
## Provide the actual results and outputs:
```
TASK [controller : create seed nodes list] **********************************************************************************************
Monday 05 February 2018 17:14:58 +0200 (0:00:00.179) 0:00:37.382 *******
ok: [controller0] => (item=(0, u'172.17.0.1'))
TASK [controller : (re)start controller] ************************************************************************************************
Monday 05 February 2018 17:14:58 +0200 (0:00:00.210) 0:00:37.592 *******
changed: [controller0]
TASK [controller : wait until the Controller in this host is up and running] ************************************************************
Monday 05 February 2018 17:15:02 +0200 (0:00:03.716) 0:00:41.308 *******
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 (11 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (10 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (9 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (8 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (7 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (6 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (5 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (4 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (3 retries left).
FAILED - RETRYING: wait until the Controller in this host is up and running (2 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": "", "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"}
PLAY RECAP ******************************************************************************************************************************
controller0 : ok=16 changed=3 unreachable=0 failed=1
kafka0 : ok=8 changed=6 unreachable=0 failed=0
Monday 05 February 2018 17:16:04 +0200 (0:01:02.233) 0:01:43.542 *******
===============================================================================
controller : wait until the Controller in this host is up and running -- 62.23s
kafka : (re)start kafka ------------------------------------------------ 13.16s
zookeeper : wait until the Zookeeper in this host is up and running ----- 7.29s
kafka : wait until the kafka server started up -------------------------- 5.34s
controller : (re)start controller --------------------------------------- 3.72s
zookeeper : (re)start zookeeper ----------------------------------------- 3.35s
zookeeper : pull the zookeeper:3.4 image -------------------------------- 2.24s
kafka : pull the wurstmeister/kafka:0.11.0.1 image ---------------------- 1.70s
Gathering Facts --------------------------------------------------------- 0.61s
controller : copy jmxremote password file ------------------------------- 0.59s
Gathering Facts --------------------------------------------------------- 0.40s
controller : copy jmxremote access file --------------------------------- 0.40s
Gathering Facts --------------------------------------------------------- 0.36s
controller : check if whisk_local_whisks with CouchDB exists ------------ 0.31s
controller : ensure controller config directory is created with permissions --- 0.31s
controller : ensure controller log directory is created with permissions --- 0.23s
controller : create seed nodes list ------------------------------------- 0.21s
controller : prepare controller ports ----------------------------------- 0.19s
controller : check if whisk_local_subjects with CouchDB exists ---------- 0.19s
controller : check if whisk_local_activations with CouchDB exists ------- 0.19s
*******************************************************************************************************************
sudo docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
40caf6dde712 whisk/controller:latest "/bin/sh -c 'exec /i?" About a minute ago Up About a minute 0.0.0.0:15000->15000/tcp, 0.0.0.0:16000->16000/tcp, 0.0.0.0:8000->2551/tcp, 0.0.0.0:10001->8080/tcp controller0
e3caca9904ac wurstmeister/kafka:0.11.0.1 "start-kafka.sh" About a minute ago Up About a minute 0.0.0.0:9092->9092/tcp kafka0
6cb008c9dcb6 zookeeper:3.4 "/docker-entrypoint.?" About a minute ago Up About a minute 0.0.0.0:2181->2181/tcp, 0.0.0.0:2888->2888/tcp, 0.0.0.0:3888->3888/tcp zookeeper0
5dd7b8271cc9 openwhisk/apigateway:0.9.8 "/usr/bin/dumb-init ?" 7 minutes ago Up 7 minutes 80/tcp, 8423/tcp, 0.0.0.0:9000->9000/tcp, 0.0.0.0:9001->8080/tcp apigateway
54f5b954e9f4 redis:3.2 "docker-entrypoint.s?" 7 minutes ago Up 7 minutes 0.0.0.0:6379->6379/tcp redis
8d53009037bd apache/couchdb:2.1 "tini -- /docker-ent?" 9 minutes ago Up 9 minutes 0.0.0.0:4369->4369/tcp, 0.0.0.0:5984->5984/tcp, 0.0.0.0:9100->9100/tcp couchdb
```
## Additional information you deem important:
* I faced same issue with other components such as kafka but was able to connect in few retries.
----------------------------------------------------------------
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:
users@infra.apache.org
With regards,
Apache Git Services