-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
Systemd unit doesn't kill child process (restart/stop/reload) #1576
Comments
…oad) killall binary is included in the package psmisc. we maybe have another way to solve this issue with « standard » tools https://stackoverflow.com/questions/392022/best-way-to-kill-all-child-processes Refs: influxdata#1576
…oad) killall binary is included in the package psmisc. we maybe have another way to solve this issue with « standard » tools https://stackoverflow.com/questions/392022/best-way-to-kill-all-child-processes Refs: influxdata#1576
Thanks for reporting this. I'm also seeing the same issue. This is why my changes to telegraf.conf weren't being reflected. After killing processes, telegraf is re-reading my edited config and working properly. |
(fix is in 1.0.0-beta1) |
Unfortunately I will not have time to cherry pick that into a 0.13.x release. For users needing a fix see the change to the systemd telegraf.service file here: https://github.com/influxdata/telegraf/pull/1279/files @sbadia if you could post a step-by-step how you patched it, that might help other users as well. Thank you! |
@sparrc ack ! Yes, sure, here are the manual procedure, (it's a bit shorter with a config. mgt tool) Intro (tested on telegraf 0.13.x)
Stop the telegraf service, and show reaming process
Kill them all :-)
Backup and patch the systemd unit using master raw
And finaly reload systemd and relaunch telegraf
|
Bug report
Using systemd, the
stop
orreload
/restart
command doesn't kill the child telegraf processes.System info:
Steps to reproduce:
Expected behavior:
The
stop
orrestart
/reload
action should not leave remaining process.Actual behavior:
Un-controlled process are still running
Use case:
When we upgrade packages the old process are still running… it's a bit annoying…
The text was updated successfully, but these errors were encountered: