==================================================================
Please DO NOT REPLY to this mail or send email to the developers
about this bug. Please follow-up to Bugzilla using this link:
http://bugs.contribs.org/show_bug.cgi?id=8708
Have you checked the Frequently Asked Questions (FAQ)?
http://wiki.contribs.org/SME_Server:Documentation:FAQ
Please also take the time to read the following useful guide:
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
==================================================================
--- Comment #8 from Unnilennium <[email protected]> ---
gamin loging was not efficient as it did not detect new log lines, neither
pooling.
still the same problem, fail2ban stop after logrotate :
2014-12-22 01:12:27,493 fail2ban.actions: WARNING [recidive] Unban 87.244.159.5
2014-12-22 01:12:28,071 fail2ban.jail : INFO Jail 'recidive' stopped
2014-12-22 01:12:29,434 fail2ban.server : INFO Changed logging target to
/var/log/fail2ban/daemon.log for Fail2ban v0.8.10
2014-12-22 01:12:29,434 fail2ban.jail : INFO Creating new jail
'http-overflows'
2014-12-22 01:12:29,434 fail2ban.jail : INFO Jail 'http-overflows' uses
poller
2014-12-22 01:12:29,467 fail2ban.jail : INFO Initiated 'polling' backend
2014-12-22 01:12:29,468 fail2ban.comm : WARNING Command ['set',
'http-overflows', 'addlogpath', '/var/log/httpd/error_log'] has failed.
Received <exceptions.IOError instance at 0x865532c>
maybe fail2ban should be stopped BEFORE log rotate and started after.
--
You are receiving this mail because:
You are the QA Contact for the bug._______________________________________________
Mail for each SME Contribs bug report
To unsubscribe, e-mail [email protected]
Searchable archive at http://lists.contribs.org/mailman/public/contribteam/
