ConfigServer Community Forum

Sorry for the delayed response... The firewall should start *before* the network is up. That is why iptables starts at 08 and network at 10. I recommend 09 based on your response, however, 12 would be better than nothing (c[sf] would still start before s[ssd]). I guess it doesn't really matter becau...

The solution to this issue (in case you happen upon this ancient post) is that your iptables commands in csfpre.sh must have the full path to iptables (i.e. /sbin/iptables). The "update" process that automatically restarts does not have /sbin in its path.

We also have an issue where several of our systems are getting defunct lfd processes. 1. Type of Virtual Server: VMWare 2. Kernel Version: 2.6.32-642.3.1.el6.x86_64 3. OS/Version: CentOS 6.8 4. Memory: 16GB 5. Process Name: [lfd] Details: # ps -ef | grep lfd root 6678 1 0 00:07 ? 00:00:17 lfd - slee...

We have seen this problem several times as well. I have a sneaking suspicion that it has something to do with automatic updates.

Hi, We are having a bad interaction between CSF and SSSD. SSSD starts at 12 and CSF starts at 15. When CSF starts, it starts blocking packets for a period of time (sometimes several seconds) while it sorts out its policies (csf.allow). We do not have an extensive set of policies, but maybe 20 or so ...