意外的应用程序崩溃:“劫持:后端错误:退出状态:500，并且找不到该进程的退出代码文件". [英] Unexpected app crashes: "hijack: Backend error: Exit status: 500 and could not find the exitcode file for the process"

问题描述

app.crash索引:0，原因:CRASHED，exit_description:实例不健康:劫持:后端错误:退出状态:500，消息:{"Type":"，"Message":设备上没有剩余空间，" Handle:"，" ProcessID:"};连接:进程错误:找不到该进程的退出代码文件:stat/var/vcap/data/garden/depot/XXX/processes/XXX/exitcode:没有这样的文件或目录；连接:

app.crash index: 0, reason: CRASHED, exit_description: Instance became unhealthy: hijack: Backend error: Exit status: 500, message: {"Type":"","Message":"no space left on device","Handle":"","ProcessID":""} ; connection: process error: could not find the exitcode file for the process: stat /var/vcap/data/garden/depot/XXX/processes/XXX/exitcode: no such file or directory; connection:

最近，在AppCloud中运行的多个应用程序上一直持续发生上述错误.应用程序之间没有连接，并且使用不同的构建包时，这些应用程序有很大的不同.

有人可以帮我还是遇到其他同样的问题?

Lately, the above error has been persistently occurring on several apps running in the AppCloud. There is no connection between the apps and the apps are very different with different buildpacks.

Can someone help me or has someone else the same problems?

设置示例: 在Swisscom Application Cloud中使用cloudfoundry php buildpack部署了PHP Webapp，同一个应用程序两次...一个应用程序因上面的错误而崩溃，另一个应用程序没有发生该错误(非常奇怪，一个应用程序正在运行，另一个没有运行.完全相同的配置/环境)，并在Linux容器Stack cflinuxfs2( https://github.com/cloudfoundry/cflinuxfs2 )

Setup Example: PHP Webapp deployed with the cloudfoundry php buildpack in Swisscom Application Cloud, the same App twice... one app crashes with the error above and the other app doesn't do the error (so very strange, one is running and one not with the exactly same config/environment), installed HTTPD and PHP with all dependencies in the linux container, Stack cflinuxfs2 (https://github.com/cloudfoundry/cflinuxfs2)

推荐答案

我们调查了这些崩溃，并发现它们是由于Cloud Foundry配置中的一个问题所致，该问题导致托管应用容器的VM运行在iNodes之外.然后，这通过操作系统报告设备上没有剩余空间"来体现，这可以说是有点误导，并且让我们上了一段时间.

We have investigated these crashes and have discovered, that they are due to an issue in our configuration of Cloud Foundry which causes the VMs which host the app containers to run out of iNodes. This then manifests itself with the OS reporting "no space left on device" which is arguably a bit misleading and had us fooled for a while.

我们当前正在开发一个新版本，它将解决此问题.我们计划将此版本尽快部署到生产中.我们将通过这篇文章为您提供最新信息.

We are currently working on a new release which will fix this issue. We plan to deploy this release to production as soon as possible. We will keep you updated via this post.

更新:我们推出了一个新的平台版本，该版本已解决了该问题.请检查您的事件日志以确认这一点.

Update: we have rolled out a new platform release which has fixed the issue. Please check your event logs to confirm this.

这篇关于意外的应用程序崩溃:“劫持:后端错误:退出状态:500，并且找不到该进程的退出代码文件".的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！