Bug #5686
closedMultiple dpinger processes monitoring the same thing
100%
Description
On my test system with single WAN and 3 site-to-site OpenVPN clients I currently have 3 dpinger processes doing the same thing:
root 14675 0.0 0.1 19228 2376 - Is 3:58PM 1:08.37 /usr/local/bin/dpinger -S -i WAN_DHCP -B 10.49.209.3 -p /var/run/dpinger_WAN_DHCP_10.49.209.3_8.8.8.8.pid -u /var/run/dpinger_WAN_DHCP_10.49.209.3_8.8.8.8.sock -C /etc/rc.gateway_alarm -s 250 -l 500 -t 25000 -A 1000 -D 500 -L 20 8.8.8.8
root 29750 0.0 0.1 19228 2300 - Is 2:45PM 0:54.02 /usr/local/bin/dpinger -S -i WAN_DHCP -B 10.49.209.3 -p /var/run/dpinger_WAN_DHCP_10.49.209.3_8.8.8.8.pid -u /var/run/dpinger_WAN_DHCP_10.49.209.3_8.8.8.8.sock -C /etc/rc.gateway_alarm -s 250 -l 500 -t 25000 -A 1000 -D 500 -L 20 8.8.8.8
root 71729 0.0 0.1 19228 2376 - Ss 10:29PM 0:53.58 /usr/local/bin/dpinger -S -i WAN_DHCP -B 10.49.209.3 -p /var/run/dpinger_WAN_DHCP_10.49.209.3_8.8.8.8.pid -u /var/run/dpinger_WAN_DHCP_10.49.209.3_8.8.8.8.sock -C /etc/rc.gateway_alarm -s 250 -l 500 -t 25000 -A 1000 -D 500 -L 20 8.8.8.8
On forum thread https://forum.pfsense.org/index.php?topic=104381.0 M_Devil has a bucketload of dpinger processes.
There is some problem here. I guess somewhere (WAN up/down, VPN up/down...?) the existing dpinger process is not getting killed but a new one is being started or?
Updated by Renato Botelho almost 9 years ago
- Status changed from New to Feedback
- % Done changed from 0 to 100
Applied in changeset b76cb978611ce1ebe776685536a23c0dfcca5ed9.