fix(server): stop recursive restart wrapper causing spawn EAGAIN outage#231
Merged
Conversation
… check server.js re-spawned node server.js on every crash, so a crash-loop stacked wrapper processes until the OS process table filled and every spawn failed with EAGAIN, keeping staging at 502 even after the underlying crash was fixed. The entry point now runs index.js in-process and leaves restarts to pm2. The deploy workflow also gains a post-restart health probe on the app port plus a pm2 log tail, so a deploy that leaves the app down says so in the run log instead of reporting success. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
This was referenced Jun 15, 2026
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
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.
Root cause of the persistent staging 502: server.js recursively spawned new wrapper processes on every crash. This morning's crash-loop stacked wrappers until the OS hit spawn EAGAIN (errno -11, confirmed in pm2 logs), so even the already-fixed code could not start. server.js now requires index.js in-process (pm2 owns restarts), and the deploy workflow gains a post-restart port-4003 health probe + pm2 log tail so failed boots are visible in the run log. NOTE: merging this is necessary but not sufficient — orphaned wrapper processes must be killed on the server once (commands provided in chat).
🤖 Generated with Claude Code