• 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.

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