You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
There might be a bug that is caused by the combination of fork_worker together with the systemd notification integration (also known as SdNotify). When both are active, reforking will change the Active status in systemd to reloading (reload), but never changes it back.
Current behavior
A refork signals to systemd that a reload is being performed. This signal never gets changed to ready again.
Expected behavior
Either, a refork is signalled as reload and, once finished, signalled as finished OR the refork is not changing the systemd status at all. I would prefer the second option (no signalling to systemd at all, since we are not completely reloading the application).
Desktop:
OS: Linux
Puma Version: 6.4.0
The text was updated successfully, but these errors were encountered:
Describe the bug
There might be a bug that is caused by the combination of
fork_worker
together with the systemd notification integration (also known asSdNotify
). When both are active, reforking will change theActive
status in systemd toreloading (reload)
, but never changes it back.Puma config:
/usr/local/bin/bundle exec puma -C puma.rb -b tcp://0.0.0.0:9292 hello.ru
To Reproduce
I've created a minimal repository with reproduction steps: MrSerth/puma-refork-systemd.
Current behavior
A refork signals to systemd that a reload is being performed. This signal never gets changed to ready again.
Expected behavior
Either, a refork is signalled as reload and, once finished, signalled as finished OR the refork is not changing the systemd status at all. I would prefer the second option (no signalling to systemd at all, since we are not completely reloading the application).
Desktop:
The text was updated successfully, but these errors were encountered: