Yunohost Upgrade to Buster 4.0 failure

Hi Aleks,

What can I do to get the 403 forbidden nginx error fixed. Some other forum topics have not been helpful.

Aleks,

What do you make of this?

tail -20 /var/log/nginx/error.log
2020/08/30 02:51:50 [error] 5926#5926: *70 directory index of “/usr/share/yunohost/admin/” is forbidden, client: 193.118.53.210, server: , request: “GET /yunohost/admin/ HTTP/1.1”, host: “97.91.135.28”, referrer: “https://97.91.135.28/yunohost/admin
2020/08/30 09:52:04 [error] 5926#5926: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, certificate: “/etc/yunohost/certs/shinevar.nohost.me/crt.pem”
2020/08/30 10:31:23 [error] 5926#5926: *110 directory index of “/usr/share/yunohost/admin/” is forbidden, client: 193.118.53.210, server: , request: “GET /yunohost/admin/ HTTP/1.1”, host: “97.91.135.28”, referrer: “https://97.91.135.28/yunohost/admin
2020/08/30 10:53:15 [error] 5926#5926: *115 directory index of “/usr/share/yunohost/admin/” is forbidden, client: 192.35.168.203, server: , request: “GET /yunohost/admin/ HTTP/1.1”, host: “97.91.135.28”
2020/08/30 12:10:45 [error] 5926#5926: *126 directory index of “/usr/share/yunohost/admin/” is forbidden, client: 128.14.209.178, server: , request: “GET /yunohost/admin/ HTTP/1.1”, host: “97.91.135.28”, referrer: “https://97.91.135.28/yunohost/admin
2020/08/30 12:25:42 [error] 5926#5926: *127 directory index of “/usr/share/yunohost/admin/” is forbidden, client: 213.6.61.219, server: , request: “GET /yunohost/admin/ HTTP/1.1”, host: “97.91.135.28”
2020/08/30 13:32:45 [error] 5926#5926: ocsp.int-x3.letsencrypt.org could not be resolved (110: Operation timed out) while requesting certificate status, responder: ocsp.int-x3.letsencrypt.org, certificate: “/etc/yunohost/certs/shinevar.nohost.me/crt.pem”

hmpf i guess yes that’s not expected … Let’s look at ls -l /usr/share/yunohost/admin

Btw let’s also run a dpkg --audit

and dpkg --verify yunohost yunohost-admin

Hello Aleks,

Happy Monday. Here is the output of those commands:

ls -l /usr/share/yunohost/admin
total 0
lrwxrwxrwx 1 root root 34 Oct 22 2019 ca.crt -> /etc/ssl/certs/ca-yunohost_crt.pem

dpkg --audit
The following packages are only half configured, probably due to problems
configuring them the first time. The configuration should be retried using
dpkg --configure or the configure menu option in dselect:
nginx-extras nginx web/proxy server (extended version)

dpkg --verify yunohost yunohost-admin
dpkg: package ‘yunohost-admin’ is not installed

Apparently nginx is not fully installed and yunohost-admin is not?

What the hell -_- …

Well then idk let’s try to apt install yunohost-admin ?

Alright Aleks,

PTL! Good news! The install worked. Logged into Yunohost Admin, ran system updates, upgraded RoundCube. Everything looks good. Here is the output from the install. Some errors noted, but overall it looks good.

apt install yunohost-admin
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following packages were automatically installed and are no longer required:
g+±6 guile-2.0-libs libbind9-140 libdns162 libevent-2.0-5 libhiredis0.13 libisc160 libisccc140 libisccfg140
libjemalloc1 liblwres141 libmariadbclient18 libperl5.24 libstdc+±6-dev libunbound2 python-apt
Use ‘apt autoremove’ to remove them.
The following additional packages will be installed:
unscd yunohost
Suggested packages:
htop acpi-support-base udisks2
The following NEW packages will be installed:
unscd yunohost yunohost-admin
0 upgraded, 3 newly installed, 0 to remove and 20 not upgraded.
1 not fully installed or removed.
Need to get 0 B/8,713 kB of archives.
After this operation, 21.1 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up nginx-extras (1.14.2-2+deb10u3) …
[ ok ] Upgrading binary: nginx.
Selecting previously unselected package unscd.
(Reading database … 56632 files and directories currently installed.)
Preparing to unpack …/unscd_0.53-1+b1_amd64.deb …
Unpacking unscd (0.53-1+b1) …
Setting up unscd (0.53-1+b1) …
Selecting previously unselected package yunohost.
(Reading database … 56641 files and directories currently installed.)
Preparing to unpack …/yunohost_4.0.4_all.deb …
Unpacking yunohost (4.0.4) …
Setting up yunohost (4.0.4) …
Regenerating configuration, this might take a while…
Success! Configuration updated for ‘dnsmasq’
Warning: The configuration file ‘/etc/fail2ban/jail.conf’ has been manually modified and will not be updated…]
Warning: The configuration file ‘/etc/mysql/my.cnf’ has been manually modified and will not be updated
Warning: The configuration file ‘/etc/avahi/avahi-daemon.conf’ has been manually modified and will not be updated
Warning: The configuration file ‘/etc/ldap/schema/mailserver.schema’ has been manually modified and will not be updated
Warning: The configuration file ‘/etc/ldap/schema/sudo.schema’ has been manually modified and will not be updated
Warning: The configuration file ‘/etc/ssh/sshd_config’ has been manually modified and will not be updated
Launching migrations…
Info: No migrations to run
Re-diagnosing server health…
Error: Found 1 significant issue(s) related to Base system!
Warning: Found 1 item(s) that could be improved for Internet connectivity.
Success! Everything looks good for DNS records!
Error: Found 4 significant issue(s) related to Ports exposure!
Success! Everything looks good for Web!

Error: Found 4 significant issue(s) (and 1 warning(s)) related to Email!#…]
Error: Failed to get status information via dbus for service php7.3-fpm, systemctl didn’t recognize this service (‘NoSuchUnit’).
Error: Found 2 significant issue(s) (and 1 warning(s)) related to Services status check!
Success! Everything looks good for System resources!
Warning: Found 4 item(s) that could be improved for System configurations.
Warning: To see the issues found, you can go to the Diagnosis section of the webadmin, or run ‘yunohost diagnosis show --issues’ from the command-line.
Selecting previously unselected package yunohost-admin.########################…]
(Reading database … 56899 files and directories currently installed.)
Preparing to unpack …/yunohost-admin_4.0.3_all.deb …
Unpacking yunohost-admin (4.0.3) …##################################################…]
Setting up yunohost-admin (4.0.3) …#######################################################…]
Processing triggers for systemd (241-7~deb10u4) …#####################################################…]
Processing triggers for man-db (2.8.5-2) …

Aleks,

Hold on! When I try to open up my applications I get a 502 Bad Gateway nginx error.

apt install php7.3-fpm php7.3 --reinstall

Nice artwork Aleks!

Hey Aleks,

Did the php reinstall. Still getting the 502 bad gateway nginx error.

The only apps not working are the ones using php though. I have a couple apps which are just html/css, they are working fine.

Then please share the log of the php reinstall … And what about the diagnosis, is it still unhappy about php being down

Here is the output of the php reinstall:

apt install php7.3-fpm php7.3 --reinstall
Reading package lists… Done
Building dependency tree
Reading state information… Done
The following NEW packages will be installed:
php7.3
0 upgraded, 1 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 43.4 kB/1,470 kB of archives.
After this operation, 78.8 kB of additional disk space will be used.
Get:1 http://ftp.debian.org/debian buster/main amd64 php7.3 all 7.3.19-1~deb10u1 [43.4 kB]
Fetched 43.4 kB in 1s (63.9 kB/s)
(Reading database … 54892 files and directories currently installed.)
Preparing to unpack …/php7.3-fpm_7.3.19-1~deb10u1_amd64.deb …
Unpacking php7.3-fpm (7.3.19-1~deb10u1) over (7.3.19-1~deb10u1) …]
Setting up php7.3-fpm (7.3.19-1~deb10u1) …]
Selecting previously unselected package php7.3.############…]
(Reading database … 54892 files and directories currently installed.)
Preparing to unpack …/php7.3_7.3.19-1~deb10u1_all.deb …
Unpacking php7.3 (7.3.19-1~deb10u1) …##############################…]
Setting up php7.3 (7.3.19-1~deb10u1) …#######################################…]
Processing triggers for man-db (2.8.5-2) …########################################################…]
Processing triggers for systemd (241-7~deb10u4) …

Here are logs from system update concerning php:

2020-08-31 10:45:49,853: WARNING - Creating config file /etc/php/7.3/mods-available/mbstring.ini with new version
2020-08-31 10:45:50,154: INFO - + Setting up python3-apt (1.8.4.1) …
2020-08-31 10:45:50,455: INFO - + Setting up libbrotli1:amd64 (1.0.7-2) …
2020-08-31 10:45:50,656: INFO - + Setting up python3-tk:amd64 (3.7.3-1) …
2020-08-31 10:45:50,757: INFO - + Setting up php-mbstring (2:7.3+69) …
2020-08-31 10:45:50,958: INFO - + Setting up libjansson4:amd64 (2.12-1) …
2020-08-31 10:45:51,058: INFO - + Setting up python3-pycurl (7.43.0.2-0.1) …
2020-08-31 10:45:51,359: INFO - + Setting up python3-gi (3.30.4-1) …
2020-08-31 10:45:51,560: INFO - + Setting up php7.3-xml (7.3.19-1~deb10u1) …
2020-08-31 10:45:51,761: WARNING -
2020-08-31 10:45:51,761: WARNING - Creating config file /etc/php/7.3/mods-available/dom.ini with new version
2020-08-31 10:45:52,162: WARNING -
2020-08-31 10:45:52,163: WARNING - Creating config file /etc/php/7.3/mods-available/simplexml.ini with new version
2020-08-31 10:45:52,463: WARNING -
2020-08-31 10:45:52,464: WARNING - Creating config file /etc/php/7.3/mods-available/wddx.ini with new version
2020-08-31 10:45:52,865: WARNING -
2020-08-31 10:45:52,865: WARNING - Creating config file /etc/php/7.3/mods-available/xml.ini with new version
2020-08-31 10:45:53,166: WARNING -
2020-08-31 10:45:53,166: WARNING - Creating config file /etc/php/7.3/mods-available/xmlreader.ini with new version
2020-08-31 10:45:53,567: WARNING -
2020-08-31 10:45:53,568: WARNING - Creating config file /etc/php/7.3/mods-available/xmlwriter.ini with new version
2020-08-31 10:45:53,969: WARNING -
2020-08-31 10:45:53,970: WARNING - Creating config file /etc/php/7.3/mods-available/xsl.ini with new version
2020-08-31 10:45:54,170: INFO - + Setting up php7.3-zip (7.3.19-1~deb10u1) …
2020-08-31 10:45:54,371: WARNING -
2020-08-31 10:45:54,373: WARNING - Creating config file /etc/php/7.3/mods-available/zip.ini with new version
2020-08-31 10:45:54,674: INFO - + Setting up python3-lib2to3 (3.7.3-1) …
2020-08-31 10:45:54,875: INFO - + Setting up php7.3-curl (7.3.19-1~deb10u1) …
2020-08-31 10:45:55,075: WARNING -
2020-08-31 10:45:55,076: WARNING - Creating config file /etc/php/7.3/mods-available/curl.ini with new version
2020-08-31 10:45:55,377: INFO - + Setting up python3-systemd (234-2+b1) …
2020-08-31 10:45:55,678: INFO - + Setting up php7.3-gd (7.3.19-1~deb10u1) …
2020-08-31 10:45:55,879: WARNING -
2020-08-31 10:45:55,879: WARNING - Creating config file /etc/php/7.3/mods-available/gd.ini with new version

Ran the diagnosis, but it said php7.3 was installed successfully.

was installed successfully … ? Is it an error ? :thinking:

The diagnosis from admin said it was successful. Here are the journalctl logs today for php:

Aug 31 10:45:33 systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
-- Subject: A start job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13185.
Aug 31 10:45:33 systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
-- Subject: A start job for unit php7.3-fpm.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has finished successfully.
-- 
-- The job identifier is 13185.
Aug 31 10:45:57 systemd[1]: Stopping The PHP 7.3 FastCGI Process Manager...
-- Subject: A stop job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13267.
Aug 31 10:45:57 systemd[1]: php7.3-fpm.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit php7.3-fpm.service has successfully entered the 'dead' state.
Aug 31 10:45:57 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
-- Subject: A stop job for unit php7.3-fpm.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has finished.
-- 
-- The job identifier is 13267 and the job result is done.
Aug 31 10:45:57 systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
-- Subject: A start job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13267.
Aug 31 10:45:57 systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
-- Subject: A start job for unit php7.3-fpm.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has finished successfully.
-- 
-- The job identifier is 13267.
Aug 31 10:47:45 systemd[1]: Reloading The PHP 7.3 FastCGI Process Manager.
-- Subject: A reload job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A reload job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13432.
Aug 31 10:47:45 systemd[1]: Reloaded The PHP 7.3 FastCGI Process Manager.
-- Subject: A reload job for unit php7.3-fpm.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A reload job for unit php7.3-fpm.service has finished.
-- 
-- The job identifier is 13432 and the job result is done.
Aug 31 11:23:26 systemd[1]: Stopping The PHP 7.3 FastCGI Process Manager...
-- Subject: A stop job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13602.
Aug 31 11:23:26 systemd[1]: php7.3-fpm.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit php7.3-fpm.service has successfully entered the 'dead' state.
Aug 31 11:23:26 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
-- Subject: A stop job for unit php7.3-fpm.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has finished.
-- 
-- The job identifier is 13602 and the job result is done.
Aug 31 11:23:26 systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
-- Subject: A start job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13602.
Aug 31 11:23:26 systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
-- Subject: A start job for unit php7.3-fpm.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has finished successfully.
-- 
-- The job identifier is 13602.
Aug 31 11:28:17 systemd[1]: Stopping The PHP 7.3 FastCGI Process Manager...
-- Subject: A stop job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13684.
Aug 31 11:28:17 systemd[1]: php7.3-fpm.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit php7.3-fpm.service has successfully entered the 'dead' state.
Aug 31 11:28:17 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
-- Subject: A stop job for unit php7.3-fpm.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has finished.
-- 
-- The job identifier is 13684 and the job result is done.
Aug 31 11:28:17 systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
-- Subject: A start job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13684.
Aug 31 11:28:17 systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
-- Subject: A start job for unit php7.3-fpm.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has finished successfully.
-- 
-- The job identifier is 13684.
Aug 31 11:29:48 systemd[1]: Stopping The PHP 7.3 FastCGI Process Manager...
-- Subject: A stop job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13849.
Aug 31 11:29:48 systemd[1]: php7.3-fpm.service: Succeeded.
-- Subject: Unit succeeded
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- The unit php7.3-fpm.service has successfully entered the 'dead' state.
Aug 31 11:29:48 systemd[1]: Stopped The PHP 7.3 FastCGI Process Manager.
-- Subject: A stop job for unit php7.3-fpm.service has finished
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A stop job for unit php7.3-fpm.service has finished.
-- 
-- The job identifier is 13849 and the job result is done.
Aug 31 11:29:48 systemd[1]: Starting The PHP 7.3 FastCGI Process Manager...
-- Subject: A start job for unit php7.3-fpm.service has begun execution
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has begun execution.
-- 
-- The job identifier is 13849.
Aug 31 11:29:48 systemd[1]: Started The PHP 7.3 FastCGI Process Manager.
-- Subject: A start job for unit php7.3-fpm.service has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- A start job for unit php7.3-fpm.service has finished successfully.
-- 
-- The job identifier is 13849.

So are there remaining issues …?

Still getting the 502 bad gateway error on all my php apps.

What about the migration about php7.0 -> php7.3 in Tools > Migrations ? Did that one run ? (I don’t remember the whole story of this thread…)

When php 7.3 was at the migration page, it did not migrate. I ended up back then deleting it and going forward.