• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Issue Problems with fail2ban

alexmaw

New Pleskian
Server operating system version
Ubuntu 22.04
Plesk version and microupdate number
18.0.60_build1800240421.18
Hello, good morning. I hope someone can give me a hand. I currently have a problem with fail2ban.
At first everything was working fine but after modifying the fail2ban bad bot file How to Avoid High CPU Load & Block Bad Bots with Plesk

I got some errors like the ones mentioned here: Unable to create a subscription or open Jails in Fail2Ban: f2bmng failed: ERROR:f2bmng - Support Cases from Plesk Knowledge Base and decided to follow the steps to reinstall fail2ban.


When doing so I get the following errors:
On installation:
dpkg: error processing package plesk-fail2ban-configurator (--configure):
dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup error from a previous failure.
Processing triggers for man-db (2.10.2-1) ...
Errors were encountered while processing:
fail2ban
plesk-fail2ban-configurator
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Bootstrapper has finished action (exec time: 0 sec.): parent_name='PLESK_18_0_60', sequence='pkgs', stage='rollback', sequence_order='1', operation='install', exec_cmd='rm -f /tmp/pp-bootstrapper-mode.flag; rm -f /var/lock/parallels-panel-maintenance-mode.flag; touch /var/lock/parallels-panel-upgrade-failure.flag; :'', m_arch='', exit code: 0, output: ~empty
[2024-05-04 11:51:05.838149] Launching component and product checkers...
[2024-05-04 11:51:05.838222] FileFetcher: get file (~empty)/report-update
[2024-05-04 11:51:05.838304] Downloading file report-update: 0%
[2024-05-04 11:51:06.092172] Downloading file report-update: 100% was finished.
[2024-05-04 11:51:06.092450] FileFetcher: get file (~empty)/pool/PSA_18.0.60_14384/examiners/py_launcher.sh
[2024-05-04 11:51:06.092501] Downloading file pool/PSA_18.0.60_14384/examiners/py_launcher.sh: 0%
[2024-05-04 11:51:06.163098] Downloading file pool/PSA_18.0.60_14384/examiners/py_launcher.sh: 100% was finished.
[2024-05-04 11:51:06.730847] Examination executed ["/root/parallels/pool/PSA_18.0.60_14384/examiners/py_launcher.sh" "/root/parallels/report-update" --op update --rc 1 --start-flag /var/lock/plesk-report-update.flag --to=18.0.60.1 --from=18.0.60] with code 0
Output:
~empty
Error:
~empty
[2024-05-04 11:51:06.731325] Execute command /opt/psa/admin/bin/send-error-report install --version 18.0.60
[2024-05-04 11:51:06.732733] Warning: Failed to detach from parents cgroup, installer might be unexpectedly killed later by the system
[2024-05-04 11:51:06.737402] Error: An error occurred on attempt to install packages.
Attention! Your software might be inoperable.
Visit https://support.plesk.com/ to search for a solution.
In the system log:

Execution status has failed with exit code 3, stdout: × fail2ban.service - Fail2Ban Service
Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
Drop-In: /usr/lib/systemd/system/fail2ban.service.d
└─50-ensure-log.conf
Active: failed (Result: exit-code) since Sat 2024-05-04 11:52:11 CEST; 6min ago
Docs: man:fail2ban(1)
Process: 2069698 ExecStartPre=/bin/mkdir -p /run/fail2ban (code=exited, status=0/SUCCESS)
Process: 2069699 ExecStartPre=/bin/sh -c umask 077; touch /var/log/fail2ban.log (code=exited, status=0/SUCCESS)
Process: 2069701 ExecStart=/usr/bin/fail2ban-server -xf start (code=exited, status=255/EXCEPTION)
Main PID: 2069701 (code=exited, status=255/EXCEPTION)
CPU: 148ms

May 04 11:52:11 *** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 *** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 **** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 **** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 **** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 *** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 *** fail2ban-server[2069701]: 2024-05-04 11:52:11,167 fail2ban.configreader [2069701]: ERROR No section: 'Definition'
May 04 11:52:11 *** fail2ban-server[2069701]: Server ready
May 04 11:52:11 *** systemd[1]: fail2ban.service: Main process exited, code=exited, status=255/EXCEPTION
May 04 11:52:11 *** systemd[1]: fail2ban.service: Failed with result 'exit-code'.

I'm a bit lost and I don't know how to continue in the process of repairing fail2ban.
I hope someone can tell me how to recover the functionality.
Best regards.
 
I can't tell for sure based on the error you posted, but it might be related to bug PPPM-14406 (I could be wrong tho). Best suggestion I can give is to contact Plesk support for investigation of the issue on your server.

To sign-in to support please go to https://support.plesk.com

If you experience login issues, please see this KB article:
https://support.plesk.com/hc/en-us/...rt-plesk-com-and-password-reset-does-not-work

If you bought your license from a reseller, your reseller should provide support for you. If the reseller does not provide support, here is an alternative:
https://support.plesk.com/hc/en-us/articles/12388090147095-How-to-get-support-directly-from-Plesk
 
Back
Top