Reporter Michael Rhyner (mikerhyner) Created Oct 11, 2018 1:30:46 PM Updated Oct 11, 2018 1:30:46 PM Priority Normal Type Bug State Submitted Assignee Laurent Declercq (nuxwin) Subsystem No subsystem Affected versions 1.5.1 Milestone 1.6.0 Severity No severity
We have little issue with imscp-traffic-logger:
As we use fail2ban to block suspicious requests (using iptables), there's some conflict with each other from time to time as they generate some kind of race condition when many Ban/Unban action happening (the same time when imscp-traffic-logger is reloading). Then systemd reports "/imscp_traffic.service" as failed with this cause:
"perl: [ERROR] main::start: Another app is currently holding the xtables lock. Perhaps you want to use the -w option?"
So perhaps we should add the proposed iptables option '-w' (wait for xtables lock) within /var/www/imscp/engine/tools/imscp-net-traffic-logger...
You'll find my proposed patch attached...