Fix boot loop with Puma #6097
Open
Fix boot loop with Puma #6097
Conversation
This file contains hidden or 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
Fix a boot loop that caused a 502 Bad Gateway error
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fix a boot loop that caused a 502 Bad Gateway error.
[1/4] Resolving packages... success Already up-to-date. Done in 0.59s. yarn run v1.22.19 $ node esbuild.mjs watch build finished Done in 0.62s. Database 'greenlight-v3-production' already exists => Booting Puma => Rails 7.1.4.1 application starting in production => Runbin/rails server --helpfor more startup options A server is already running. Check /usr/src/app/tmp/pids/server.pid. Exiting Greenlight-v3 starting on port: 3000 Postgres host: postgres Postgres port: 5432 Redis host: redis Redis port: 6379 yarn install v1.22.19 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. [1/4] Resolving packages... success Already up-to-date. Done in 0.61s. yarn run v1.22.19 $ sass ./app/assets/stylesheets/application.bootstrap.scss ./app/assets/builds/application.css --no-source-map --load-path=node_modules --style compressed Done in 3.77s. yarn install v1.22.19 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json. [1/4] Resolving packages... success Already up-to-date. Done in 0.58s. yarn run v1.22.19 $ node esbuild.mjs watch build finished Done in 0.65s. Database 'greenlight-v3-production' already exists => Booting Puma => Rails 7.1.4.1 application starting in production => Runbin/rails server --helpfor more startup options A server is already running. Check /usr/src/app/tmp/pids/server.pid. Exiting Greenlight-v3 starting on port: 3000 Postgres host: postgres Postgres port: 5432 Redis host: redis Redis port: 6379 yarn install v1.22.19 warning package-lock.json found. Your project contains lock files generated by tools other than Yarn. It is advised not to mix package managers in order to avoid resolution inconsistencies caused by unsynchronized lock files. To clear this warning, remove package-lock.json.