An earnest appeal - please do fix APINGER in 2.2

eri--

You really need to have a fixed time.
Otherwise you will get wierd results from apinger.

maverick_slo

Disable hyper-v time sync you really don`t need it…

applerule

Figured I'd chime back in with an update. Still on Monday Oct 06 snapshot, and no weird issues with apinger. I have had a legitmate outage during this time and everything has recovered as expected. I am not sure if ermal's modifications or me disabling hyper-v time sync fixed it. It could be a combination of both. Either way ermal pointed me in the right direction and all still appears good on my end. I suggest anyone else with the problem to disable hyper-v time sync and configure ntp and see if that resolves your issue. :)

Supermule

I havent had the issue since I initiated time sync via Vsphere client on the hosts.

Oct 17 19:59:33 apinger: SIGHUP received, reloading configuration.
Oct 17 19:59:32 apinger: Starting Alarm Pinger, apinger(21363)
Oct 17 18:56:57 apinger: alarm canceled: WAN_DHCP(62.243.131.197) *** delay ***
Oct 17 18:56:49 apinger: ALARM: WAN_DHCP(62.243.131.197) *** delay ***

naras

Hyper-v time sync disabled, kern.timecounter.hardware set to ACPI-fast, now it's all good.

Thanks to all of you.

firewalluser

On the point of some people have experienced this but not commented, I'd just say having skimmed through the thread, symptoms seem consistent with what I have seen so will try out some of the suggestions to see where it gets me.

I havent seen it on a vm of 2.1.4 but have seen it on real hw using the amd64 2.1.4 release though, so yes quite difficult to replicate.

naras

@naras:

Hyper-v time sync disabled, kern.timecounter.hardware set to ACPI-fast, now it's all good.

Thanks to all of you.

This worked once, I just can't get my timing correct, OPT1 is always offline after a upgrade or reboot.

I've tried almost all snapshots and all combinations of timecounter, ntpd never worked with TSC, shows "unreach/pending" for all time servers in the ntp status page, ntpd works with the timecounter i8254, but pfsense 2.2 get frozen after a period of time, and ntpd works great with Hyper-V and ACPI-fast counters, but OPT1 is always offline after upgrade or reboot.

Hyper-v time syc disabled already, and two pppoe line are from same ISP.

Please help me out, thanks.

Maybe I was just too hasty to see good results, didn't give Apinger enough time to recover. I waited for enough time after upgraded to latest snapshot, and did see OPT1 online.

thiagoc

I can reproduce the problem with one interface using a external monitor IP (I've used OpenDNS) with RTT > 150ms and the other using the gateway as monitor IP (RTT < 2ms).

2.1.5-RELEASE (amd64)

EDIT: actually the problem occurs also with the other external monitor IP. How can I enable the debug on apinger? Is there a way to use the new version of apinger on 2.1.5?

cmb

You'll need to go to 2.2 if you want to try out the new apinger. That's pretty low-risk at this point, outside of some packages that need some work still.

cmb

locking this thread since it keeps getting hijacked, the original issues have been confirmed resolved, new ones need their own threads so we can follow up appropriately.