run-parts: /etc/cron.weekly/fail2ban-vacuum exited with return code 5

[PixelOnline]

Username:

TITLE

run-parts: /etc/cron.weekly/fail2ban-vacuum exited with return code 5

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.61 Mise à jour 6

PROBLEM DESCRIPTION

Hello,

I have receive this mail but i don't see other topic on your forum

sujet : test -x /usr/sbin/anacron || (cd / && run-parts --report /etc/cron.weekly)
body mail : run-parts: /etc/cron.weekly/fail2ban-vacuum exited with return code 5

I can't find any equivalent subject and no information on this error code

info Plesk Obsidian 18.0.61 Mise à jour 6

STEPS TO REPRODUCE

Mail

ACTUAL RESULT

just mail

EXPECTED RESULT

none

ANY ADDITIONAL INFORMATION

systemctl status fail2ban
● 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: active (running) since Fri 2024-05-24 16:08:40 UTC; 1 months 13 days ago
       Docs: man:fail2ban(1)
   Main PID: 494195 (fail2ban-server)
      Tasks: 25 (limit: 38203)
     Memory: 63.6M
        CPU: 11h 16min 53.158s
     CGroup: /system.slice/fail2ban.service
             └─494195 /usr/bin/python2 /usr/bin/fail2ban-server -xf start

Warning: journal has been rotated since unit was started, output may be incomplete.

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Help with sorting out

 

[Kaspar@Plesk]

Most likely the fail2ban database was locked when the scheduled task (cron job) ran. You can wait another day, this issue will most likely resolve itself. Otherwise you can try to run the scheduled task manually: /etc/cron.weekly/fail2ban-vacuum

 

[PixelOnline]

Ok thanks