bugzilla-daemon at bugzilla.netfilter.org
2011-Oct-19 10:22 UTC
[Bug 758] New: Retry iptables command on transient failure
http://bugzilla.netfilter.org/show_bug.cgi?id=758 Summary: Retry iptables command on transient failure Product: iptables Version: unspecified Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P5 Component: iptables AssignedTo: netfilter-buglog at lists.netfilter.org ReportedBy: nils.rennebarth at funkwerk-ec.com Estimated Hours: 0.0 On our system, the command # iptables -t mangle -D <some chain> <some rule> or # iptables -t mangle -F <some chain> sometimes fails with exit code 4. Retrying the same command again works. This happens often enough that is is annoying. Couldn't iptables itself try a number of times and only exit if the condition persists instead of giving up immediately? The message when that happens suggests that it comes from the following fragment in iptables-standalone.c: if (errno == EAGAIN) { exit(RESOURCE_PROBLEM); } so I assume, that some system call returned EAGAIN. This may indicate a real error condition (deadlock situation), which is why I wouldn't retry indefinitely, but failing on a single try appears to be a common case. -- Configure bugmail: http://bugzilla.netfilter.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. You are watching all bug changes.
Possibly Parallel Threads
- [Bug 758] Retry iptables command on transient failure
- [Bug 748] New: Range check for ulog-cprange is wrong
- Confusion using "ssh-add -D" and then "ssh-add -l"
- [Bug 3082] New: Add support for deterministically derived keys
- [jamie@audible.transient.net: Bug#160155: gapless playback]