• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Fail2ban extension hangs

Paula1

New Pleskian
Hi there,
I just update to 12.0.18 Update #69

Suddenly Fail2ban extension hangs and uses a lot a ram when I try to see the banned ips.

I have the same symptoms explained in this article http://kb.odin.com/en/122407
I don't use any big jail. I use only proftp, sshd and recidive.
Although I'm pretty sure the solution that they provide does not applied to my situation, I tried it without any luck.

I tried the following as well:

-disabling all jails,
-restarting the server,
-uninstalling and reinstalling fail2ban (using add/remove components)

The problem persists even without any jail activated.

I will appreciate any help,
Thanks in advance.
 
I ran into the same problem. I have uninstalled Fail2Ban, excluded it from the EPEL repo and reinstalled Fail2Ban via the Plesk installer.

Everything is now working ok again :)
 
Thanks both of you for your help.
The problem is solved:

-uninstall fail2ban
-exclude fail2ban from EPEL repository
-reinstall fail2ban using plesk installer.

Just like Cris1 said it. (I appreciate Gbotica's helps as well)

Thanks!
 
Back
Top