Actions
Bug #8057
closed
don't start dpinger if still one running
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
-
Start date:
11/06/2017
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.4.1
Affected Architecture:
Description
It's the 2nd or 3rd time I see multiple instances of dpinger.
You have a pid file and can check for the process before spawning a new one or really kill the old one.
root 48040 0.0 0.1 10980 2428 - Is Thu22 0:31.70 /usr/local/bin/dpinger -S -r 0 -i OV_1_VPNV4 -B 10.190.254.17 -p /var/run/dpinger_OV_1_VPNV4~10.190.254.17~10.190 root 85613 0.0 0.1 13028 2472 - Is Thu22 0:29.85 /usr/local/bin/dpinger -S -r 0 -i OV_1_VPNV4 -B 10.190.254.17 -p /var/run/dpinger_OV_1_VPNV4~10.190.254.17~10.190 root 47834 0.0 0.1 10980 2428 - Is Thu22 0:27.42 /usr/local/bin/dpinger -S -r 0 -i OV_2_VPNV4 -B 10.190.254.93 -p /var/run/dpinger_OV_2_VPNV4~10.190.254.93~10 root 53187 0.0 0.1 10980 2428 - Is Thu22 0:28.05 /usr/local/bin/dpinger -S -r 0 -i OV_3_VPNV4 -B 10.190.254.85 -p /var/run/dpinger_OV_3_VPNV4~10.190.254.85~10.190.254.8 root 47031 0.0 0.1 10980 2428 - Is Thu22 0:27.30 /usr/local/bin/dpinger -S -r 0 -i OV_4_VPNV4 -B 10.190.254.6 -p /var/run/dpinger_OV_4_VPNV4~10.190.254.6~10.190.254.5.p root 48097 0.0 0.1 10980 2428 - Is Thu22 0:27.37 /usr/local/bin/dpinger -S -r 0 -i OV_5_VPNV4 -B 10.190.254.97 -p /var/run/dpinger_OV_5_VPNV4~10.190.254.97~10.1 root 49378 0.0 0.1 10980 2428 - Is Thu22 0:31.68 /usr/local/bin/dpinger -S -r 0 -i OV_6_VPNV4 -B 10.190.254.53 -p /var/run/dpinger_OV_6_VPNV4~10.190.254.53~10.190.2 root 86881 0.0 0.1 13028 2472 - Is Thu22 0:29.53 /usr/local/bin/dpinger -S -r 0 -i OV_6_VPNV4 -B 10.190.254.53 -p /var/run/dpinger_OV_6_VPNV4~10.190.254.53~10.190.2 root 49747 0.0 0.1 10980 2428 - Is Thu22 0:31.65 /usr/local/bin/dpinger -S -r 0 -i OV_7_VPNV4 -B 10.190.254.57 -p /var/run/dpinger_OV_7_VPNV4~10.190.254.57~10.190.254.58.pid root 88247 0.0 0.1 13028 2472 - Is Thu22 0:29.50 /usr/local/bin/dpinger -S -r 0 -i OV_7_VPNV4 -B 10.190.254.57 -p /var/run/dpinger_OV_7_VPNV4~10.190.254.57~10.190.254.58.pid root 51632 0.0 0.1 10980 2428 - Is Thu22 0:28.08 /usr/local/bin/dpinger -S -r 0 -i OV_8_VPNV4 -B 10.190.254.69 -p /var/run/dpinger_OV_8_VPNV4~10.190.254.69~10.190.254.7 root 50210 0.0 0.1 13028 2472 - Is Thu22 0:31.65 /usr/local/bin/dpinger -S -r 0 -i OV_9_VPNV4 -B 10.190.254.77 -p /var/run/dpinger_OV_9_VPNV4~10.190.254.77~10.190.254.7 root 89323 0.0 0.1 13028 2472 - Is Thu22 0:29.91 /usr/local/bin/dpinger -S -r 0 -i OV_9_VPNV4 -B 10.190.254.77 -p /var/run/dpinger_OV_9_VPNV4~10.190.254.77~10.190.254.7 root 47386 0.0 0.1 10980 2428 - Is Thu22 0:31.19 /usr/local/bin/dpinger -S -r 0 -i OV_10_VPNV4 -B 10.190.254.9 -p /var/run/dpinger_OV_10_VPNV4~10.190.254.9~10.190 root 84872 0.0 0.1 13028 2472 - Is Thu22 0:29.52 /usr/local/bin/dpinger -S -r 0 -i OV_10_VPNV4 -B 10.190.254.9 -p /var/run/dpinger_OV_10_VPNV4~10.190.254.9~10.190 root 52511 0.0 0.1 10980 2428 - Is Thu22 0:27.66 /usr/local/bin/dpinger -S -r 0 -i OV_11_VPNV4 -B 10.190.254.81 -p /var/run/dpinger_OV_11_VPNV4~10.190.254.81~10.190.254.8 root 52011 0.0 0.1 10980 2428 - Is Thu22 0:27.93 /usr/local/bin/dpinger -S -r 0 -i OV_12_VPNV4 -B 10.190.254.73 -p /var/run/dpinger_OV_12_VPNV4~10.190.254.73~10.190.254.7 root 48873 0.0 0.1 13028 2472 - Is Thu22 0:32.06 /usr/local/bin/dpinger -S -r 0 -i OV_13_VPNV4 -B 10.190.254.49 -p /var/run/dpinger_OV_13_VPNV4~10.190.254.49~ root 86121 0.0 0.1 13028 2472 - Is Thu22 0:30.28 /usr/local/bin/dpinger -S -r 0 -i OV_13_VPNV4 -B 10.190.254.49 -p /var/run/dpinger_OV_13_VPNV4~10.190.254.49~ root 46738 0.0 0.1 13028 2472 - Is Thu22 0:31.43 /usr/local/bin/dpinger -S -r 0 -i OV_14_VPNV4 -B 10.190.254.1 -p /var/run/dpinger_OV_14_VPNV4~10.190.254.1~10.190.254 root 84321 0.0 0.1 13028 2472 - Is Thu22 0:29.65 /usr/local/bin/dpinger -S -r 0 -i OV_14_VPNV4 -B 10.190.254.1 -p /var/run/dpinger_OV_14_VPNV4~10.190.254.1~10.190.254 root 51100 0.0 0.1 13028 2472 - Is Thu22 0:27.75 /usr/local/bin/dpinger -S -r 0 -i OV_15_VPNV4 -B 10.190.254.65 -p /var/run/dpinger_OV_15_VPNV4~10.190.254.65~10.190.254.66. root 51373 0.0 0.1 13028 2468 - Is Thu22 0:21.74 /usr/local/bin/dpinger -S -r 0 -i OV_16_VPNV4 -B 10.190.253.241 -p /var/run/dpinger_OV_16_VPNV4~10.190.253.241~10.190.253.242.p root 48586 0.0 0.1 10980 2428 - Is Thu22 0:27.79 /usr/local/bin/dpinger -S -r 0 -i OV_17_V2_VPNV4 -B 10.190.252.1 -p /var/run/dpinger_OV_17_VPNV4~10.190.252. root 50533 0.0 0.1 10980 2428 - Is Thu22 0:30.74 /usr/local/bin/dpinger -S -r 0 -i OV_18_VPNV4 -B 10.190.255.1 -p /var/run/dpinger_OV_18_VPNV4~10.190.255.1~10.1 root 90188 0.0 0.1 10980 2428 - Is Thu22 0:29.86 /usr/local/bin/dpinger -S -r 0 -i OV_18_VPNV4 -B 10.190.255.1 -p /var/run/dpinger_OV_18_VPNV4~10.190.255.1~10.1 root 46286 0.0 0.1 10980 2428 - Is Thu22 2:39.05 /usr/local/bin/dpinger -S -r 0 -i WAN_GW -B 1.2.3.4 -p /var/run/dpinger_WAN_GW~1.2.3.4~5.6.7.8.pid -u /va root 83608 0.0 0.1 10980 2428 - Is Thu22 2:38.42 /usr/local/bin/dpinger -S -r 0 -i WAN_GW -B 1.2.3.4 -p /var/run/dpinger_WAN_GW~1.2.3.4~5.6.7.8.pid -u /va root 45992 0.0 0.1 10980 2428 - Is Thu22 0:31.00 /usr/local/bin/dpinger -S -r 0 -i self -B 10.190.0.1 -p /var/run/dpinger_self~10.190.0.1~10.190.0.1.pid -u /var/run/dpinger_self~ root 83059 0.0 0.1 10980 2428 - Is Thu22 0:30.01 /usr/local/bin/dpinger -S -r 0 -i self -B 10.190.0.1 -p /var/run/dpinger_self~10.190.0.1~10.190.0.1.pid -u /var/run/dpinger_self~
Even for the local interface I see this and it's never going down, because it's a vif from xen:
root 45992 0.0 0.1 10980 2428 - Is Thu22 0:31.00 /usr/local/bin/dpinger -S -r 0 -i self -B 10.190.0.1 -p /var/run/dpinger_self~10.190.0.1~10.190.0.1.pid -u /var/run/dpinger_self~
root 83059 0.0 0.1 10980 2428 - Is Thu22 0:30.01 /usr/local/bin/dpinger -S -r 0 -i self -B 10.190.0.1 -p /var/run/dpinger_self~10.190.0.1~10.190.0.1.pid -u /var/run/dpinger_self~
em0.1000: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=3<RXCSUM,TXCSUM>
ether 02:0a:3e:70:c2:30
inet6 fe80::a:3eff:fe70:c230%em0.1000 prefixlen 64 scopeid 0x7
inet 10.190.0.1 netmask 0xffffff00 broadcast 10.190.0.255
inet 192.168.255.255 netmask 0xffffffff broadcast 192.168.255.255
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
vlan: 1000 vlanpcp: 0 parent interface: em0
groups: vlan
To "repair" this I send a killall -9 dpinger and restart dpinger on dashboard.
Updated by Jim Pingle over 4 years ago
- Category set to Gateway Monitoring
- Status changed from New to Closed
Old report and no recent recurrences. Lots of things in this area have changed, so most likely it's either fixed no longer relevant.
Actions