Fix site start/stop status by removing stale socket file#2534
Merged
Conversation
Collaborator
📊 Performance Test ResultsComparing 611152d vs trunk site-editor
site-startup
Results are median values from multiple test runs. Legend: 🟢 Improvement (faster) | 🔴 Regression (slower) | ⚪ No change |
sejas
approved these changes
Feb 4, 2026
Member
sejas
left a comment
There was a problem hiding this comment.
Nice! it solved my issue! 👌
Now I can see the sites starting and stopping as expected.
Contributor
|
pm2-axon is supposed to automatically handle The gist of the logic is that:
If this fixes the underlying problem, that's great 👍 Still, I'm curious how the pm2-axon logic fails and why… |
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
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.
Related issues
Proposed Changes
~/.studio/pm2/events.sock) before binding in the_eventscommandRoot cause: When Studio crashes or is force-killed, the socket file is left behind. On restart, the
_eventscommand cannot bind to this socket (EADDRINUSE), preventing site-event updates from flowing to the UI.Testing Instructions
npm start)pkill -9 -f "Electron.app"ls -la ~/.studio/pm2/events.socknpm start)Pre-merge Checklist