主页 / coding / 问题 / 79311762
Accepted
Milenko Markovic
Asked: 2024-12-27 20:06:29 +0800 CST

为什么一个 pod 发生 CrashLoopBackOff 而另一个 pod 运行正常？

  • 772

我已经部署，但随着时间的推移，出现了错误。

NAME                                  READY   STATUS             RESTARTS        AGE
pod/picanagm-solution-5cb8887968-qk4pr   0/1     CrashLoopBackOff   140 (78s ago)   11h
pod/picanagm-solution-77f5fcfdc-kwd9w    1/1     Running            0               2d20h

失败 Pod 的日志

Events:
  Type     Reason   Age                     From     Message
  ----     ------   ----                    ----     -------
  Warning  BackOff  2m42s (x3258 over 11h)  kubelet  Back-off restarting failed container

和

Picked up JAVA_TOOL_OPTIONS: -Dlogging.config=/app/run/logback.xml -DcontentServer.factory-reset=folder -DcontentServer.factory-reset.folder-name=file:/app/bookmarks -DSameSite=none -Dconfiguration.sign-off.enabled=true -Ddata.extraction.templates.base.dir.path=${java.io.tmpdir} --add-opens=java.base/java.util.concurrent=ALL-UNNAMED --add-opens=java.base/java.util=ALL-UNNAMED

I> No access restrictor found, access to any MBean is allowed
Jolokia: Agent started with URL http://10.244.4.81:8778/jolokia/
Exception in thread "main" java.lang.UnsupportedClassVersionError: com/activeviam/MINDZ/starter/main/MINDZApplication has been compiled by a more recent version of the Java Runtime (class file version 65.0), this version of the Java Runtime only recognizes class file versions up to 61.0
    at java.base/java.lang.ClassLoader.defineClass1(Native Method)
    at java.base/java.lang.ClassLoader.defineClass(ClassLoader.java:1012)

一个副本集正常，另一个副本集尚未准备好

replicaset.apps/picanagm-solution-5cb8887968   1         1         0       11h

为什么？如何调试此行为？

kubernetes

1 个回答

  1. Best Answer

    这个问题的答案Why did I got CrashLoopBackOff for one pod and the other is working fine?是：

    当旧副本运行良好时，意味着没有问题。但是，当新副本无法正常运行时，则表明它存在错误。在具有两个副本的部署中，旧副本会等待新副本准备就绪，并最终自行关闭。因此，如果新副本无法正常运行（CrashLoopBackOff），旧副本仍将正常运行。

    • 0

相关问题