Project

General

Profile

Actions

Bug #16077

open

dpinger not reliable - ping request/replies

Added by Stefan Bauer about 1 month ago. Updated about 1 month ago.

Status:
Incomplete
Priority:
Normal
Assignee:
-
Category:
Gateway Monitoring
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Default
Affected Version:
2.7.x
Affected Architecture:

Description

The running dpinger process, seems to be stall for no reason, hence reporting the gateway as down, but it is not:

root 62188 0.0 0.0 17736 2808 - Is Sat13 0:27.94 /usr/local/bin/dpinger -S -r 0 -i GW_KD -B 10.8.0.2 -p /var/run/dpinger_GW_KD_DH~10.8.0.2~1.1.1.1.pid -u /var/run/dpinger_GW_KD_DH~10.8.0.2~1.1.1.1.sock -C /etc/rc.gateway_alarm -d 1 -s 500 -l 2000

[2.7.2-RELEASE][admin@dhpn]/root: tcpdump -ni vtnet2 host 1.1.1.1
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on vtnet2, link-type EN10MB (Ethernet), snapshot length 262144 bytes
08:59:31.311619 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59301, length 9
08:59:31.820832 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59302, length 9
08:59:32.331754 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59303, length 9
08:59:32.840861 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59304, length 9
08:59:33.350907 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59305, length 9
08:59:33.862761 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59306, length 9
08:59:34.371285 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 62188, seq 59307, length 9

Saving the gateway configuration without any changes, "re-starts" the dpinger and pings are working again.

09:03:10.976622 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 0, length 9
09:03:11.001018 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 0, length 9
09:03:11.481186 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 1, length 9
09:03:11.503886 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 1, length 9
09:03:11.991642 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 2, length 9
09:03:12.011385 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 2, length 9
09:03:12.501207 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 3, length 9
09:03:12.518272 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 3, length 9
09:03:13.011616 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 4, length 9
09:03:13.026412 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 4, length 9
09:03:13.521414 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 5, length 9
09:03:13.541170 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 5, length 9
09:03:14.040837 IP 10.8.0.2 > 1.1.1.1: ICMP echo request, id 37365, seq 6, length 9
09:03:14.057380 IP 1.1.1.1 > 10.8.0.2: ICMP echo reply, id 37365, seq 6, length 9

Actions #1

Updated by Jim Pingle about 1 month ago

  • Status changed from New to Incomplete

There isn't nearly enough information here to identify any specific problem. It's most likely not dpinger but something in the system routing or firewall states that gets corrected by the combinations of actions taken when reapplying gateway settings. Before anything can be fully determined there needs to be an identified cause for why it stops working, and ideally a way to replicate that on demand.

The forum is the proper place for that discussion and diagnosis. This can be reopened once sufficient information has been collected.

Actions

Also available in: Atom PDF