Page 1 of 1

lfd keep failing on Cloudlinux 7

Posted: 22 Feb 2016, 20:14
by puppet
Hello,

I installed CSF on Cloudlinux 7 + cpanel server. I disabled firewalld and installed iptables instead. However, the LFD service keep failing after about 30 mins.

# cat /etc/csf/csf.error

Code: Select all

Error: FASTSTART: (DROP no logging IPv4) [] [iptables-restore: line 20 failed]. Try restarting csf with FASTSTART disabled, at line 4738 in /usr/sbin/csf
The startup log shows the lfd.service was killed, but I have no idea why it was killed.

Startup Log

Code: Select all

Feb 22 11:25:42 server.domain.com systemd[1]: Starting ConfigServer Firewall & Security - lfd...
Feb 22 11:25:43 server.domain.com systemd[1]: Started ConfigServer Firewall & Security - lfd.
Feb 22 12:00:51 server.domain.com systemd[1]: lfd.service: main process exited, code=killed, status=9/KILL
Feb 22 12:00:51 server.domain.com systemd[1]: Unit lfd.service entered failed state.
Feb 22 12:00:51 server.domain.com systemd[1]: lfd.service failed.

Re: lfd keep failing on Cloudlinux 7

Posted: 21 Apr 2016, 16:47
by kjg
Did you solve this?

We are getting the same problems on a Cloudlinux 7 + cpanel server

Starting ConfigServer Firewall & Security - lfd...
lfd.service: control process exited, code=killed status=9
Failed to start ConfigServer Firewall & Security - lfd.
Unit lfd.service entered failed state.
lfd.service failed.

Re: lfd keep failing on Cloudlinux 7, Centos7 + Cpanel

Posted: 04 May 2016, 12:25
by m7000
Hi,

same Problem here. Also Centos7,cloudlinux and cpanel.
After some time of successfull running from one to other second failed with same error Messages as above and won't start again anymore after.
After same as in above posts written errors/kill got this always repeated later in log and csf/lfd not started again:

May 4 06:29:33 htt systemd: PID file /var/run/lfd.pid not readable (yet?) after start.

A manual restart also not worked. Only after disabled FASTSTART it came up for some minutes (..only).
Are there any solution already related this or anyone else with same Problems ? Maybe it's a bug ?