Skip to content
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

systemv init: "$PID_FILE does not exist, process is not running" can be wrong #90

Closed
igalic opened this issue Aug 3, 2016 · 1 comment

Comments

@igalic
Copy link
Contributor

igalic commented Aug 3, 2016

Affected Puppet, Ruby, OS and module versions/distributions

  • Puppet: any
  • Ruby: any
  • Distribution: Debian/Ubuntu
  • Module version: v2.0.0

How to reproduce (e.g Puppet code you use)

¯(°_o)/¯

What are you seeing

when kafka died a horrible death (unclean shutdown? kill -9?) it can happen that the pid file isn't cleaned up properly. So, even though it's running, our init script says it's not, and doesn't even attempt to stop it

What behaviour did you expect instead

same as systemd…

Any additional information you'd like to impart

this is my fault, sorry

@igalic
Copy link
Contributor Author

igalic commented Aug 30, 2016

i think we fixed this in #94 and #96

@igalic igalic closed this as completed Aug 30, 2016
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

No branches or pull requests

1 participant