简体繁体 English

超时后无法部署到AWS Elastic Beanstalk

[英]Can't deploy to AWS Elastic Beanstalk after timeout

原文 2015-03-30 15:28:14 6 1 amazon-web-services/ amazon-ec2/ elastic-beanstalk

I am newish to AWS Elastic Beanstalk and this is the first time I have encountered this issue. 我对AWS Elastic Beanstalk很新，这是我第一次遇到这个问题。 I tried deploying a new version via zip upload of my app to an instance and the updated completed with errors: 我尝试通过我的应用程序的zip上传部署一个新版本到一个实例，更新完成时出现错误：

"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. 每次尝试重新部署时都会重复此操作。

I went into the EC2 instance and noticed the the /var/app/ondeck folder was still there. 我进入EC2实例并注意到/ var / app / ondeck文件夹仍然存在。

I assume this is the issue, but i doubt that simply removing this directory would be the answer - unless it is that simple. 我认为这是问题，但我怀疑只是删除这个目录将是答案 - 除非这么简单。

The /var app/current version is still present and the app runs fine using the version that was deployed prior to the initial timeout. / var app / current版本仍然存在，并且应用程序使用在初始超时之前部署的版本运行正常。

I inherited this app it is Laravel and the composer scripts take a while to run. 我继承了这个应用程序，它是Laravel，作曲家脚本需要一段时间才能运行。

Thanks for any help. 谢谢你的帮助。

1 个解决方案

I have faced same problem. 我遇到了同样的问题。 When I update back previous platform version, it turns to healthy state, and I can deploy now. 当我更新以前的平台版本时，它会变为健康状态，我现在可以部署。