redpine42 opened a new issue #226: CouchDB fails to start URL: https://github.com/apache/incubator-openwhisk-deploy-kube/issues/226 Running Kubernetes in DC/OS. DC/OS version 1.11.2. Kubernetes version 1.1.1-1.10-4. Starting OpenWhisk via Helm instructions fails continually. 1. kubectl create namespace openwhisk 2. kubectl label nodes --all openwhisk-role=invoker 3. Create mycluster.yaml ``` whisk: ingress: type: NodePort api_host_name: 192.168.80.14 api_host_port: 31001 nginx: httpsNodePort: 31001 ``` 4. helm install . --namespace=openwhisk --name=owdev -f mycluster.yaml ``` Every 2.0s: kubectl get pods --all-namespaces Fri Jun 15 15:34:49 2018 NAMESPACE NAME READY STATUS RESTARTS AGE kube-system kube-dns-797d4bd8dd-4dbch 3/3 Running 0 1d kube-system kube-dns-797d4bd8dd-7j6zh 3/3 Running 0 1d kube-system kubernetes-dashboard-5c469b58b8-6g9nh 1/1 Running 0 1d kube-system metrics-server-77c969f8c-jr5jl 1/1 Running 0 1d kube-system tiller-deploy-df4fdf55d-684wm 1/1 Running 0 23h openwhisk apigateway-666478f446-ljpsh 1/1 Running 0 1h openwhisk controller-0 0/1 Init:1/2 0 1h openwhisk couchdb-6d596fd84-shd8h 0/1 CrashLoopBackOff 19 1h openwhisk invoker-ctldh 0/1 Init:0/2 0 1h openwhisk invoker-kzpk4 0/1 Init:0/2 0 1h openwhisk invoker-tttzt 0/1 Init:0/2 0 1h openwhisk kafka-0 1/1 Running 0 1h openwhisk kafkaprovider-586b444cb7-lsqlb 0/1 Init:0/1 0 1h openwhisk nginx-598c75d7d6-wpgxl 1/1 Running 0 1h openwhisk redis-5d77674f65-759fd 1/1 Running 0 1h openwhisk zookeeper-959c585d6-r94c2 1/1 Running 0 1h ``` Logs: ``` kubectl logs couchdb-6d596fd84-shd8h --namespace=openwhisk + TIMEOUT=0 + echo 'wait for CouchDB to be up and running' wait for CouchDB to be up and running + /docker-entrypoint.sh /opt/couchdb/bin/couchdb ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 0 -eq 30 ']' + echo 'waiting for CouchDB to be available' waiting for CouchDB to be available + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 1 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 2 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 3 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 4 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 5 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 6 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 7 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 8 -eq 30 ']' + echo 'waiting for CouchDB to be available' waiting for CouchDB to be available + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 9 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 10 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 11 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 12 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 13 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 14 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 15 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 16 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 17 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 18 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 19 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 20 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 21 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 22 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 23 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 24 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 25 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 26 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 27 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 waiting for CouchDB to be available + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 28 -eq 30 ']' + echo 'waiting for CouchDB to be available' waiting for CouchDB to be available + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils waiting for CouchDB to be available + '[' 29 -eq 30 ']' + echo 'waiting for CouchDB to be available' + sleep 2 + let TIMEOUT=TIMEOUT+1 ++ curl --output /dev/null --silent http://127.0.0.1:5984/_utils + '[' 30 -eq 30 ']' + '[' 30 -eq 30 ']' + echo 'failed to setup CouchDB' + exit 1 failed to setup CouchDB ``` Describe pod ``` kubectl describe pod couchdb-6d596fd84-wfrq8 --namespace=openwhisk Error from server (NotFound): pods "couchdb-6d596fd84-wfrq8" not found [duser@higgs helm]$ kubectl describe pod couchdb-6d596fd84-shd8h --namespace=openwhisk Name: couchdb-6d596fd84-shd8h Namespace: openwhisk Node: kube-node-0-kubelet.kubernetes.mesos/192.168.80.16 Start Time: Fri, 15 Jun 2018 14:01:52 -0400 Labels: name=couchdb pod-template-hash=281529840 Annotations: <none> Status: Running IP: 9.0.1.68 Controlled By: ReplicaSet/couchdb-6d596fd84 Containers: couchdb: Container ID: docker://5414141a8a3f0654453d2b623ef13236357e672da8e7ce9b149aeea88e5a73e0 Image: openwhisk/kube-couchdb:latest Image ID: docker-pullable://openwhisk/kube-couchdb@sha256:fe494b6cbf1b5d2464db7d9194e1bd0cb01b85f4fdfa3c7b71e26c1538b43a64 Port: 5984/TCP Command: /init.sh State: Waiting Reason: CrashLoopBackOff Last State: Terminated Reason: Error Exit Code: 1 Started: Fri, 15 Jun 2018 15:33:34 -0400 Finished: Fri, 15 Jun 2018 15:34:35 -0400 Ready: False Restart Count: 19 Readiness: http-get http://:5984/test_activations delay=60s timeout=1s period=10s #success=1 #failure=10 Environment: DB_HOST: 127.0.0.1 DB_PREFIX: test_ COUCHDB_USER: <set to the key 'db_username' in secret 'db.auth'> Optional: false COUCHDB_PASSWORD: <set to the key 'db_password' in secret 'db.auth'> Optional: false DB_PORT: 5984 NODENAME: couchdb0 Mounts: /var/run/secrets/kubernetes.io/serviceaccount from default-token-hqbnj (ro) Conditions: Type Status Initialized True Ready False PodScheduled True Volumes: default-token-hqbnj: Type: Secret (a volume populated by a Secret) SecretName: default-token-hqbnj Optional: false QoS Class: BestEffort Node-Selectors: <none> Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s node.kubernetes.io/unreachable:NoExecute for 300s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning Unhealthy 39m (x5 over 1h) kubelet, kube-node-0-kubelet.kubernetes.mesos Readiness probe failed: Get http://9.0.1.68:5984/test_activations: dial tcp 9.0.1.68:5984: getsockopt: connection refused Warning BackOff 34s (x331 over 1h) kubelet, kube-node-0-kubelet.kubernetes.mesos Back-off restarting failed container ```
---------------------------------------------------------------- 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
