• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved fail2ban cannot be started

TorbHo

Regular Pleskian
After migration of a lot of domains from backup, fail2ban cannot be started.

Plesk Onyx
17.5.3 Update #13
‪Ubuntu 16.04.2 LTS‬

Error message:

Fehler: Die Einstellungen können nicht gespeichert werden: f2bmng failed: Synchronizing state of fail2ban.service with SysV init with /lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install enable fail2ban
Job for fail2ban.service failed because the control process exited with error code. See "systemctl status fail2ban.service" and "journalctl -xe" for details.
ERROR:f2bmng:Failed to start fail2ban service.

systemctl status fail2ban.service shows:

● fail2ban.service - Fail2Ban Service

Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)

Active: inactive (dead) (Result: exit-code) since Do 2017-07-13 10:44:45 CEST; 4min 50s ago

Docs: man:fail2ban(1)

Process: 2090 ExecStart=/usr/bin/fail2ban-client -x start (code=exited, status=255)

Process: 2087 ExecStartPre=/bin/mkdir -p -m 755 /var/run/fail2ban (code=exited, status=0/SUCCESS)
 
Now it works.

I uninstalled the fail2ban extension AND removed the /etc/fail2ban directory via ssh.
After that, I reinstalled the extension via:

# /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component fail2ban​
 
Back
Top