超时后无法部署到AWS Elastic Beanstalk [英] Can't deploy to AWS Elastic Beanstalk after timeout

问题描述

我不熟悉AWS Elastic Beanstalk，这是我第一次遇到此问题.我尝试通过将应用程序zip上传到实例来部署新版本，并且更新完成但出现错误:

I am newish to AWS Elastic Beanstalk and this is the first time I have encountered this issue. I tried deploying a new version via zip upload of my app to an instance and the updated completed with errors:

已完成但有命令行超时"，我增加了配置文件中的超时并重新部署，此后我收到此消息.

"Completed but with Command Line Timeouts", I increased the timeout in the config file and redeployed, after which I got this message.

在异常终止的部署过程中，某些实例可能已经部署了新的实例 应用程序版本.确保所有实例都运行相同 版本，然后重新部署相应的应用程序版本.

During an aborted deployment, some instances may have deployed the new application version. To ensure all instances are running the same version, re-deploy the appropriate application version.

每次尝试重新部署时都会重复一次.

This repeats each time try to redeploy.

我进入EC2实例，发现/var/app/ondeck文件夹仍然存在.

I went into the EC2 instance and noticed the the /var/app/ondeck folder was still there.

我认为这是问题所在，但我怀疑简单地删除此目录是否可以解决问题-除非如此简单.

I assume this is the issue, but i doubt that simply removing this directory would be the answer - unless it is that simple.

/var应用程序/当前版本仍然存在，并且该应用程序可以使用在初始超时之前部署的版本正常运行.

The /var app/current version is still present and the app runs fine using the version that was deployed prior to the initial timeout.

我继承了这个应用程序，它是Laravel，编写器脚本需要一些时间才能运行.

I inherited this app it is Laravel and the composer scripts take a while to run.

感谢您的帮助.

推荐答案

我也遇到了同样的问题.当我更新回以前的平台版本时，它会变成正常状态，现在可以部署了.

I have faced same problem. When I update back previous platform version, it turns to healthy state, and I can deploy now.

这篇关于超时后无法部署到AWS Elastic Beanstalk的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！