One node pod CrashLoopBackOff
Hi,
I have 5 applications running the same setup (node+express) but 1 of them keeps getting a CrashLoopBackOff, when checking the logs I get the following:
error Command failed with signal "SIGKILL".
But the node isn't reporting any issues:
Conditions:
Type Status LastHeartbeatTime LastTransitionTime Reason Message
---- ------ ----------------- ------------------ ------ -------
NetworkUnavailable False Tue, 13 Apr 2021 13:38:51 +0200 Tue, 13 Apr 2021 13:38:51 +0200 CalicoIsUp Calico is running on this node
MemoryPressure False Sun, 02 May 2021 10:22:07 +0200 Wed, 21 Apr 2021 12:36:05 +0200 KubeletHasSufficientMemory kubelet has sufficient memory available
DiskPressure False Sun, 02 May 2021 10:22:07 +0200 Wed, 21 Apr 2021 12:36:05 +0200 KubeletHasNoDiskPressure kubelet has no disk pressure
PIDPressure False Sun, 02 May 2021 10:22:07 +0200 Wed, 21 Apr 2021 12:36:05 +0200 KubeletHasSufficientPID kubelet has sufficient PID available
Ready True Sun, 02 May 2021 10:22:07 +0200 Wed, 21 Apr 2021 12:36:05 +0200 KubeletReady kubelet is posting ready status. AppArmor enabled
Allocated resources:
(Total limits may be over 100 percent, i.e., overcommitted.)
Resource Requests Limits
-------- -------- ------
cpu 550m (27%) 0 (0%)
memory 230Mi (5%) 340Mi (8%)
ephemeral-storage 0 (0%) 0 (0%)
hugepages-1Gi 0 (0%) 0 (0%)
hugepages-2Mi 0 (0%) 0 (0%)
And locally the program runs just fine, so I'm out of ideas on why the pod keeps rebooting.
1 Reply
watrick
Linode Staff
I haven't personally run into a situation like this before, though doing some digging into the error that you shared, I found a post on Stack Overflow that provides a couple of possible explanations and additional commands to help troubleshoot:
One of the highest voted responses on there suggests that the trouble is in the Docker file, where you need to have a command to run or having ReplicationControllerspecify a command. Though, with the information you provided about this running on multiple nodes makes me think this may not the case here.
Another suggestion lower down on the post suggests adjusting the initialDelaySeconds config, as someone with a similar issue was able to resolve it with that.