• EN
Question

catalog-svc-5c6ffff9f9-lbgvl pod is going on Init:CrashLoopBackOff mode.

N
Userlevel 3

Hi,

my catalog-svc-5c6ffff9f9-lbgvl pod is running on Init:CrashLoopBackOff mode.

Events:
  Type     Reason            Age                  From               Message
  ----     ------            ----                 ----               -------
  Normal   Scheduled         20m                  default-scheduler  Successfully assigned kasten-io/catalog-svc-5c6ffff9f9-lbgvl to znlapcdp07447v
  Normal   Pulled            20m                  kubelet            Successfully pulled image "gcr.io/kasten-images/upgrade:5.5.6" in 2.057493741s
  Normal   Pulled            20m                  kubelet            Successfully pulled image "gcr.io/kasten-images/upgrade:5.5.6" in 191.938119ms
  Normal   Pulling           20m (x3 over 20m)    kubelet            Pulling image "gcr.io/kasten-images/upgrade:5.5.6"
  Normal   Created           20m (x3 over 20m)    kubelet            Created container upgrade-init
  Normal   Started           20m (x3 over 20m)    kubelet            Started container upgrade-init
  Normal   Pulled            20m                  kubelet            Successfully pulled image "gcr.io/kasten-images/upgrade:5.5.6" in 175.403555ms
  Warning  BackOff           19m (x4 over 20m)    kubelet            Back-off restarting failed container
  Warning  DNSConfigForming  19s (x104 over 20m)  kubelet            Search Line limits were exceeded, some search paths have been omitted, the applied search line is: kasten-io.svc.cluster.local svc.cluster.local cluster.local zurich.com zurich.net mega.us.zurich.com

2 comments

Madi.Cristil
Userlevel 7
Badge +7

@jaiganeshjk 

Madi Cristil
jaiganeshjk
Userlevel 6
Badge +2

@ntiwari38 Init crashlooping of Catalog SVC mostly occurs when it cannot write data into its Persistent Volume.

If you are using an NFS StorageClass which doesn’t support fsGroup fields in the workload securityContext, You might have to manually change the permissions & ownership for the directory to the user which catalog uses(UID/GID is 1000) 

You can look at the reason for crashlooping with the below command

kubectl logs deploy/catalog-svc --all-containers -n kasten-io

 

Jaiganesh

Comment


Terms & Conditions