Skip to content

Stop SolidQueue on puma restart when puma plugin is used. #185

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 1, 2024

Conversation

nashby
Copy link
Contributor

@nashby nashby commented Mar 23, 2024

Without doing so SolidQueue would be running making Puma not properly stop so when Puma tries to start its process again we would get Errno::EADDRINUSE error.

Closes #180


@pid = fork do
exec(*cmd)
Dir.chdir('test/dummy') do
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had to change the dir here this way instead of using --dir option because when you trigger puma's restart it can't find the app anymore since current dir is already test/dummy and it's trying to use test/dummy in addition.

@nashby nashby force-pushed the puma-restart branch 6 times, most recently from bc96173 to 56f7f02 Compare March 23, 2024 17:58
Without doing so SolidQueue would be running making Puma not properly stop so whne Puma tries to
start its process again we would get `Errno::EADDRINUSE` error.
Copy link
Member

@rosa rosa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great spot, thank you! 🙏

@rosa rosa merged commit 35f0b35 into rails:main Apr 1, 2024
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Address already in use error when using both tmp_restart & solid_queue puma plugin
2 participants