New apinger problems when monitoring HE ipv6 tunnel

[gogol]

Like the title says I am monitoring a Tunnelbroker tunnel which every now and then has some packet loss or longer RTT. I disabled that monitoring in 2.1 because a pinger showed long delays while there weren't any delays at the moment and showed an orange status. Something stayed in memory I guess.
With this 2.1.1 version I enabled the monitoring again, but now my logs show this:

an 24 11:27:54	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns GwIpv6' -c 'service reload ipsecdns' -c 'service reload openvpn GwIpv6' -c 'filter reload' ) exited with status: 255
Jan 24 11:27:54	a pinger: Error while starting command form alarm(delay) on target(2001:470:xxxx:xxxx::1-GwIpv6)
Jan 24 11:27:46	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns GwIpv6' -c 'service reload ipsecdns' -c 'service reload openvpn GwIpv6' -c 'filter reload' ) exited with status: 255
Jan 24 11:27:46	a pinger: Error while starting command form alarm(delay) on target(2001:470:xxxx:xxxx::1-GwIpv6)
Jan 24 11:27:44	apinger: alarm canceled: GwIpv6(2001:470:xxxx:xxxx::1) *** delay ***
Jan 24 11:27:36	apinger: ALARM: GwIpv6(2001:470:xxxx:xxxx::1) *** delay ***

[jimp]

What is the build time on the snapshot you're using? If it's from earlier than Thursday, upgrade and check it again.

[gogol]

2.1.1-PRERELEASE (amd64) 
built on Thu Jan 23 17:15:05 EST 2014 
FreeBSD 8.3-RELEASE-p14

Still the same error. Would there be something I can change?

[Cino]

i'm seeing a similar results on my box also

Jan 25 08:59:27 	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN_IPv6' -c 'service reload ipsecdns' -c 'service reload openvpn WAN_IPv6' -c 'filter reload' ) exited with status: 255
Jan 25 08:59:27 	apinger: Error while starting command form alarm(delay) on target(2001:470:xxxx:xxxx::1-WAN_IPv6)
Jan 25 08:59:27 	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN_DHCP' -c 'service reload ipsecdns' -c 'service reload openvpn WAN_DHCP' -c 'filter reload' ) exited with status: 255
Jan 25 08:59:27 	apinger: Error while starting command form alarm(delay) on target(68.xxx.xxx.1-WAN_DHCP)
Jan 25 08:59:19 	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN_IPv6' -c 'service reload ipsecdns' -c 'service reload openvpn WAN_IPv6' -c 'filter reload' ) exited with status: 255
Jan 25 08:59:19 	apinger: Error while starting command form alarm(delay) on target(2001:470:xxxx:xxxx::1-WAN_IPv6)
Jan 25 08:59:19 	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns WAN_DHCP' -c 'service reload ipsecdns' -c 'service reload openvpn WAN_DHCP' -c 'filter reload' ) exited with status: 255
Jan 25 08:59:19 	apinger: Error while starting command form alarm(delay) on target(68.xxx.xxx.1-WAN_DHCP)
Jan 25 08:59:17 	apinger: alarm canceled: WAN_IPv6(2001:470:xxx:xxx::1) *** delay ***
Jan 25 08:59:17 	apinger: alarm canceled: WAN_DHCP(68.xxx.xxx.1) *** delay ***
Jan 25 08:59:09 	apinger: ALARM: WAN_IPv6(2001:470:xxx:xxx::1) *** delay ***
Jan 25 08:59:09 	apinger: ALARM: WAN_DHCP(68.xxx.xxx.1) *** delay ***

Not sure if its apinger or my connection, but 4-6 months ago apinger started to report packet lost/delay (around the same time there were many changes to the binary)… I could be wrong but I felt that apinger became way too sensitive.. Running a speedtest to over my WAN, apinger would report there is packet lost/connect down while the test is running.  I fine tuned the gateway settings so it wouldn't report (in my eyes) false findings.

[doktornotor]

2.1.1-PRERELEASE (i386) 
built on Sat Jan 25 10:00:56 EST 2014 
FreeBSD 8.3-RELEASE-p14

Same problem.

Jan 26 14:46:42	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns HEIPv6GW' -c 'service reload ipsecdns' -c 'service reload openvpn HEIPv6GW' -c 'filter reload' ) exited with status: 255
Jan 26 14:46:42	apinger: Error while starting command form alarm(down) on target(2001:470:6e:xxx::x-HEIPv6GW)
Jan 26 14:46:32	apinger: alarm canceled: HEIPv6GW(2001:470:6e:xxx::x) *** down ***
Jan 26 14:42:56	apinger: command (/usr/local/sbin/pfSctl -c 'service reload dyndns HEIPv6GW' -c 'service reload ipsecdns' -c 'service reload openvpn HEIPv6GW' -c 'filter reload' ) exited with status: 255
Jan 26 14:42:56	apinger: Error while starting command form alarm(down) on target(2001:470:6e:xxx::x-HEIPv6GW)
Jan 26 14:42:46	apinger: ALARM: HEIPv6GW(2001:470:6e:xxx::x) *** down ***
Jan 26 12:26:59	apinger: Starting Alarm Pinger, apinger(27054)

I have strong feeling reverting the apinger thing back to 2.1 state would be a nice improvement.

[Nukama]

I had this problem, too.
With 2.1.1-PRERELEASE (amd64) built on Wed Jan 29 16:03:22 EST 2014 (or some earlier version)
the RRD graphs are working for my HE IPv6 Tunnel.

Thanks

[jimp]

Next new snap should be OK
https://forum.pfsense.org/index.php/topic,71555.msg393514.html#msg393514

[gogol]

I think it is ok now. Running the latest "built on Fri Jan 31 10:30:26 EST 2014" snapshot for about three hours.

I don't know how apinger does the calculations but I had a lot of delay messages but without the 255 exit codes after this update.
I just deleted the gateway under Routing:Gateways and recreated it with another name.

Thanks!