Actions
Bug #3227
closed
apinger treats interface as down while it isn't
Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
09/24/2013
Due date:
% Done:
0%
Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.0.1
Affected Architecture:
i386
Description
This issue affects a 2.0.1 installation and might be fixed in 2.1. There is eg. bug 3138 but that one was affecting 2.1-rc1 first and is fixed for 2.1. Maybe this is related to bug 3191 though. I file this bug because I have access to the device right now and can gather data. I hope that I'll have time for an upgrade to 2.1 later this week.
In short: This is a system with two uplinks and pfSense thinks one is down most the time while it actually isn't. It looks like apinger is confused.
[2.0.1-RELEASE][root@pfsense.example.net]/etc(37): cat /tmp/apinger.status 123.117.24.1|123.117.29.249|GW_OPT3|5353|0|0|0.000ms|100.0%|down 122.113.34.3|122.113.34.4|PublicGW|5353|5344|1380002366|1.679ms|0.0%|none [2.0.1-RELEASE][root@pfsense.example.net]/etc(38): ls -l /tmp/apinger.status -rw-r--r-- 1 root wheel 143 Sep 24 13:59 /tmp/apinger.status [2.0.1-RELEASE][root@pfsense.example.net]/etc(39): ping -nq -c 120 -S 123.117.29.249 123.117.24.1 PING 123.117.24.1 (123.117.24.1) from 123.117.29.249: 56 data bytes --- 123.117.24.1 ping statistics --- 120 packets transmitted, 119 packets received, 0.8% packet loss round-trip min/avg/max/stddev = 11.270/30.469/155.542/22.397 ms [2.0.1-RELEASE][root@pfsense.example.net]/etc(40): cat /tmp/apinger.status 123.117.24.1|123.117.29.249|GW_OPT3|5487|0|0|0.000ms|100.0%|down 122.113.34.3|122.113.34.4|PublicGW|5487|5478|1380002501|1.021ms|0.0%|none [2.0.1-RELEASE][root@pfsense.example.net]/etc(41): ls -l /tmp/apinger.status -rw-r--r-- 1 root wheel 143 Sep 24 14:01 /tmp/apinger.status
Files
Updated by Malte Stretz about 11 years ago
The RRD graph. Most the time when apinger thought this link was down it was actually working fine.
Updated by Malte Stretz about 11 years ago
[2.0.1-RELEASE][root@pfsense.example.net]/etc(43): tail -n 40 /var/log/apinger.log Sep 23 12:46:16 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Sep 23 12:47:55 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Sep 23 12:57:29 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Sep 23 12:57:36 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Sep 23 14:35:25 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Sep 23 14:35:34 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Sep 23 14:59:28 pfsense apinger: Exiting on signal 15. Sep 23 14:59:29 pfsense apinger: Starting Alarm Pinger, apinger(5286) Sep 23 14:59:39 pfsense apinger: ALARM: GW_OPT3(123.117.224.1) *** down *** Sep 23 15:00:29 pfsense apinger: Error while feeding rrdtool: Broken pipe Sep 23 15:00:29 pfsense apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s. Sep 23 17:38:01 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Sep 23 17:38:39 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** loss *** Sep 23 17:39:34 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Sep 23 17:40:24 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** loss *** Sep 23 20:16:02 pfsense apinger: alarm canceled: GW_OPT3(123.117.224.1) *** down *** Sep 24 09:51:57 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Sep 24 09:52:50 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Sep 24 09:53:09 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Sep 24 09:53:41 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Sep 24 12:29:27 pfsense apinger: Exiting on signal 15. Sep 24 12:29:28 pfsense apinger: Starting Alarm Pinger, apinger(10062) Sep 24 12:29:29 pfsense apinger: Exiting on signal 15. Sep 24 12:29:30 pfsense apinger: Starting Alarm Pinger, apinger(57303) Sep 24 12:29:40 pfsense apinger: ALARM: GW_OPT3(123.117.24.1) *** down *** Sep 24 12:30:30 pfsense apinger: Error while feeding rrdtool: Broken pipe Sep 24 12:30:30 pfsense apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s. delay *** Aug 14 10:14:53 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Aug 14 10:16:11 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Aug 14 10:18:00 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Aug 14 10:18:29 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Aug 14 10:18:51 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Aug 14 10:21:59 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Aug 14 10:22:28 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay *** Aug 14 10:24:23 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** delay *** Aug 14 10:25:42 pfsense apinger: ALARM: PublicGW(122.113.34.3) *** loss *** Aug 14 10:26:41 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** loss *** Aug 14 10:32:01 pfsense apinger: alarm canceled: PublicGW(122.113.34.3) *** delay ***
Updated by Chris Buechler about 10 years ago
- Status changed from New to Closed
not an apparent issue on 2.2 (unless this somehow overlapped with separate issues open there)
Actions