Bug #2737
closedexcessive filterdns processes in some circumstance(s)
0%
Description
Some people are seeing huge numbers of filterdns processes. For instance:
http://forum.pfsense.org/index.php/topic,57143.0.html
on the filter's instance of filterdns. Not seeing that on one of our systems, but another has 3 instances running. It doesn't appear to be happening because of the filter reload process. On the system where I'm seeing 3 instances:
[2.1-BETA1][root@fw1.hq.pfsense.org]/root(5): cat /tmp/filterdns.pid 56384 [2.1-BETA1][root@fw1.hq.pfsense.org]/root(6): ps ax|grep filter 40134 ?? Is 0:00.01 /usr/local/sbin/filterdns -p /tmp/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 56384 ?? Is 0:00.01 /usr/local/sbin/filterdns -p /tmp/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 59963 ?? INs 0:00.01 /usr/local/sbin/filterdns -p /tmp/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 10540 0 S+ 0:00.00 grep filter [2.1-BETA1][root@fw1.hq.pfsense.org]/root(7): /etc/rc.filter_configure_sync [2.1-BETA1][root@fw1.hq.pfsense.org]/root(8): ps ax | grep filter 15260 ?? Ss 0:00.01 /usr/local/sbin/filterdns -p /tmp/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 40134 ?? Is 0:00.01 /usr/local/sbin/filterdns -p /tmp/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 59963 ?? INs 0:00.01 /usr/local/sbin/filterdns -p /tmp/filterdns.pid -i 300 -c /var/etc/filterdns.conf -d 1 15554 0 S+ 0:00.00 grep filter [2.1-BETA1][root@fw1.hq.pfsense.org]/root(9): cat /tmp/filterdns.pid 15260
That part at least is killing off the instance it knows about via its PID file, and re-launching it correctly. Something else is somehow duplicating instances of the process.
Updated by Dim Hatz almost 12 years ago
A small fix to consider while looking at the issue of multiple filterdns processes, is that the scripts invoking filterdns should use a consistent path for all the pid files.
Because currently pid files are stored them in both /tmp and /var/run ...
/tmp/filterdns.pid
/var/run/filterdns-ipsec.pid
Updated by Ermal Luçi almost 12 years ago
- Status changed from New to Resolved
- Assignee set to Ermal Luçi
This is solved now days since filterdns just reloads config and does not need to be restarted on change.