-
-
Notifications
You must be signed in to change notification settings - Fork 414
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
[🐛 BUG]: Services directly killed when restarting or terminating #1814
Comments
version 2023.2.2 acts the same when service is restarting, but when server is stopped, service receives signal
|
Hey @chazzbg 👋 I'll double-check this case, but looks strange, since I'm sending |
I also find this quite odd. Without exec_timeout, service process seems to get the signal
|
Ok, thanks. Thus, I know where the bug is 😃 |
No duplicates 🥲.
What happened?
Services are directly killed when their timeout is reached. The same happens when a termination command is send to the RPC.
As far as i understand, rr should send SIGINT and wait for the specified timeout to send SIGKILL but
none of this seems to be happening.
Test setup is dead simple, not much can go wrong and I'm not sure what else i could add.
Version (rr --version)
2023.3.8
How to reproduce the issue?
.rr.yaml
service.php
Dockerfile
Relevant log output
The text was updated successfully, but these errors were encountered: