fix(hotfix-master): update ebextension #286
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
prestonlimlianjie
requested review from
lamkeewei,
alexanderleegs,
kwajiehao and
gweiying
alexanderleegs
approved these changes
Sep 7, 2021
prestonlimlianjie
changed the title
harishv7
pushed a commit
that referenced
this pull request
Feb 17, 2023
fix(hotfix-master): update ebextension
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
Deployments to AWS EB fail with the following error:
Command failed on instance. Return code: 7 Output: command 00_reload_nginx in .ebextensions/nginx-max-body-size.config failed. For more detail, check /var/log/eb-activity.log using console or EB CLI.We found a Stackoverflow recommendation that fixes the issue and tested it on the CMS staging environment:
https://stackoverflow.com/questions/40766708/issue-with-aws-beanstalk-command/48203336#48203336
Fix
We removed the unnecessary
service nginx reloadcommand and the deploy succeeded on staging.