Echec installation WordPress Yunohost sur Raspberry Pi 3

fdrubigny1 · April 17, 2020, 2:20pm

Bonjour,
j’ai YunoHost 3.7.1.1 installé sur un Raspberry Pi 3.
j’ai plusieurs domaines dessus don 3 sites WordPress.

J’ai essayé d’installé un autre site WordPress sur un autre domaine mais à chaque fois l’installation échoue…
Je vous joins le fichier de log =>

2020-04-17 12:58:39,555: DEBUG - + ynh_handle_getopts_args --service_name=fail2ban --action=reload
2020-04-17 12:58:39,557: DEBUG - + set +x
2020-04-17 12:58:39,558: DEBUG - + local service_name=fail2ban
2020-04-17 12:58:39,559: DEBUG - + local action=reload
2020-04-17 12:58:39,559: DEBUG - + local log_path=/var/log/fail2ban/fail2ban.log
2020-04-17 12:58:39,560: DEBUG - + local length=20
2020-04-17 12:58:39,561: DEBUG - + local timeout=300
2020-04-17 12:58:39,562: DEBUG - + [[ -n '' ]]
2020-04-17 12:58:39,563: DEBUG - + '[' reload == reload ']'
2020-04-17 12:58:39,564: DEBUG - + action=reload-or-restart
2020-04-17 12:58:39,564: DEBUG - + systemctl reload-or-restart fail2ban
2020-04-17 12:58:40,568: DEBUG - + journalctl --no-pager --lines=20 -u fail2ban
2020-04-17 12:58:40,569: WARNING - Job for fail2ban.service failed because the control process exited with error code.
2020-04-17 12:58:40,570: DEBUG - + test -e /var/log/fail2ban/fail2ban.log
2020-04-17 12:58:40,571: WARNING - See "systemctl status fail2ban.service" and "journalctl -xe" for details.
2020-04-17 12:58:40,572: DEBUG - + false
2020-04-17 12:58:40,572: WARNING - -- Logs begin at Thu 2020-04-16 22:17:01 UTC, end at Fri 2020-04-17 12:58:40 UTC. --
2020-04-17 12:58:40,573: DEBUG - + ynh_exit_properly
2020-04-17 12:58:40,574: WARNING - Apr 17 10:07:29 xxxnohost.me systemd[1]: Reloading Fail2Ban Service.
2020-04-17 12:58:40,575: DEBUG - + local exit_code=1
2020-04-17 12:58:40,575: WARNING - Apr 17 10:07:30 xxxnohost.me fail2ban-client[27093]: ERROR  No file(s) found for glob /var/www/rainloop/app/data/_data_/_default_/logs/fail2ban/auth-fail.log
2020-04-17 12:58:40,576: DEBUG - + '[' 1 -eq 0 ']'
2020-04-17 12:58:40,577: WARNING - Apr 17 10:07:30 xxxnohost.me fail2ban-client[27093]: ERROR  Failed during configuration: Have not found any log file for rainloop jail
2020-04-17 12:58:40,578: DEBUG - + trap '' EXIT
2020-04-17 12:58:40,579: WARNING - Apr 17 10:07:30 xxxnohost.me systemd[1]: fail2ban.service: Control process exited, code=exited status=255
2020-04-17 12:58:40,580: DEBUG - + set +eu
2020-04-17 12:58:40,581: WARNING - Apr 17 10:07:30 xxxnohost.me systemd[1]: Reload failed for Fail2Ban Service.
2020-04-17 12:58:40,582: DEBUG - + sleep 0.5
2020-04-17 12:58:40,582: WARNING - Apr 17 12:08:55 xxxnohost.me systemd[1]: Reloading Fail2Ban Service.
2020-04-17 12:58:40,583: WARNING - Apr 17 12:08:56 xxxnohost.me fail2ban-client[9402]: ERROR  No file(s) found for glob /var/www/rainloop/app/data/_data_/_default_/logs/fail2ban/auth-fail.log
2020-04-17 12:58:40,584: WARNING - Apr 17 12:08:56 xxxnohost.me fail2ban-client[9402]: ERROR  Failed during configuration: Have not found any log file for rainloop jail
2020-04-17 12:58:40,585: WARNING - Apr 17 12:08:56 xxxnohost.me systemd[1]: fail2ban.service: Control process exited, code=exited status=255
2020-04-17 12:58:40,586: WARNING - Apr 17 12:08:56 xxxnohost.me systemd[1]: Reload failed for Fail2Ban Service.
2020-04-17 12:58:40,587: WARNING - Apr 17 12:09:10 xxxnohost.me systemd[1]: Reloading Fail2Ban Service.
2020-04-17 12:58:40,588: WARNING - Apr 17 12:09:10 xxxnohost.me fail2ban-client[9787]: ERROR  No file(s) found for glob /var/www/rainloop/app/data/_data_/_default_/logs/fail2ban/auth-fail.log
2020-04-17 12:58:40,589: WARNING - Apr 17 12:09:10 xxxnohost.me fail2ban-client[9787]: ERROR  Failed during configuration: Have not found any log file for rainloop jail
2020-04-17 12:58:40,590: WARNING - Apr 17 12:09:11 xxxnohost.me systemd[1]: fail2ban.service: Control process exited, code=exited status=255
2020-04-17 12:58:40,591: WARNING - Apr 17 12:09:11 xxxnohost.me systemd[1]: Reload failed for Fail2Ban Service.
2020-04-17 12:58:40,592: WARNING - Apr 17 12:58:39 xxxnohost.me systemd[1]: Reloading Fail2Ban Service.
2020-04-17 12:58:40,593: WARNING - Apr 17 12:58:40 xxxnohost.me fail2ban-client[15796]: ERROR  No file(s) found for glob /var/www/rainloop/app/data/_data_/_default_/logs/fail2ban/auth-fail.log
2020-04-17 12:58:40,594: WARNING - Apr 17 12:58:40 xxxnohost.me fail2ban-client[15796]: ERROR  Failed during configuration: Have not found any log file for rainloop jail
2020-04-17 12:58:40,595: WARNING - Apr 17 12:58:40 xxxnohost.me systemd[1]: fail2ban.service: Control process exited, code=exited status=255
2020-04-17 12:58:40,596: WARNING - Apr 17 12:58:40 xxxnohost.me systemd[1]: Reload failed for Fail2Ban Service.
2020-04-17 12:58:41,100: DEBUG - + type -t ynh_clean_setup
2020-04-17 12:58:41,101: WARNING - /usr/share/yunohost/helpers.d/logging: line 11: args_array: readonly variable
2020-04-17 12:58:41,103: DEBUG - + ynh_die
2020-04-17 12:58:41,104: DEBUG - + local legacy_args=mc
2020-04-17 12:58:41,105: DEBUG - + args_array=([m]=message= [c]=ret_code=)
2020-04-17 12:58:41,233: ERROR - Could not install wordpress: An error occurred inside the app installation script
None

Par avance, merci pour votre aide.
Amicalement, Francis.

Maniack_Crudelis · April 17, 2020, 5:53pm

Is your rainloop instance up to date ?

If you have an upgrade for this app, it may fix your situation.
Otherwise, I don’t know why rainloop is broken, but you may fix that by creating this file

sudo touch /var/www/rainloop/app/data/_data_/_default_/logs/fail2ban/auth-fail.log
sudo chown rainloop -R /var/www/rainloop

After that, you should be able to install wordpress.

fdrubigny1 · April 17, 2020, 8:06pm

Hello @Maniack_Crudelis many thanks for your help.
I tried the first command but the answer is :
touch: cannot touch '/var/www/rainloop/app/data/_data_/_default_/logs/fail2ban/auth-fail.log': No such file or directory
So I’m going to try to upgrade via the web interface.
I’ll let you know if it worked.
Thank you so much.

fdrubigny1 · April 17, 2020, 8:29pm

Upgrade via the web interface don’t work and i’ve got an error :
ser
2020-04-17 20:23:36,940: DEBUG - 12423 + local password
2020-04-17 20:23:36,941: DEBUG - 12424 + local database
2020-04-17 20:23:36,942: DEBUG - 12425 + ynh_handle_getopts_args --user=root --password=********** --database=
2020-04-17 20:23:36,943: DEBUG - 12426 + set +x
2020-04-17 20:23:37,045: DEBUG - 12528 + database=
2020-04-17 20:23:37,046: DEBUG - 12529 + mysql -u root --password=********** -B ‘’
2020-04-17 20:23:37,047: DEBUG - 12531 + ynh_mysql_connect_as rainloop ********** rainloop
2020-04-17 20:23:37,048: DEBUG - 12533 + local legacy_args=upd
2020-04-17 20:23:37,049: DEBUG - 12534 + args_array=([u]=user= [p]=password= [d]=database=)
2020-04-17 20:23:37,050: DEBUG - 12536 + declare -Ar args_array
2020-04-17 20:23:37,051: DEBUG - 12537 + local user
2020-04-17 20:23:37,052: DEBUG - 12539 + local password
2020-04-17 20:23:37,053: DEBUG - 12540 + local database
2020-04-17 20:23:37,054: DEBUG - 12541 + ynh_handle_getopts_args rainloop ********** rainloop
2020-04-17 20:23:37,055: DEBUG - 12542 + set +x
2020-04-17 20:23:37,056: DEBUG - 12544 + echo ‘! Helper used in legacy mode !’
2020-04-17 20:23:37,057: DEBUG - 12545 + set +x
2020-04-17 20:23:37,058: DEBUG - 12546 + database=rainloop
2020-04-17 20:23:37,059: DEBUG - 12548 + mysql -u rainloop --password=********** -B rainloop
2020-04-17 20:23:37,060: DEBUG - 12549 + sudo mkdir -p /var/www/rainloop/logs /var/www/rainloop/temp
2020-04-17 20:23:37,161: DEBUG - 12651 + sudo chown -R www-data: /var/www/rainloop
2020-04-17 20:23:37,364: DEBUG - 12853 + sudo cp -a ./nginx.conf /etc/nginx/conf.d/xxx.nohost.me.d/rainloop.conf
2020-04-17 20:23:37,365: DEBUG - 12855 + sudo cp -a ./php-fpm.conf /etc/php/7.0/fpm/pool.d/rainloop.conf
2020-04-17 20:23:37,467: DEBUG - 12956 + sudo service php7.0-fpm reload
2020-04-17 20:23:37,669: DEBUG - 13165 + sudo service nginx reload
2020-04-17 20:23:38,273: DEBUG - 13712 Pour voir le journal de cette opération ‘Restaurer ‘rainloop’ depuis une sauvegarde’, utilisez la commande ‘yunohost log display 20200417-202331-backup_restore_app-rainloop’
2020-04-17 20:23:38,275: DEBUG - 13752 The permission database has been resynchronized
2020-04-17 20:23:39,481: DEBUG - 14918 La configuration de SSOwat générée
2020-04-17 20:23:39,883: DEBUG - 15389 Restauré
2020-04-17 20:23:39,885: DEBUG - 15389 action [2431.1] executed in 14.112s
2020-04-17 20:23:39,886: DEBUG - apps:
2020-04-17 20:23:39,887: DEBUG - rainloop: Success
2020-04-17 20:23:39,888: DEBUG - system:
2020-04-17 20:23:39,989: DEBUG - + ynh_die ‘–message=The app was restored to the way it was before the failed upgrade.’
2020-04-17 20:23:39,991: DEBUG - + local legacy_args=mc
2020-04-17 20:23:39,992: DEBUG - + args_array=([m]=message= [c]=ret_code=)
2020-04-17 20:23:39,994: DEBUG - + declare -Ar args_array
2020-04-17 20:23:39,995: DEBUG - + local message
2020-04-17 20:23:39,996: WARNING - The app was restored to the way it was before the failed upgrade.
2020-04-17 20:23:39,998: DEBUG - + local ret_code
2020-04-17 20:23:40,000: DEBUG - + ynh_handle_getopts_args ‘–message=The app was restored to the way it was before the failed upgrade.’
2020-04-17 20:23:40,001: DEBUG - + set +x
2020-04-17 20:23:40,002: DEBUG - + echo ‘The app was restored to the way it was before the failed upgrade.’
2020-04-17 20:23:40,004: DEBUG - + exit 1
2020-04-17 20:23:40,127: ERROR - Impossible de mettre à jour rainloop : Une erreur s’est produite durant l’exécution du script de mise à niveau de l’application
Traceback (most recent call last):
File “/usr/lib/python2.7/dist-packages/moulinette/interfaces/api.py”, line 301, in wrapper
curr_v = params[k]
KeyError: ‘app’

fdrubigny1 · April 17, 2020, 8:46pm

Upgrade rainloop is ok, i trie to install WordPress

Aleks · April 17, 2020, 8:54pm

The log you pasted is only the automatic restore of the app after the failed operation … You gotta share the full log (possibly you should have a “Share with Yunopaste” button on the interface

fdrubigny1 · April 17, 2020, 9:12pm

Ok, i don’t know…
The upgrade of rainloop via web interface is now Ok, but installation of WordPress failed.
This is the entire log => https://paste.yunohost.org/raw/odafilines

Many thanks for your help.
Francis

Aleks · April 17, 2020, 9:18pm

I’m totally randomly jumping in, but it looks like the actual error is … :

2020-04-17 21:04:26,742: WARNING - avril 17 16:17:15 maindomain.tld fail2ban-client[642]: 2020-04-17 16:17:15,492 fail2ban.server         [1105]: INFO    Starting in daemon mode
2020-04-17 21:04:26,748: WARNING - avril 17 16:17:16 maindomain.tld systemd[1]: fail2ban.service: Unit cannot be reloaded because it is inactive.

I don’t understand exactly … looks like for some reason fail2ban wasnt started and it didn’t want to reload because the service was “inactive” … but it started it just a few microseconds before … Maybe systemd was still seeing the service as inactive if it wasnt fully started …

fdrubigny1 · April 17, 2020, 9:32pm

Ok, it’s very difficult, i don’t understand the logs…
i don’t know how to fix this error.
i’m going to search, many thanks for your help.

Maniack_Crudelis · April 17, 2020, 9:52pm

What is especially strange is that:

github.com

YunoHost/yunohost/blob/stretch-unstable/data/helpers.d/fail2ban#L133


[Definition]
failregex = $failregex
ignoreregex =
EOF
  fi


  # Common to usage 1 and 2.
  ynh_store_file_checksum "$finalfail2banjailconf"
  ynh_store_file_checksum "$finalfail2banfilterconf"


  ynh_systemd_action --service_name=fail2ban --action=reload


  local fail2ban_error="$(journalctl -u fail2ban | tail -n50 | grep "WARNING.*$app.*")"
  if [[ -n "$fail2ban_error" ]]; then
    ynh_print_err --message="Fail2ban failed to load the jail for $app"
    ynh_print_warn --message="${fail2ban_error#*WARNING}"
  fi
}


# Remove the dedicated fail2ban config (jail and filter conf files)
#

github.com

YunoHost/yunohost/blob/stretch-unstable/data/helpers.d/systemd#L121


    else
        # Read the specified log file
        tail -F -n0 "$log_path" > "$templog" 2>&1 &
        # Get the PID of the tail command
        local pid_tail=$!
    fi
fi


# Use reload-or-restart instead of reload. So it wouldn't fail if the service isn't running.
if [ "$action" == "reload" ]; then
    action="reload-or-restart"
fi


systemctl $action $service_name \
    || ( journalctl --no-pager --lines=$length -u $service_name >&2 \
    ; test -e "$log_path" && echo "--" >&2 && tail --lines=$length "$log_path" >&2 \
    ; false )


# Start the timeout and try to find line_match
if [[ -n "${line_match:-}" ]]
then

Haven’t read the log yet though, but fail2ban shouldn’t failed to reload in such case.

fdrubigny1 · April 17, 2020, 10:01pm

Unfortunately I don’t understand all these lines of code …
In the web interface fail2ban is marked as active and started, so basically there is no reason why it cannot restart and especially that it is inactive for a few miliseconds? This is the first time I have encountered a problem installing Wordpress on YunoHost, so I am a bit lost.

Many thanks for your help.
Francis

Maniack_Crudelis · April 17, 2020, 10:12pm

Just tried it, with the service stopped, reload-or-restart does work.
Even with the service disabled, it does restart…

I can’t reproduce, even doing it on purpose !

@fdrubigny1 If fail2ban is up, you can retry to install Wordpress.

EDIT: Could you also run this

yunopaste < $(sudo journalctl -u fail2ban)

To give us some intel about what happened with fail2ban ?

fdrubigny1 · April 17, 2020, 10:26pm

the answer is : -bash: $(sudo journalctl -u fail2ban): ambiguous redirect

fdrubigny1 · April 17, 2020, 10:28pm

I just tried the installation again but it still failed …
I made 2 screenshots during the installation because there are 2 “danger warning” messages.
I don’t speak English very well, I use translate to help me.
There is a message I understood that it concerns the new group authorization system, but I do not understand how to make these settings.
I provide a link to the installation log. https://paste.yunohost.org/raw/udonawelac

Maniack_Crudelis · April 17, 2020, 10:28pm

Sorry !

yunopaste <<< $(sudo journalctl -u fail2ban)

fdrubigny1 · April 17, 2020, 10:28pm

answer is : hastebin

Maniack_Crudelis · April 17, 2020, 10:43pm

If you’re still here
I would like the result of those commands please:

date
yunopaste <<< $(sudo journalctl -u fail2ban)

An install of wordpress
then again

yunopaste <<< $(sudo journalctl -u fail2ban)

Edit: And also

yunopaste <<< $(sudo tail -n100 /var/log/fail2ban.log)

Please

fdrubigny1 · April 17, 2020, 10:46pm

Date : Fri Apr 17 22:45:08 UTC 2020
yunopaste : hastebin

I launch installation of Wordpress

Many thanks for the time you spend on my problem.

Installation of Wordpress failed…
yunopaste <<< $(sudo journalctl -u fail2ban) answer is :
https://paste.yunohost.org/okeqinewoz

yunopaste <<< $(sudo tail -n100 /var/log/fail2ban.log) answer is :
https://paste.yunohost.org/yujikawehu

Sorry, I am editing my last post because I have reached the maximum reply allowed for my first post.

Oh you are not a bad boy who did not finish the model on his first post!
I don’t understand if this is a joke?

So I’m going to ask you, first, are you using your ssh connection? And secondly, have you changed the default port 22?

Yes I am using my ssh connection. I do not really remember for port 22 but it seems to me that yes I had changed it … it’s been a long time since I installed YunoHost on my Raspberry Pi 3 years at least I think … but it seems to me that yes otherwise ssh would not work, right?

Which reminds me how much fail2ban can take a very long time to reload all prohibited IP addresses on each reboot.
And here we already have a hundred lines of prohibited repeat offenders.

Indeed I also noticed all these banners! However, these are just simple personal blogs …

I will create a specific version of Wordpress that you will try, we will see if it works.

I will continue tomorrow because I can no longer respond and the Raspberry clock displays 2 hours less than the actual time here in France. In reality it is already 1:20 a.m. …

Once again thank you very much for this precious help!

You were supposed to have a template when you created this post, probably with the answers to my questions.

No there was no model? …

The installation seems blocked … in my console it is in the configuration of fail2ban but I have a lot of warning and there for several minutes nothing has happened, as if the work was frozen? …

I’m relaunching tomorrow, thank you very much for the help.

Hi! Despite my command console that blocked, a priori Wordpress is still installed until the end! Awesome! Thank you very much for your precious help!

Maniack_Crudelis · April 17, 2020, 11:06pm

Really !?
Fail2ban didn’t failed to reload this time !

Huh… well your fail2ban log… I think we found the problem !
Oh aren’t you a nasty boy who didn’t fill the template on his first post !
So I’m gonna ask you, first, do you use your ssh connection ? And second, did you change the default port 22 ?

Cause looks like your fail2ban is working hard kicking out many IP
I see INFO [sshd] Found 112.85.42.232, and soon after NOTICE [recidive] Ban 112.85.42.232

Which remind me by the way that fail2ban can take a very long time reloading all the IP it has banned at each restart.
And right here, we have already a hundred lines of banned recidivists.

I’m gonna make a specific version of Wordpress you’ll try, we’ll see if it works.

Maniack_Crudelis · April 17, 2020, 11:21pm

Ok let’s try to install from this branch:

sudo yunohost app install https://github.com/YunoHost-Apps/wordpress_ynh/tree/fucking_fail2start

If I’m not mistaking it should work, and you can keep that version installed.