systemd PIDFile /var/run Warnings
Our DNS Only server is reporting repeated systemd warnings concerning cPanel and related service unit files using the legacy /var/run/ directory in their PIDFile= configuration.
The warnings appear during system startup and/or systemd reloads.
Observed Messages
------------------------
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/tailwatchd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/tailwatchd.pid → /run/tailwatchd.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/queueprocd.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/queueprocd.pid → /run/queueprocd.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/dnsadmin.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/dnsadmin.pid → /run/dnsadmin.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/cpanel.service:10: PIDFile= references a path below legacy directory /var/run/, updating /var/run/cpsrvd.pid → /run/cpsrvd.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/cphulkd.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/cphulkd_processor.pid → /run/cphulkd_processor.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/cpgreylistd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/cpgreylistd.pid → /run/cpgreylistd.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/cpanel_php_fpm.service:8: PIDFile= references a path below legacy directory /var/run/, updating /var/run/cpanel_php_fpm.pid → /run/cpanel_php_fpm.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/cpdavd.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/cpdavd.pid → /run/cpdavd.pid; please update the unit file accordingly.
Aug 14 00:43:26 ns2 systemd[1]: /etc/systemd/system/cpanellogd.service:7: PIDFile= references a path below legacy directory /var/run/, updating /var/run/cpanellogd.pid → /run/cpanellogd.pid; please update the unit file accordingly.
Aug 14 00:43:27 ns2 NetworkManager[825]: <info> [1786632207.2289] manager: kernel firmware directory '/lib/firmware' changed
Aug 14 00:43:31 ns2 NetworkManager[825]: <info> [1786632211.6976] manager: kernel firmware directory '/lib/firmware' changed
Aug 14 00:43:37 ns2 systemd[1]: /usr/lib/systemd/system/htcacheclean.service:8: Special user nobody configured, this is not safe!
Aug 14 00:43:37 ns2 systemd[1]: /usr/lib/systemd/system/htcacheclean.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/apache2/htcacheclean/pid → /run/apache2/htcacheclean/pid; please update the unit file accordingly.
Aug 14 00:43:37 ns2 systemd[1]: /usr/lib/systemd/system/htcacheclean.service:8: Special user nobody configured, this is not safe!
Aug 14 00:43:37 ns2 systemd[1]: /usr/lib/systemd/system/htcacheclean.service:9: PIDFile= references a path below legacy directory /var/run/, updating /var/run/apache2/htcacheclean/pid → /run/apache2/htcacheclean/pid; please update the unit file accordingly.
Aug 14 00:43:38 ns2 dracut[304333]: dracut-057-117.git20260625.el9_8
Our main server has this one, kinda similar
"Aug 13 01:16:52 main_servername systemd-tmpfiles[2894223]: [/usr/lib/tmpfiles.d/ea-ruby27-passenger.conf:1] Line references path below legacy directory /var/run/, updating /var/run/ea-ruby27-passenger → /run/ea-ruby27-passenger; please update the tmpfiles.d/ drop-in file accordingly."
Are these unit files / path references expected to be maintained by cPanel and be updated by a cPanel update or maintenance process rather than manually modified?
Need to get a heads up before I get my hands dirty.
I've not made manual changes at this stage - just pending your advice.
Thank you.
-
Hey there! The short story is "annoying, but can be ignored"
as it doesn't actually affect anything working on the server.
1 -
My kinda story .... "and they all lived happily ever after".
As always, thank you.
1
Please sign in to leave a comment.
Comments
2 comments