ElasticBeanstalk-应用程序更改未显示 [英] ElasticBeanstalk - application changes not showing

查看:70
本文介绍了ElasticBeanstalk-应用程序更改未显示的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在使用Elasticbeanstalk在AWS上托管应用程序.我正在使用工具带从本地计算机推送应用程序.直到几个星期前,一切工作正常,但最近我的更改没有生效.我可以在aws管理控制台中看到正在推送和部署我的应用程序,但是更改没有完成.

I'm hosting an application with AWS, using elasticbeanstalk. I'm using the toolbelt to push my application from my local machine. Up until a couple weeks ago, everything was working fine, but recently my changes aren't taking effect. I can see in the aws management console that my application is being pushed and deployed, but changes aren't coming through.

我检查了环境事件日志,以查看典型部署中是否有新内容,并且看到的错误是

I checked the environment event log to see if anything was new from a typical deployment and the error I'm seeing is

ERROR   Update environment operation is complete, but with command timeouts. Try increasing the timeout period. For more information, see troubleshooting documentation.
ERROR   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.
ERROR   Failed to deploy application.
ERROR   Unsuccessful command execution on instance id(s) 'i-8d88a587'. Aborting the operation.

到底是什么问题,我该怎么解决?

What is the problem exactly, and what can I do to fix this?

推荐答案

可能有多种原因.

下一步故障排除步骤是下载最新的Elastic Beanstalk日志(从Web控制台或使用eb logs命令行工具.)

The next troubleshooting step is to download the most recent Elastic Beanstalk logs (either from the web console or with the eb logs command line tool.)

打开/var/log/eb-activity.log并查看最后几行,以确定失败的确切命令.

Open /var/log/eb-activity.log and look at the last few lines to determine the exact command that failed.

示例可能是

  • 服务器卷空间不足或
  • .ebextensions/中的自定义脚本存在错误
  • a server volume ran out of space or
  • a custom script in .ebextensions/ has a bug

这篇关于ElasticBeanstalk-应用程序更改未显示的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆