I ran two clara reference pipelines (ct-recon-vnetseg.yaml ct-recon.yaml) successfully. But when i attempted the third (ct-vnetseg.yaml), the dicom-adapter status turned to CrashLoopBackOff. I tried all I could, including re-deploying clara but I still get the same status. Kubectl describe pod [pod name] shows that it is restarting failed container. How can I resolve this? See attached details.
clara-user@Clara-server:~/clara/my-pipelines$ kubectl get pods
NAME READY STATUS RESTARTS AGE
clara-clara-platformapiserver-59dfbcd6b6-frd6z 1/1 Running 0 17h
clara-dicom-adapter-677db74bdd-hg5sd 0/1 CrashLoopBackOff 205 17h
clara-results-service-58d7cdc45-xttk7 1/1 Running 0 17h
clara-ui-58b97bc76b-sv5xn 1/1 Running 0 17h
clara-workflow-controller-796b77b8d-vb7qs 1/1 Running 0 17h
clara-user@Clara-server:~/clara/my-pipelines$ kubectl describe pod clara-dicom-adapter-677db74bdd-hg5sd
Name: clara-dicom-adapter-677db74bdd-hg5sd
Namespace: default
Priority: 0
Node: clara-server/172.19.0.74
Start Time: Wed, 13 Nov 2019 10:39:10 -0500
Labels: app.kubernetes.io/instance=clara-dicom-adapter
app.kubernetes.io/name=dicom-adapter
pod-template-hash=677db74bdd
Annotations: <none>
Status: Running
IP: 10.244.0.72
Controlled By: ReplicaSet/clara-dicom-adapter-677db74bdd
Containers:
dicom-adapter:
Container ID: docker://8860c47f17f0a6b67803672aabf06cf79d392866798f5510feb763522b86d050
Image: clara/dicomadapter:0.2.0
Image ID: docker://sha256:e58e4ec8a8fce1c992523e03839f9d78264939167f537e65a79259268b501f8e
Port: 104/TCP
Host Port: 104/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 208
Started: Thu, 14 Nov 2019 03:43:09 -0500
Finished: Thu, 14 Nov 2019 03:43:10 -0500
Ready: False
Restart Count: 205
Environment: <none>
Mounts:
/app/app.yaml from dicom-server-config (rw,path="app.yaml")
/payloads from pv-dicom-adapter-volume (rw,path="clara-core/payloads")
/var/run/secrets/kubernetes.io/serviceaccount from default-token-v44hz (ro)
Conditions:
Type Status
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
pv-dicom-adapter-volume:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: pv-dicom-adapter-volume-claim
ReadOnly: false
dicom-server-config:
Type: ConfigMap (a volume populated by a ConfigMap)
Name: clara-dicom-adapter-configmap
Optional: false
default-token-v44hz:
Type: Secret (a volume populated by a Secret)
SecretName: default-token-v44hz
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 BackOff 3m52s (x4732 over 17h) kubelet, clara-server Back-off restarting failed container