To circle back: This looks like missing configuration in Consul in the docker 
compose setup.

Reported https://github.com/openwhisk/openwhisk-devtools/issues/4

(Note: This of course ties back into the discussion about whether we use Consul 
at all or not, see [1])

Thanks
Felix

[1] 
https://lists.apache.org/thread.html/7f3a3f720e412f5ddb0651f56bba222ffef3c797beb615a34456d66c@%3Cdev.openwhisk.apache.org%3E

Am 25.01.2017 um 11:18 schrieb Felix Meschberger 
<[email protected]<mailto:[email protected]>>:

Hi

digging along it looks like the OpenWhisk controller is actually not starting.

Where the log file then says:

[2017-01-24T18:08:18.043Z] [INFO] [??] [WhiskConfig] reading properties from 
consul at consul.docker:8500
[2017-01-24T18:08:20.989Z] [WARN] [??] [WhiskConfig] failed to read properties 
from consul: null
[2017-01-24T18:08:21.011Z] [ERROR] [??] [Config] required property 
whisk.system.key still not set


Woot ! No properties from consul. I think this is fine, right ?

But where do I get the whisk.system.key ?

Thanks
Felix

Am 24.01.2017 um 16:02 schrieb Felix Meschberger 
<[email protected]<mailto:[email protected]>>:

Hi

I am trying to run the docker-compose setup of the openwhisk/openwhisk-devtools 
repository. It builds fine and starts launching the containers. But it waits 
indefinitely for the openwhisk controller to start while consul fails to 
connect to port 8888:

2017/01/24 15:01:15 [WARN] agent: http request failed 
'http://172.18.0.9:8888/ping': Get http://172.18.0.9:8888/ping: dial tcp 
172.18.0.9:8888: getsockopt: connection refused

I am running on macOS Sierra with Docker 1.13.0.

Could it be docker on mac being the problem ?

Thanks
Felix


Reply via email to