Instance deployment failed error on eb create command

0

I'm getting Instance deployment failed error on 'eb create les-app-env' command.

Error:

2022-07-12 10:42:59 INFO Created CloudWatch alarm named: awseb-e-9dhtmixwn6-stack-AWSEBCloudwatchAlarmLow-KTOGLIH19F0K 2022-07-12 10:43:15 ERROR Instance deployment failed. For details, see 'eb-engine.log'. 2022-07-12 10:43:15 ERROR Instance deployment failed to install application dependencies. The deployment failed. 2022-07-12 10:43:18 ERROR [Instance: i-0325bf91e0b716996] Command failed on instance. Return code: 1 Output: Engine execution has encountered an error.. 2022-07-12 10:43:18 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1]. 2022-07-12 10:44:21 ERROR Create environment operation is complete, but with errors. For more information, see troubleshooting documentation. ERROR: ServiceError - Create environment operation is complete, but with errors. For more information, see troubleshooting documentation.

How to resolve this?

gefragt vor 2 Jahren403 Aufrufe
1 Antwort
0

The environment created but as you say the deployment to the EC2 Instance (i-0325bf91e0b716996) failed.

This is the important message:

 INFO Command execution completed on all instances. Summary: [Successful: 0, Failed: 1]

Commands will execute on the instance during a deployment. In this case one failed. The only way to see which one is using logs, as it says "For details, see eb-engine.log". The logs can be got from the Beanstalk web UI [1] or directly on the EC2 Instance, if using linux its /var/log/eb-engine.log

Review the logs for additional information and feel free to post the error here and I'll take a look. On a side note, if you are using ebextensions and have commands defined you can specify "ignoreErrors" [2] to true meaning a failed command will not cause the deployment to fail.

P.s re:Post offers Markdown functionality when posting a question, be sure to use code blocks and quotes to make your questions readable. It will encourage more people to answer and comment.

  1. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html
  2. https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customize-containers-ec2.html#linux-commands
profile picture
beantwortet vor 2 Jahren
  • I went till the Cloud Watch eb engine log page. From there how do I view the eb engine log? This is the path it is showing: /aws/elasticbeanstalk/lesoko-app-env/var/log/eb-engine.log. And there is an ARN as well. How can I use it to view the log?

  • @rePost-User-1778305 the log will only be visible in CloudWatch if log streaming is enabled. The log group you are looking at "lesoko-app-env" is different from the environment that you have in the question "les-app-env". In CloudWatch the logs are separated by environment. To view the log for this environment you will need to check "/aws/elasticbeanstalk/les-app-env/var/log/eb-engine.log" - inside this log group there should be a log stream for each instance in the environment, e.g. "i-0325bf91e0b716996"

  • There are no log streams under /aws/elasticbeanstalk/lesoko-app-env/var/log/eb-engine.log in CloudWatch. And sorry for the confusion. lesoko-app-env is the actual environment name. Is there any other way to view the eb-engine.log file?

  • @rePost-User-1778305 Yes please read the answer I posted, the logs can be got from the Beanstalk UI, follow the steps here https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/using-features.logging.html#health-logs-instancelocation

Du bist nicht angemeldet. Anmelden um eine Antwort zu veröffentlichen.

Eine gute Antwort beantwortet die Frage klar, gibt konstruktives Feedback und fördert die berufliche Weiterentwicklung des Fragenstellers.

Richtlinien für die Beantwortung von Fragen