On Fri, Oct 14, 2022 at 9:55 AM Charlie Dennett <cdennett@xxxxxxxxx> wrote:
On Mon, Oct 3, 2022 at 2:57 PM Richard Shaw <hobbes1069@xxxxxxxxx> wrote:I have disabled auto-stable based on time for the updates: I have submitted updates for f36 and up and EPEL 9.I would like some sort of confirmation on the update itself or by direct communication that everything appears to be working properly.Fail2ban is somewhat fragile by nature and this is a big update.Updated yesterday (10/13/22) to the latest 1.0.1 release on my F36 system. Upon startup, fail2ban-server was using 100% of a cpu. Tried removing the sqlite database and restarting (also restarted iptables after stopping fail2ban to remove all the blocks) but that did not help. Downgraded back to 0.11.2 and the problem went away.I will attempt to reinstall 1.0.1 and increase its verbosity to see if I can discover anything. It's just my home system. Use it as my desktop and I also have an apache web server running on it for my genealogy research.
Sigh. I stopped fail2ban (the 0.11 version), restarted iptables to flush it out, upgraded fail2ban to 1.0.1 and started it. No issues. It started up, rebanned what was in the database and settled right down. Seems to be working fine now.
-- Charlie
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
