You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi.
I'm having CrashLoopBackOff when try to deploy a WppConnect on Kubernets. (Digital Ocean Cloud)
I watched this video: https://www.youtube.com/watch?v=ZJFQLp863ZI
I followed all steps but when I run kubectl apply to all the 3 files, my pod got a CrashLoopBack, could you please help me?
Here is the log:
kubectl describe pod server-cli-795c45687b-kjmw8
Name: server-cli-795c45687b-kjmw8
Namespace: default
Priority: 0
Service Account: default
Node: sendxpress-g3f9j/10.116.0.2
Start Time: Thu, 31 Oct 2024 18:19:44 +0100
Labels: app=server-cli
pod-template-hash=795c45687b
Annotations:
Status: Running
IP: 10.244.0.55
IPs:
IP: 10.244.0.55
Controlled By: ReplicaSet/server-cli-795c45687b
Containers:
server-cli:
Container ID: containerd://c3d8affb5845210ba6c10506deacd9853f126b64d75fd910ef439550958e222d
Image: wppconnect/server-cli:latest
Image ID: docker.io/wppconnect/server-cli@sha256:2d7523690140e288148363fd543034f72abe286aca7da222028c7eca7aed929f
Port: 21465/TCP
Host Port: 0/TCP
Command:
/bin/sh
-c
Args:
wppserver --secretKey My53cr3tKY --port 21465 --startAllSession
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 127
Started: Thu, 31 Oct 2024 18:20:12 +0100
Finished: Thu, 31 Oct 2024 18:20:12 +0100
Ready: False
Restart Count: 2
Limits:
cpu: 500m
memory: 1Gi
Requests:
cpu: 500m
memory: 500Mi
Liveness: http-get http://:21465/healthz delay=0s timeout=1s period=5s #success=1 #failure=1
Readiness: http-get http://:21465/healthz delay=0s timeout=1s period=3s #success=1 #failure=1
Startup: http-get http://:21465/healthz delay=0s timeout=1s period=3s #success=1 #failure=60
Environment:
Mounts:
/home/tokens from server-cli-volume (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zvj8w (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
server-cli-volume:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: server-cli-volume
ReadOnly: false
kube-api-access-zvj8w:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 37s default-scheduler Successfully assigned default/server-cli-795c45687b-kjmw8 to sendxpress-g3f9j
Normal SuccessfulAttachVolume 33s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-09851878-5bff-4bb1-a190-7c383391caa5"
Normal Pulled 28s kubelet Successfully pulled image "wppconnect/server-cli:latest" in 138ms (138ms including waiting). Image size: 795772713 bytes.
Normal Pulled 28s kubelet Successfully pulled image "wppconnect/server-cli:latest" in 188ms (188ms including waiting). Image size: 795772713 bytes.
Normal Pulling 9s (x3 over 28s) kubelet Pulling image "wppconnect/server-cli:latest"
Normal Created 9s (x3 over 28s) kubelet Created container server-cli
Normal Started 9s (x3 over 28s) kubelet Started container server-cli
Normal Pulled 9s kubelet Successfully pulled image "wppconnect/server-cli:latest" in 134ms (134ms including waiting). Image size: 795772713 bytes.
Warning BackOff 4s (x7 over 27s) kubelet Back-off restarting failed container server-cli in pod server-cli-795c45687b-kjmw8_default(f447f9ab-b961-4576-9f94-1fd14978d85f)
alvaro@Alvaros-MBP k8s_wppconnect % kubectl logs server-cli-795c45687b-kjmw8
/bin/sh: wppserver: not found
alvaro@Alvaros-MBP k8s_wppconnect % kubectl get pod
NAME READY STATUS RESTARTS AGE
server-cli-795c45687b-kjmw8 0/1 CrashLoopBackOff 5 (8s ago) 3m12s
The text was updated successfully, but these errors were encountered:
Hi.
I'm having CrashLoopBackOff when try to deploy a WppConnect on Kubernets. (Digital Ocean Cloud)
I watched this video: https://www.youtube.com/watch?v=ZJFQLp863ZI
I followed all steps but when I run kubectl apply to all the 3 files, my pod got a CrashLoopBack, could you please help me?
Here is the log:
kubectl describe pod server-cli-795c45687b-kjmw8
Name: server-cli-795c45687b-kjmw8
Namespace: default
Priority: 0
Service Account: default
Node: sendxpress-g3f9j/10.116.0.2
Start Time: Thu, 31 Oct 2024 18:19:44 +0100
Labels: app=server-cli
pod-template-hash=795c45687b
Annotations:
Status: Running
IP: 10.244.0.55
IPs:
IP: 10.244.0.55
Controlled By: ReplicaSet/server-cli-795c45687b
Containers:
server-cli:
Container ID: containerd://c3d8affb5845210ba6c10506deacd9853f126b64d75fd910ef439550958e222d
Image: wppconnect/server-cli:latest
Image ID: docker.io/wppconnect/server-cli@sha256:2d7523690140e288148363fd543034f72abe286aca7da222028c7eca7aed929f
Port: 21465/TCP
Host Port: 0/TCP
Command:
/bin/sh
-c
Args:
wppserver --secretKey My53cr3tKY --port 21465 --startAllSession
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 127
Started: Thu, 31 Oct 2024 18:20:12 +0100
Finished: Thu, 31 Oct 2024 18:20:12 +0100
Ready: False
Restart Count: 2
Limits:
cpu: 500m
memory: 1Gi
Requests:
cpu: 500m
memory: 500Mi
Liveness: http-get http://:21465/healthz delay=0s timeout=1s period=5s #success=1 #failure=1
Readiness: http-get http://:21465/healthz delay=0s timeout=1s period=3s #success=1 #failure=1
Startup: http-get http://:21465/healthz delay=0s timeout=1s period=3s #success=1 #failure=60
Environment:
Mounts:
/home/tokens from server-cli-volume (rw)
/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-zvj8w (ro)
Conditions:
Type Status
PodReadyToStartContainers True
Initialized True
Ready False
ContainersReady False
PodScheduled True
Volumes:
server-cli-volume:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: server-cli-volume
ReadOnly: false
kube-api-access-zvj8w:
Type: Projected (a volume that contains injected data from multiple sources)
TokenExpirationSeconds: 3607
ConfigMapName: kube-root-ca.crt
ConfigMapOptional:
DownwardAPI: true
QoS Class: Burstable
Node-Selectors:
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
Type Reason Age From Message
Normal Scheduled 37s default-scheduler Successfully assigned default/server-cli-795c45687b-kjmw8 to sendxpress-g3f9j
Normal SuccessfulAttachVolume 33s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-09851878-5bff-4bb1-a190-7c383391caa5"
Normal Pulled 28s kubelet Successfully pulled image "wppconnect/server-cli:latest" in 138ms (138ms including waiting). Image size: 795772713 bytes.
Normal Pulled 28s kubelet Successfully pulled image "wppconnect/server-cli:latest" in 188ms (188ms including waiting). Image size: 795772713 bytes.
Normal Pulling 9s (x3 over 28s) kubelet Pulling image "wppconnect/server-cli:latest"
Normal Created 9s (x3 over 28s) kubelet Created container server-cli
Normal Started 9s (x3 over 28s) kubelet Started container server-cli
Normal Pulled 9s kubelet Successfully pulled image "wppconnect/server-cli:latest" in 134ms (134ms including waiting). Image size: 795772713 bytes.
Warning BackOff 4s (x7 over 27s) kubelet Back-off restarting failed container server-cli in pod server-cli-795c45687b-kjmw8_default(f447f9ab-b961-4576-9f94-1fd14978d85f)
alvaro@Alvaros-MBP k8s_wppconnect % kubectl logs server-cli-795c45687b-kjmw8
/bin/sh: wppserver: not found
alvaro@Alvaros-MBP k8s_wppconnect % kubectl get pod
NAME READY STATUS RESTARTS AGE
server-cli-795c45687b-kjmw8 0/1 CrashLoopBackOff 5 (8s ago) 3m12s
The text was updated successfully, but these errors were encountered: