Page 1 of 1

systemd issue due to recent update

Posted: 18 Sep 2019, 08:21
by tanfwc
Error log

Sep 18 14:41:18 moon systemd[1]: Starting ConfigServer Firewall & Security - lfd...
Sep 18 14:41:19 moon systemd[1]: Can't open PID file /var/run/lfd.pid (yet?) after start: Too many levels of symbolic links
Sep 18 14:42:48 moon systemd[1]: lfd.service start operation timed out. Terminating.
Sep 18 14:42:48 moon systemd[1]: Failed to start ConfigServer Firewall & Security - lfd.
Sep 18 14:42:48 moon systemd[1]: Unit lfd.service entered failed state.
Sep 18 14:42:48 moon systemd[1]: lfd.service failed.
Warning: Journal has been rotated since unit was started. Log output is incomplete or unavailable.

Temporary Solution
cat /etc/systemd/system/lfd.service.d/override.conf
[Service]
PIDFile=/run/lfd.pid

This seems to only affect some system, not sure why but hope this information helps

Re: systemd issue due to recent update

Posted: 18 Sep 2019, 16:20
by mediast
We're having the exact same issue, but your temporary fix did not work. Also not impacting all of our servers.

Nick

Re: systemd issue due to recent update

Posted: 18 Sep 2019, 17:19
by tanfwc
Can provide me some log to have a look?

Re: systemd issue due to recent update

Posted: 27 Sep 2019, 20:29
by getvipin
mediast wrote: 18 Sep 2019, 16:20 We're having the exact same issue, but your temporary fix did not work. Also not impacting all of our servers.

Nick
Looks like the issue is with CentOS 7.7 update ?
Try using,
1) # systemctl edit lfd.service
2) Add these lines
[Service]
PIDFile=/run/lfd.pid
3) systemctl daemon-reload
4) Restart lfd

Thanks,
Vipin

Re: systemd issue due to recent update

Posted: 28 Sep 2019, 15:53
by ForumAdmin
getvipin wrote: 27 Sep 2019, 20:29
mediast wrote: 18 Sep 2019, 16:20 We're having the exact same issue, but your temporary fix did not work. Also not impacting all of our servers.

Nick
Looks like the issue is with CentOS 7.7 update ?
Try using,
1) # systemctl edit lfd.service
2) Add these lines
[Service]
PIDFile=/run/lfd.pid
3) systemctl daemon-reload
4) Restart lfd

Thanks,
Vipin
That should resolve the issue for now. We will have this modification to the lfd service in the next release.