什么是openshift荚CrashLoopBackOff状态？ [英] What is CrashLoopBackOff status for openshift pods?

问题描述

有一个以上的例子，我已经看到了openshift起源运行从荚此状态。在这种情况下，它是用于CDI骆驼例的快速启动。我是能够成功地建立并在本地运行（非 - openshift），但是当我尝试在我的本地openshift部署（使用 MVN -Pf8本地部署），我得到这个输出是特殊的例子（剪断的相关性）： -

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) :-

[流浪的无业游民@骆驼] $ OC得到荚
NAME就绪状态重新启动AGE
CDI-骆驼z4czs 0/1 CrashLoopBackOff 42米

日志尾如下： -

  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

Temporary workaround -> https://github.com/fabric8io/ipaas-quickstarts/issues/1157

基本上，需要被删除的src / main / HAWT-app目录。

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

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