On Tue, Aug 4, 2009 at 10:56 AM, Matthias Niggemeier<[email protected]> wrote: > Von: Matthias Niggemeier [mailto:[email protected]] > Gesendet: Dienstag, 4. August 2009 08:47 > An: [email protected] > Betreff: [pfSense Support] Problem with apinger > >> Hi there, >>since the upgrade to 1.2.3-RC2 (July 23) parts of my failoverpools go > offline once a day. The system log shows entries >like this: >> >>apinger: ALARM: 208.67.220.220(208.67.220.220) *** down ***. Loss 0.0%, > Delay 75.436ms >> >>In this situation, I have to go to load_balancer_pool.php, edit one pool > and hit save. After that, everything is >>fine and online. >>Is there a workaround for this? > > Update: > > The sequence before failing is as follows: > > Aug 4 15:38:33 apinger: Target "208.67.220.220": Lost packet count mismatch > (-7(recently_lost) != 0(really_lost))! > Aug 4 15:38:33 apinger: Target "208.67.220.220": Received packets buffer: > ################################################## #................... > Aug 4 15:38:40 apinger: ALARM: 208.67.220.220(208.67.220.220) *** down ***. > Loss 12.0%, Delay 72.620ms > > After that apinger does not recover until I go to the pool configuration and > hit save.
This is a known issue that we are working on. No workarounds exist at present. Scott --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected] Commercial support available - https://portal.pfsense.org
