==================================================================
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 #14 from Dan Brown <[email protected]> ---
I just ran across this bug as I was about to report this (or something very
similar) myself. My forum thread from six months ago is at
http://forums.contribs.org/index.php?topic=51222.0. I've installed the updated
RPM from the fws repo:
[dan@e-smith ~]$ rpm -q smeserver-fail2ban
smeserver-fail2ban-0.1.10-1.el6.fws.noarch
On reboot (after signal-event post-upgrade), fail2ban failed to start with the
attached error screen, but when I logged in as root and did 'service fail2ban
start', it started without errors. Will monitor and report.
--
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/
