Unable to access Fail2ban settings: Timeout of 10 seconds has been reached. Lock 'service.fail2ban' is already owned by another process with pid <unknown>

Created:

2016-11-16 12:54:04 UTC

Modified:

2017-08-08 13:10:11 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Unable to access Fail2ban settings: Timeout of 10 seconds has been reached. Lock 'service.fail2ban' is already owned by another process with pid <unknown>

Applicable to:

  • Plesk 12.5 for Linux
  • Plesk 12.0 for Linux

Symptoms

While accessing Tools & Settings > IP Address Banning (Fail2Ban), one of the following errors appear:

PLESK_ERROR: Internal error: f2bmng failed: ERROR:f2bmng:Timeout of 10 seconds has been reached. Lock 'service.fail2ban' is already owned by another process with pid <unknown>

PLESK_ERROR: 502 Bad Gateway

PLESK_ERROR: Unable to remove subscription. The following error occurs in panel.log:

PLESK_ERROR: Internal error: f2bmng failed: ERROR:f2bmng:Timeout of 10 seconds has been reached. Lock 'service.fail2ban' is already owned by another process with pid <unknown>

PLESK_ERROR: ERROR findFailure failed to parse timeText

Cause

Incorrect/Incomplete installation of Fail2ban packages. When Plesk tries to get the service status for fail2ban, the process hangs and returns a timeout error.

Resolution

  1. Stop Fail2Ban service in Tools & Settings > Services Management
  2. Connect to the server using SSH.
  3. Delete all Fail2Ban logs:

    # rm -f /var/log/fail2ban*

  4. Reinstall Fail2Ban using Plesk Installer.

Additional Information

How to install Plesk additional components

Have more questions? Submit a request
Please sign in to leave a comment.