openshift pod 的 CrashLoopBackOff 状态是什么?

问题描述

有不止一个例子，我在 openshift origin 中运行的 pod 中看到了这种状态.在这种情况下，它是 cdi camel 示例的快速入门.我能够在本地(非 openshift)成功构建和运行它，但是当我尝试在本地 openshift 上部署时(使用 mvn -Pf8-local-deploy)，我得到了该特定输出示例(剪下相关性):-

There is more than one example where I have seen this status from a pod running in openshift origin. In this case it was the quickstart for the cdi camel example. I was able to successfully build and run it locally (non - openshift) but when I try to deploy on my local openshift (using mvn -Pf8-local-deploy), I get this output for that particular example (snipped for relevance) :-

[vagrant@vagrant camel]$ oc 获取豆荚姓名准备状态重新开始年龄cdi-camel-z4czs 0/1 CrashLoopBackOff 4 2m

日志尾部如下:-

  Error occurred during initialization of VM
  Error opening zip file or JAR manifest missing : agents/jolokia.jar
  agent library failed to init: instrument

有人可以帮我解决这个问题吗?

Can someone help me solve this ?

推荐答案

临时解决方法 -> https://github.com/fabric8io/ipaas-quickstarts/issues/1157

基本上需要删除src/main/hawt-app目录.

Basically, the src/main/hawt-app directory needs to be deleted.

这篇关于openshift pod 的 CrashLoopBackOff 状态是什么?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！