Actions
Bug #448
closed
Netfilter lock problems
Status:
Rejected
Priority:
High
Assignee:
-
Category:
System :: Network
Start date:
2015-03-21
Due date:
% Done:
0%
Estimated time:
Patch Available:
Confirmed:
No
Branch:
Entity:
DuckCorp
Security:
Yes
Help Needed:
Description
This is probably due to concurrency. I guess fail2ban and firewalling should be started in the proper order and not at the same time. This problem affects all machines except Korutopi.
Here is the log:
Mar 21 00:35:35 Daneel fail2ban[910]: Starting authentication failure monitor: fail2ban. Mar 21 00:35:35 Daneel firewalling[902]: Starting firewall ...Another app is currently holding the xtables lock. Perhap s you want to use the -w option? Mar 21 00:35:35 Daneel firewalling[902]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? Mar 21 00:35:35 Daneel firewalling[902]: Another app is currently holding the xtables lock. Perhaps you want to use the -w option? Mar 21 00:35:43 Daneel firewalling[902]: .
Updated by Marc Dequènes almost 9 years ago
- Related to Enhancement #458: Experiment with nftables added
Updated by Marc Dequènes over 6 years ago
- Status changed from New to Rejected
We do not have this problem anymore.
Actions