Hi, I’m worried because fail2ban looks like down for days.
Any suggestion how to fix this?
root@ynh:/home/admin# yunohost service start fail2ban --debug --verbose
117 DEBUG loading actions map namespace ‘yunohost’
128 DEBUG extra parameter classes loaded: [‘ask’, ‘password’, ‘required’, ‘pattern’]
128 DEBUG initializing base actions map parser for cli
131 DEBUG registering new callback action ‘yunohost.utils.packages.ynh_packages_version’ to [‘-v’, ‘–version’]
236 DEBUG lock has been acquired
242 INFO processing action [28373.1]: yunohost.service.start with args={‘names’: [‘fail2ban’]}
300665 WARNING Impossible d’exécuter la commande « service fail2ban start »
300797 DEBUG action [28373.1] ended after 300.555s
300798 DEBUG lock has been released
300799 ERROR Impossible de démarrer le service « fail2ban »
and I tried to regen configuraiton:
root@ynh:/home/admin# yunohost service regen-conf fail2ban --force --verbose --debug
114 DEBUG loading actions map namespace ‘yunohost’
125 DEBUG extra parameter classes loaded: [‘ask’, ‘password’, ‘required’, ‘pattern’]
125 DEBUG initializing base actions map parser for cli
127 DEBUG registering new callback action ‘yunohost.utils.packages.ynh_packages_version’ to [‘-v’, ‘–version’]
230 DEBUG lock has been acquired
236 INFO processing action [28829.1]: yunohost.service.regen-conf with args={‘force’: True, ‘dry_run’: False, ‘with_diff’: False, ‘names’: [‘fail2ban’], ‘list_pending’: False}
237 DEBUG custom hook folder not found for action ‘conf_regen’ in /etc/yunohost/hooks.d/
307 INFO Exécution de la commande « sudo -n -u admin -H sh -c BASH_XTRACEFD=7 /bin/bash -x “./52-fail2ban” pre 1 0 /home/yunohost.conf/pending/fail2ban 7>&1 »…
344 INFO + set -e
346 INFO + FORCE=1
346 INFO + DRY_RUN=0
346 INFO + case “$1” in
347 INFO + do_pre_regen /home/yunohost.conf/pending/fail2ban
348 INFO + pending_dir=/home/yunohost.conf/pending/fail2ban
348 INFO + cd /usr/share/yunohost/templates/fail2ban
349 INFO + fail2ban_dir=/home/yunohost.conf/pending/fail2ban/etc/fail2ban
350 INFO + mkdir -p /home/yunohost.conf/pending/fail2ban/etc/fail2ban/filter.d
350 INFO + cp yunohost.conf /home/yunohost.conf/pending/fail2ban/etc/fail2ban/filter.d/yunohost.conf
353 INFO + cp jail.conf /home/yunohost.conf/pending/fail2ban/etc/fail2ban/jail.conf
357 INFO + exit 0
429 INFO Application des configurations en attentes pour le service « fail2ban »…
534 DEBUG processing pending conf ‘/home/yunohost.conf/pending/fail2ban/etc/fail2ban/filter.d/yunohost.conf’ to system conf ‘/etc/fail2ban/filter.d/yunohost.conf’
535 DEBUG > system conf is already up-to-date
535 DEBUG processing pending conf ‘/home/yunohost.conf/pending/fail2ban/etc/fail2ban/jail.conf’ to system conf ‘/etc/fail2ban/jail.conf’
536 DEBUG > system conf is already up-to-date
537 INFO La configuration du service « fail2ban » est déjà à jour
538 DEBUG custom hook folder not found for action ‘conf_regen’ in /etc/yunohost/hooks.d/
538 INFO Exécution de la commande « sudo -n -u admin -H sh -c BASH_XTRACEFD=7 /bin/bash -x “./52-fail2ban” post 1 0 ‘’ 7>&1 »…
577 INFO + set -e
578 INFO + FORCE=1
579 INFO + DRY_RUN=0
579 INFO + case “$1” in
580 INFO + do_post_regen
580 INFO + regen_conf_files=
581 INFO + [[ -z ‘’ ]]
581 INFO + exit 0
658 DEBUG action [28829.1] ended after 0.421s
659 DEBUG lock has been released