Kubernetes Pod terminates with Exit Code 143

user_12344281 0
Viewed 3053

I am using a containerized Spring boot application in Kubernetes. But the application automatically exits and restarts with exit code 143 and error message "Error".

I am not sure how to identify the reason for this error.

My first idea was that Kubernetes stopped the container due to too high resource usage, as described here, but I can't see the corresponding kubelet logs.

Is there any way to identify the cause/origin of the SIGTERM? Maybe from spring-boot itself, or from the JVM?

spring-boot kubernetes docker exit-code jvm
1 Answers

Exit Code 143

  1. It denotes that the process was terminated by an external signal.

  2. The number 143 is a sum of two numbers: 128+x, # where x is the signal number sent to the process that caused it to terminate.

  3. In the example, x equals 15, which is the number of the SIGTERM signal, meaning the process was killed forcibly.

Hope this helps better.

user_30983300
Related