Echec d'installation Shaarli: problème “fail2ban”

Bonjour à tou⋅te⋅s

Tentative infructueuse d’installation de Shaarli, voic je que j’ai comme indications

Mon serveur YunoHost

Matériel: VPS + debian 9
Version de YunoHost: 3.5.2.2 (stable)
J’ai accès à mon serveur : En SSH / Web
Êtes-vous dans un contexte particulier ou avez-vous effectué des modificiations particulières sur votre instance ? : non

Description du problème

Interruption du processus d’installation.

Info: Installing application shaarli…
Info: Validating installation parameters...
Info: Storing installation settings...
Info: Installing dependencies...
Info: Setting up source files...
Info: Configuring nginx web server...
Info: Reload the service nginx
Info: Configuring system user...
Info: Configuring php-fpm...
Info: Reload the service php7.0-fpm
Info: Set permissions...
Info: Set rights...
Info: Configuring log rotation...
Info: Add Fail2Ban configuration...
Warning: Job for fail2ban.service failed because the control process exited with error code.
Warning: See "systemctl status fail2ban.service" and "journalctl -xe" for details.
Warning: !!
Warning:   shaarli's script has encountered an error. Its execution was cancelled.
Warning: !!
Warning: 
Info: The operation 'Install 'shaarli' application' has failed! To get help, please share the full log of this operation using the command 'yunohost log display 20190508-215951-app_install-shaarli --share'
Info: Loading installation settings...
Info: Removing dependencies
Info: Removing app main directory
Info: Removing nginx web server configuration
Info: Reload the service nginx
Info: Removing php-fpm configuration
Info: Reload the service php7.0-fpm
Info: Removing logrotate configuration
Info: Removing Fail2Ban configuration
Warning: Remove the user shaarli
Info: Removing the dedicated system user
Success! The SSOwat configuration has been generated
Error: The operation 'Install 'shaarli' application' has failed! To get help, please share the full log of this operation using the command 'yunohost log display 20190508-215951-app_install-shaarli --share'

Commande systemctl status fail2ban.service

    ● fail2ban.service - Fail2Ban Service
       Loaded: loaded (/lib/systemd/system/fail2ban.service; enabled; vendor preset: enabled)
       Active: active (running) (Result: exit-code) since Tue 2019-05-07 17:01:34 CEST; 1 day 7h ago
         Docs: man:fail2ban(1)
      Process: 5905 ExecReload=/usr/bin/fail2ban-client reload (code=exited, status=0/SUCCESS)
     Main PID: 13458 (fail2ban-server)
        Tasks: 23 (limit: 4915)
       CGroup: /system.slice/fail2ban.service
               └─13458 /usr/bin/python3 /usr/bin/fail2ban-server -s /var/run/fail2ban/fail2ban.sock -p /var/run/fail2ban/fail2ban.pid -x -b

Commande journalctl -xe

May 09 00:09:01 temporaires.net CRON[6133]: (root) CMD (  [ -x /usr/lib/php/sessionclean ] && if [ ! -d /run/systemd/system ]; then /us
May 09 00:09:01 temporaires.net CRON[6132]: pam_unix(cron:session): session closed for user root
May 09 00:09:08 temporaires.net systemd[1]: Starting Clean php session files...
-- Subject: Unit phpsessionclean.service has begun start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit phpsessionclean.service has begun starting up.
May 09 00:09:08 temporaires.net systemd[1]: Started Clean php session files.
-- Subject: Unit phpsessionclean.service has finished start-up
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit phpsessionclean.service has finished starting up.
-- 
-- The start-up result is done.
May 09 00:09:27 temporaires.net sshd[6197]: Connection from 58.242.83.36 port *** on 95.216.195.29 port ****
May 09 00:09:27 temporaires.net sshd[6197]: Unable to negotiate with 58.242.83.36 port***: no matching key exchange method found. Th
May 09 00:10:21 temporaires.net sshd[6203]: Connection from 58.242.83.36 port *** on 95.216.195.29 port ****
May 09 00:10:21 temporaires.net sshd[6203]: Unable to negotiate with 58.242.83.36 port ***: no matching key exchange method found. Th
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (cn) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_equality_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net slapd[12587]: <= mdb_substring_candidates: (sudoUser) not indexed
May 09 00:10:42 temporaires.net sudo[6206]:     aris : TTY=pts/0 ; PWD=/home/****** ; USER=root ; 

Salut,

Il y a déjà un fil sur ce sujet, ici.
@Lapineige y propose une solution de contournement (installation de Shaarli sans support de fail2ban)

1 Like

Merci ! J’avais mal dû formulé ma recherche et je n’étais pas tombé dessus… Je vais regarder.