ConfigServer Community Forum

i have the following in logs trying to start lfd:

pr 2 10:27:39 server1 lfd[18020]: Email Script Tracking...
Apr 2 10:27:39 server1 lfd[18020]: Email Queue Tracking...
Apr 2 10:27:39 server1 lfd[18020]: Email Relay Tracking...
Apr 2 10:27:39 server1 lfd[18020]: Temp to Perm Block Tracking...
Apr 2 10:27:39 server1 lfd[18020]: Port Scan Tracking...
Apr 2 10:27:39 server1 lfd[18020]: Process Tracking...
Apr 2 10:27:40 server1 lfd[18020]: Account Tracking...
Apr 2 10:27:40 server1 lfd[18020]: User Process Tracking...
Apr 2 10:27:40 server1 lfd[18020]: SSH Tracking...
Apr 2 10:27:40 server1 lfd[18020]: SU Tracking...
Apr 2 10:27:40 server1 lfd[18020]: Watching /var/log/maillog...
Apr 2 10:27:40 server1 lfd[18020]: Watching /var/log/exim_mainlog...
Apr 2 10:27:40 server1 lfd[18020]: Watching /var/log/messages...
Apr 2 10:27:40 server1 lfd[18020]: Watching /var/log/secure...
Apr 2 10:27:40 server1 lfd[18020]: Watching /usr/local/cpanel/logs/login_log...
Apr 2 10:27:40 server1 lfd[18020]: Watching /usr/local/apache/logs/error_log...
Apr 2 10:27:40 server1 lfd[18031]: iptables command [/sbin/iptables -D LOCALINPUT -i ! lo -s 216.108.235.202 -j DROP] failed, at line 4222
Apr 2 10:27:40 server1 lfd[18031]: daemon stopped
Apr 2 10:27:45 server1 lfd[18020]: Error: pid mismatch or missing, at line 566
Apr 2 10:27:45 server1 lfd[18020]: daemon stopped


Seems, that lfd tries to delete some rule, that do not exists.
Cleaned out /etc/csf/csf.tempban and /etc/csf/csf.tempip and started successfully.
Can this caused by switching from non-testing to the testing mode?

Can lfd ignore such bad rules command and start anyway?

Yes, it's from being in TESTING mode. When TESTING is disabled it's more tolerant of iptables command failures. I'll make a development note to relax the tolerance of such failures whether in TESTING mode or not for the next release.