Project

General

Profile

Bug #536

apinger at times fails to touch filter_dirty

Added by Chris Buechler about 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
-
Category:
Multi-WAN
Target version:
Start date:
04/22/2010
Due date:
% Done:

100%

Estimated time:
Affected Version:
2.0
Affected Architecture:

Description

apinger at times fails to touch filter_dirty because it appears something messes with the perms on /tmp

Apr 22 09:45:46    apinger: command (/usr/bin/touch /tmp/filter_dirty) exited with status: 1
Apr 22 09:45:46    apinger: Error while starting command.

Associated revisions

Revision 0534d60a (diff)
Added by Chris Buechler about 9 years ago

temporary work around for ticket #536

Revision 01207fd8 (diff)
Added by Ermal Luçi about 9 years ago

Fixes #536. More fixes and optimizations on the various functions and status pages used for gateways [groups].

Revision fe22a89b (diff)
Added by Ermal Luçi about 9 years ago

Fixes #536. More fixes and optimizations on the various functions used for gateways [groups].

Revision d9dda2a5 (diff)
Added by Ermal Luçi about 9 years ago

Fixes #536. Actually add all available gateways to the gateway_groups array so all up members will be present for balancing.

History

#1 Updated by Perry Mason about 9 years ago

Don't know how related it is (with the work around), but in a multi wan setup with failover groups.
If wan fails apinger set it offline and online when it recover
if wan2 fails apinger set it offline and keeps it offline when it should recover.
I then kill apinger and start apinger and wan2 goes online.

#2 Updated by Ermal Luçi about 9 years ago

  • Status changed from New to Feedback

This seem to work ok with Chris workaround.

@Perry,

try latest snapshots it should be ok.

#3 Updated by Perry Mason about 9 years ago

No change for me on a day old snapshot. Had a longer fallout on wan2.
After the connection came back I could traceroute to the monitor ip but wan2 was still offline.

#4 Updated by Ermal Luçi about 9 years ago

  • % Done changed from 0 to 100

#5 Updated by Ermal Luçi about 9 years ago

#6 Updated by Ermal Luçi about 9 years ago

#7 Updated by Ermal Luçi about 9 years ago

Perry,

try latest snapshots i have identified the issue should work correctly now.

#8 Updated by Perry Mason almost 9 years ago

On a jun 9 snapshot the issue still shows.

#9 Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Resolved

this particular issue is resolved

Also available in: Atom PDF