Skip to content

systemd service: don't SIGKILL on stop - #3912

Open
WilliamDEdwards wants to merge 1 commit into
ytti:masterfrom
WilliamDEdwards:chore/remove-sigkill
Open

WilliamDEdwards wants to merge 1 commit into
ytti:masterfrom
WilliamDEdwards:chore/remove-sigkill

Conversation

@WilliamDEdwards

Copy link
Copy Markdown

Number of problems with SIGKILLing Oxidized:

  • There seems to be no reason, as killing with a regular SIGTERM works
  • systemd unit is set to Active: failed due to SIGKILL, which implies stopping failed even though it worked as intended
  • Oxidized doesn't get a chance to clean up /etc/oxidized/pid, which might prevent future starts ("A server is already running. Check /etc/oxidized/pid")

Number of problems with SIGKILLing Oxidized:

- There seems to be no reason, as killing with a regular SIGTERM works
- systemd unit is set to `Active: failed` due to SIGKILL, which implies stopping failed even though it worked as intended
- Oxidized doesn't get a chance to clean up `/etc/oxidized/pid`, which might prevent future starts ("A server is already running. Check /etc/oxidized/pid")
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.

1 participant