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/06/05 11:20:43 UTC
[GitHub] vcosqui opened a new issue #211: Controller pod shuts down with no
errors after start
vcosqui opened a new issue #211: Controller pod shuts down with no errors after start
URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/211
Dear openwhisk team
After some time succesfully playing with the vagrant installation of openwhisk, now I am trying to setup a k8s cluster on google GKE, so far I have been able to deploy and connect all the components but the controller. It's pod stays in CrashLoopBackOff status. I have checked the logs and I found that after starting up and connecting to kafka and couchdb it apparently shuts down with no errors.
Could you please give me some help on what could be the reason?
Thanks in advance!
```
kubectl logs controller-0 --namespace openwhisk -f
[2018-06-05T11:04:37.293Z] [INFO] Initializing Kamon...
[INFO] [06/05/2018 11:04:38.096] [main] [StatsDExtension(akka://kamon)] Starting the Kamon(StatsD) extension
[2018-06-05T11:04:38.232Z] [INFO] Slf4jLogger started
[2018-06-05T11:04:38.292Z] [INFO] Starting remoting
[2018-06-05T11:04:38.508Z] [INFO] Remoting started; listening on addresses :[akka.tcp://controller-actor-system@10.32.0.46:2552]
[2018-06-05T11:04:38.510Z] [INFO] Remoting now listens on addresses: [akka.tcp://controller-actor-system@10.32.0.46:2552]
[2018-06-05T11:04:38.538Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - Starting up...
[2018-06-05T11:04:38.603Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - Registered cluster JMX MBean [akka:type=Cluster]
[2018-06-05T11:04:38.605Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - Started up successfully
[2018-06-05T11:04:38.689Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - No seed-nodes configured, manual cluster join required
[2018-06-05T11:04:39.129Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.triggers.fires.perMinute
[2018-06-05T11:04:39.130Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.actions.sequence.maxLength
[2018-06-05T11:04:39.132Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.actions.invokes.concurrent
[2018-06-05T11:04:39.133Z] [INFO] [#tid_sid_unknown] [Config] environment set value for controller.instances
[2018-06-05T11:04:39.133Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.version.date
[2018-06-05T11:04:39.134Z] [INFO] [#tid_sid_unknown] [Config] environment set value for whisk.version.buildno
[2018-06-05T11:04:39.134Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.actions.invokes.perMinute
[2018-06-05T11:04:39.135Z] [INFO] [#tid_sid_unknown] [Config] environment set value for limits.actions.invokes.concurrentInSystem
[2018-06-05T11:04:39.136Z] [INFO] [#tid_sid_unknown] [Config] environment set value for runtimes.manifest
[2018-06-05T11:04:39.137Z] [INFO] [#tid_sid_unknown] [Config] environment set value for kafka.hosts
[2018-06-05T11:04:39.138Z] [INFO] [#tid_sid_unknown] [Config] environment set value for port
[2018-06-05T11:05:05.297Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - Exiting completed
[2018-06-05T11:05:05.318Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - Shutting down...
[2018-06-05T11:05:05.341Z] [INFO] Cluster Node [akka.tcp://controller-actor-system@10.32.0.46:2552] - Successfully shut down
[2018-06-05T11:05:05.360Z] [INFO] [#tid_sid_unknown] [Controller] Shutting down Kamon with coordinated shutdown
[2018-06-05T11:05:05.363Z] [INFO] Shutting down remote daemon.
[2018-06-05T11:05:05.364Z] [INFO] Remote daemon shut down; proceeding with flushing remote transports.
[2018-06-05T11:05:05.415Z] [INFO] Remoting shut down
```
----------------------------------------------------------------
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