Deploy the ONAP casablanca version, encountered the dmaap-dr-node pod is always restarting, checking the pod, found the following errors:

Warning Unhealthy 5m (x3669 over 4d) kubelet, 192.168.123.107 Readiness probe failed: dial tcp 10.253.9.100:8080: getsockopt: connection refused
Warning Unhealthy 5m (x1468 over 4d) kubelet, 192.168.123.107 Liveness probe failed: dial tcp 10.253.9.100:8080: getsockopt: connection refused

Here is the pod description:

[root@k1 ~]# kubectl describe pod dev-dmaap-dmaap-dr-node-65c99cd46b-88kt9 -n onap
Name: dev-dmaap-dmaap-dr-node-65c99cd46b-88kt9
Namespace: onap
Node: 192.168.123.107/192.168.123.107
Start Time: Fri, 01 Mar 2019 03:30:43 -0500
Labels: app=dmaap-dr-node
pod-template-hash=2175578026
release=dev-dmaap
Annotations: <none>
Status: Running
IP: 10.253.9.100
Controlled By: ReplicaSet/dev-dmaap-dmaap-dr-node-65c99cd46b
Init Containers:
dmaap-dr-node-readiness:
Container ID: docker://19e8e2972e8034fb6ef2a285cd03ae74c399bd5075e631163f07043c57e83e5a
Image: oomk8s/readiness-check:2.0.0
Image ID: docker-pullable://oomk8s/readiness-check@sha256:7daa08b81954360a1111d03364febcb3dcfeb723bcc12ce3eb3ed3e53f2323ed
Port: <none>
Command:
/root/ready.py
Args:
--container-name
dmaap-dr-prov
State: Terminated
Reason: Completed
Exit Code: 0
Started: Fri, 01 Mar 2019 03:31:00 -0500
Finished: Fri, 01 Mar 2019 03:31:02 -0500
Ready: True
Restart Count: 0
Environment:
NAMESPACE: onap (v1:metadata.namespace)
Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-62hv9 (ro)
Containers:
dmaap-dr-node:
Container ID: docker://4007e0d2a7bd76b4f86dd49ada95495a173c25c43f1f69d096a04f9c13826acf
Image: nexus3.onap.org:10001/onap/dmaap/datarouter-node:1.0.3
Image ID: docker-pullable://nexus3.onap.org:10001/onap/dmaap/datarouter-node@sha256:49c3d9bbdc12bb02f44454caee59658a1e0fb648843ee 349d87874a49b9a269b
Ports: 8080/TCP, 8443/TCP
State: Running
Started: Wed, 06 Mar 2019 01:52:56 -0500
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Wed, 06 Mar 2019 01:43:16 -0500
Finished: Wed, 06 Mar 2019 01:52:24 -0500
Ready: False
Restart Count: 734
Liveness: tcp-socket :8080 delay=500s timeout=1s period=10s #success=1 #failure=3
Readiness: tcp-socket :8080 delay=500s timeout=1s period=10s #success=1 #failure=3
Environment: <none>
Mounts:
/etc/localtime from localtime (rw)
/opt/app/datartr/etc/createFeed.sh from create-feed (rw)
/opt/app/datartr/etc/dedicatedFeed.json from create-feed (rw)
/opt/app/datartr/etc/node.properties from node-props (rw)
/var/run/secrets/kubernetes.io/serviceaccount from default-token-62hv9 (ro)
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
Volumes:
localtime:
Type: HostPath (bare host directory volume)
Path: /etc/localtime
HostPathType:
create-feed:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: dev-dmaap-dmaap-dr-node-create-feed-configmap
Optional: false
node-props:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: dev-dmaap-dmaap-dr-node-node-props-configmap
Optional: false
dr-node-data:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
default-token-62hv9:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-62hv9
Optional: false
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: <none>
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning Unhealthy 5m (x3669 over 4d) kubelet, 192.168.123.107 Readiness probe failed: dial tcp 10.253.9.100:8080: getsockopt: connect ion refused
Warning Unhealthy 5m (x1468 over 4d) kubelet, 192.168.123.107 Liveness probe failed: dial tcp 10.253.9.100:8080: getsockopt: connecti on refused
[root@k1 ~]#