• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Resolved Plesk with 404 not found after upgrading to Mariadb 10.5

GhaithJ

New Pleskian
hello guyz!

Sorry if I'm not in the right section of the forum.
I upgraded Mariadb from 10.1 to 10.5 by following the commands below:

Adding the repo:
sudo apt-get install software-properties-common dirmngr apt-transport-https
sudo apt-key adv --fetch-keys 'https://mariadb.org/mariadb_release_signing_key.asc'
sudo add-apt-repository 'deb [arch=amd64,i386,ppc64el,arm64] https://mirror.its.dal.ca/mariadb/repo/10.5/debian stretch main'
Upgrade:
sudo systemctl stop mariadb
sudo apt-get remove mariadb-server-10.1
sudo apt-get autoremove
sudo apt-get update
sudo apt-get install mariadb-server
sudo systemctl start mariadb
sudo mysql_upgrade
Once done, I checked Mariadb version and it's 10.5. The bad news, I just realized that Plesk seems to to be disappeared from my server. The 'plesk' command is no longer working.

I tried to follow this solution: https://support.plesk.com/hc/en-us/articles/213369589-Unable-to-access-Plesk-Unknown-database-psa-
but I'm facing an error message after running this command:
zcat mysql.daily.dump.0.gz | sed -n '/-- Current Database: `psa`/,/-- Current Database:*/p' | MYSQL_PWD=`cat /etc/psa/.psa.shadow` mysql -uadmin

Error message:
ERROR 1265 (01000) at line 3461: Data truncated for column 'event_type' at row 103


By checking the log, I have these lines when I try to access to plesk:

2022/02/24 22:40:56 [error] 12375#0: *1952 directory index of "/opt/psa/admin/htdocs/" is forbidden, client: 142.120.129.193, server: , request: "GET / HTTP/1.1", host: "srv.XXXXXXXX.XX:8443"
2022/02/24 22:40:56 [error] 12375#0: *1952 open() "/opt/psa/admin/htdocs/error_docs/403.html" failed (2: No such file or directory), client: 142.120.129.193, server: , request: "GET / HTTP/1.1", host: "srv.XXXXXXXX.XX:8443"


Any help would be much appreciated since it's a on prod server.



PS: Websites hosted on the server are working well.
 
A quick update, these are the package removed/installed (automatically) when upgrading to Mariadb 10.5

Start-Date: 2022-02-24 21:55:24
Commandline: apt-get remove mariadb-server-10.1
Remove: passenger-dev:amd64 (6.0.12-v.debian.9+p18.0.42.0+t220117.1118), psa-mailman-configurator:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), psa-mail-driver-common:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), plesk-dovecot-pigeonhole:amd64 (0.5.17.1-v.debian.9+p18.0.41.1+t220207.2342), psa-proftpd:amd64 (1.3.7c-v.debian.9+p18.0.42.0+t220117.1118), plesk-task-manager:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), pp18.0.34-bootstrapper:amd64 (18.0-v.debian.9+p18.0.34.2+t210325.1052), psa-updates:amd64 (18.0-v.debian.9+p18.0.41.0+t211211.0943), psa-libxml-proxy:amd64 (2.9.12-v.debian.9+p18.0.42.0+t220117.1118), plesk-kav-configurator:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), pp18.0.37-bootstrapper:amd64 (18.0-v.debian.9+p18.0.37.2+t210809.1806), psa-locale-base-en-us:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), psa-firewall:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), psa-drweb-configurator:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), psa-mnemo:amd64 (4.2.14-v.debian.9+p18.0.42.0+t220117.1118), mysql-server:amd64 (5.5.9999+default), wpb-headers:amd64 (18.0.29-43750.21032421), plesk-backup-utilities:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), plesk-service-node-utilities:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), libapache2-mod-passenger-plesk:amd64 (6.0.12-v.debian.9+p18.0.42.0+t220117.1118), plesk-mysql-server:amd64 (18.0-v.debian.9+p18.0.20.0+t191009.1747), plesk-resctrl:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), psa-logrotate:amd64 (3.8.2-v.debian.9+p18.0.41.1+t220207.2342), psa-watchdog:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), wpb-core:amd64 (18.0.29-43750.21032421), psa-kronolith:amd64 (4.2.29-v.debian.9+p18.0.42.0+t220117.1118), plesk-mail-pc-driver:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), plesk-config-troubleshooter:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), pp18.0.38-bootstrapper:amd64 (18.0-v.debian.9+p18.0.38.3+t211001.1903), plesk-modsecurity-configurator:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), mariadb-server-10.1:amd64 (10.1.48-0+deb9u2), default-mysql-server:amd64 (1.0.2), plesk-roundcube:amd64 (1.4.13-v.debian.9+p18.0.41.1+t220207.2342), plesk-web-hosting:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), psa-vhost:amd64 (18.0-v.debian.9+p18.0.42.0+t220118.0900), psa:amd64 (18.0.41-v.debian.9+p18.0.41.1+t220207.2342), pp18.0.32-bootstrapper:amd64 (18.0-v.debian.9+p18.0.32.2+t201217.1925), pp17.8.11-bootstrapper:amd64 (17.8.11-debian9.0.build1708191024.16), psa-imp:amd64 (6.2.27-v.debian.9+p18.0.42.0+t220117.1118), pp18.0.35-bootstrapper:amd64 (18.0-v.debian.9+p18.0.35.2+t210526.1158), psa-spamassassin:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), libpam-plesk:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), pp18.0.40-bootstrapper:amd64 (18.0-v.debian.9+p18.0.40.3+t220116.0005), plesk-completion:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), psa-passwd:amd64 (5.0.7-v.debian.9+p18.0.42.0+t220117.1118), psa-ingo:amd64 (3.2.16-v.debian.9+p18.0.42.0+t220117.1118), plesk-dovecot:amd64 (2.3.17.1-v.debian.9+p18.0.41.1+t220207.2342), psa-phpmyadmin:amd64 (5.1.1-v.debian.9+p18.0.41.1+t220207.2342), plesk-core-utilities:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), psa-horde:amd64 (5.2.23-v.debian.9+p18.0.42.0+t220117.1118), plesk-repair-kit:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), plesk-dovecot-imap-driver:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), pp18.0.33-bootstrapper:amd64 (18.0-v.debian.9+p18.0.33.1+t210225.1402), passenger:amd64 (6.0.12-v.debian.9+p18.0.42.0+t220117.1118), psa-turba:amd64 (4.2.25-v.debian.9+p18.0.42.0+t220117.1118), plesk-web-socket:amd64 (18.0-v.debian.9+p18.0.42.0+t220117.1118), pp18.0.36-bootstrapper:amd64 (18.0-v.debian.9+p18.0.36.0+t210526.1459), plesk-git-http:amd64 (18.0-v.debian.9+p18.0.41.0+t220106.1544), pp18.0.39-bootstrapper:amd64 (18.0-v.debian.9+p18.0.39.2+t211117.1817), psa-php-configurator:amd64 (1.8.0-v.debian.9+p18.0.42.0+t220117.1118), pp18.0.41-bootstrapper:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), pp-sitebuilder:amd64 (18.0.29-21032421), plesk-core:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342), plesk-l10n:amd64 (18.0-v.debian.9+p18.0.41.1+t220207.2342)
End-Date: 2022-02-24 21:59:21

Start-Date: 2022-02-24 22:00:20
Commandline: apt-get install mariadb-server
Install: mariadb-server-core-10.5:amd64 (1:10.5.15+maria~stretch, automatic), mariadb-server-10.5:amd64 (1:10.5.15+maria~stretch, automatic), galera-4:amd64 (26.4.11-stretch, automatic), libpcre2-8-0:amd64 (10.22-3, automatic), mariadb-client-10.5:amd64 (1:10.5.15+maria~stretch, automatic), mariadb-server:amd64 (1:10.5.15+maria~stretch), mariadb-client-core-10.5:amd64 (1:10.5.15+maria~stretch, automatic), libmariadb3:amd64 (1:10.5.15+maria~stretch, automatic)
Upgrade: mariadb-common:amd64 (10.1.48-0+deb9u2, 1:10.5.15+maria~stretch), libmariadbclient18:amd64 (10.1.48-0+deb9u2, 1:10.5.15+maria~stretch)
Remove: mariadb-server-core-10.1:amd64 (10.1.48-0+deb9u2), libmariadbclient-dev-compat:amd64 (10.1.48-0+deb9u2), libmariadbclient-dev:amd64 (10.1.48-0+deb9u2), galera-3:amd64 (25.3.19-2), default-libmysqlclient-dev:amd64 (1.0.2), plesk-gems-pre:amd64 (0.0.1-v.debian.9+p18.0.41.0+t211211.0943), mariadb-client-10.1:amd64 (10.1.48-0+deb9u2), mariadb-client-core-10.1:amd64 (10.1.48-0+deb9u2)
End-Date: 2022-02-24 22:00:59

Thank you guys for the help.
 
Thank you Evgeniy! I already tried that solution but I got an error when I tried to import the database (I tried different databases from different days).

If it can help someone else, I fixed the problem by removing the table exp_event from the last psa's dump and imported the database manually. After that, I re-ran the Plesk installer and decided to select to install the full packages (not only recommended ones). The installation went through.
Finally, I restart sw-engine and Plesk is back. Today I realized that roundcube wasn't accessible with an error message stating "DATABASE ERROR: CONNECTION FAILED". To fix that, I removed Roundcube from Plesk update interface and re-installed it again and it's back as normal.
 
Back
Top