我有一个Spring Boot应用程序，部署在Kubernetes上的docker容器上 . 该应用程序运行良好一段时间（小时），但在某个时刻，它开始重新启动像疯狂显示CrashLoopBackOff错误状态 .
这是我从死荚中得到的信息：
Port: 8080/TCP
State: Waiting
Reason: CrashLoopBackOff
Last State: Terminated
Reason: Error
Exit Code: 137
Started: Fri, 11 Aug 2017 10:15:03 +0200
Finished: Fri, 11 Aug 2017 10:16:22 +0200
Ready: False
Restart Count: 7
...
Volume Mounts:
/var/run/secrets/kubernetes.io/serviceaccount from default-token-bhk8f (ro)
Environment Variables:
JAVA_OPTS: -Xms512m -Xmx1792m
Conditions:
Type Status
Initialized True
Ready False
PodScheduled True
...
QoS Class: BestEffort
Tolerations: <none>
No events.
Is there any way to get more detailed information about the cause of the crashes?
Is 137 error code an out of memory error? 我一直在将Java进程的内存从-Xmx768m增加到1792m，但错误不断出现 . Could it be something else?
One weird fact: 我需要找出应用程序如何运行良好，几个小时后pod被杀死，然后每次重启都会在执行几秒后被终止 .
1 回答
kubectl logs podName containerName将为您提供容器日志，该日志应该为您提供有关错误原因的其他信息 .