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
PID file is not created using systemd collectd service #1946
Comments
Why do you need a pid file when you're running under systemd? |
There are many other applications that use the pid file. |
This is by design. Collectd doesn't write the pid file if systemd monitors the process with Type=notify. If you need to get the process status you need to use the systemd tools (systemctl status) or apis. If you really want to keep using pid files and the associated racy behaviour, use Type=forking. |
I know this is closed however I am running into issues because pid is not created. on CentOS 6 I use monit to monitor for pid files, but in CentOS 7 there is no pid file. My Ansible playbook looks at the distribution major release number and based on that, monitors the path to pid file. This works fine for auditd, chronyd, crond .... I am migrating to CentOS 7 however older CentOS 6 has to be still supported. collectd: stop_script: Thanks |
Expected behavior
Pid file is created using -P /tmp/collectd.pid as argument
Actual behavior
Run manually creates PID in /tmp
sudo /opt/collectd/sbin/collectd -P /tmp/collectd.pid
Run trough systemd does not create PID
/lib/systemd/system/collectd.service
The text was updated successfully, but these errors were encountered: