• 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 Update MarianDB from v10.1.48 to v10.2 or later on Plesk Obsidian v18.0.45

H

heydemar

Basic Pleskian
Server operating system version
Ubuntu 18.04
Plesk version and microupdate number
18.0.45_build1800220722.16
Hi,
I´am running a Plesk Server with Plesk Obsidian v18.0.45_build1800220722.16 os_Ubuntu 18.04 I need to Update my MarianDB from v10.1.48 to v10.2 or later.
On the Plesk I run some Wordpress instance.
Is there a way to Update over GUI?

Can someone give me support?

Thanks!!!
 
root@vps4:~# apt-get install mariadb-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
mariadb-server is already the newest version (1:10.2.44+maria~bionic).
The following packages were automatically installed and are no longer required:
linux-headers-4.15.0-45 linux-headers-4.15.0-45-generic linux-image-4.15.0-45-generic linux-modules-4.15.0-45-generic linux-modules-extra-4.15.0-45-generic
Use 'apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 7 not upgraded.
2 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up mariadb-server-10.2 (1:10.2.44+maria~bionic) ...
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
invoke-rc.d: initscript mysql, action "start" failed.
● mariadb.service - MariaDB 10.2.44 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Drop-In: /etc/systemd/system/mariadb.service.d
└─migrated-from-my.cnf-settings.conf
Active: failed (Result: exit-code) since Fri 2022-07-29 13:49:26 CEST; 48ms ago
Docs: man:mysqld(8)
systemd
Process: 4999 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS --basedir=/usr $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Process: 4847 ExecStartPre=/bin/sh -c [ ! -e /usr/bin/galera_recovery ] && VAR= || VAR=`cd /usr/bin/..; /usr/bin/galera_recovery`; [ $? -eq 0 ] && systemctl set-environment _WSREP_START_POSITION=$VAR || exit 1 (code=exited, status=0/SUCCESS)
Process: 4841 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 4840 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Main PID: 4999 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"

Jul 29 13:49:23 vps4.XXX.com systemd[1]: Starting MariaDB 10.2.44 database server...
Jul 29 13:49:24 vps4.XXX.com mysqld[4999]: 2022-07-29 13:49:24 140577917830848 [Note] /usr/sbin/mysqld (mysqld 10.2.44-MariaDB-1:10.2.44+maria~bionic) starting as process 4999 ...
Jul 29 13:49:26 vps4.XXX.com systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Jul 29 13:49:26 vps4.XXX.com systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jul 29 13:49:26 vps4.XXX.com systemd[1]: Failed to start MariaDB 10.2.44 database server.
dpkg: error processing package mariadb-server-10.2 (--configure):
installed mariadb-server-10.2 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of mariadb-server:
mariadb-server depends on mariadb-server-10.2 (>= 1:10.2.44+maria~bionic); however:
Package mariadb-server-10.2 is not configured yet.

dpkg: error processing package mariadb-server (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
mariadb-server-10.2
mariadb-server
E: Sub-process /usr/bin/dpkg returned an error code (1)


The Installation ask of a MarianDB Root PW, I take the password for my Plesk root User
 
MariaDB 10.2 is no longer supported:
endoflife.date

MariaDB

Check end-of-life, release policy and support schedule for MariaDB.
endoflife.date endoflife.date

You should use at least MariaDB 10.6
 
With:
sudo apt-get install mariadb-server-10.5
Everything is fine...

1659099595998.png

I have try this Update on a Test-Envioment.
Is there any impact for Wordpress??
 
It's a safe upgrade and WordPress will no longer complain that you're using an older database server.

After the upgrade has finished and all seems well, run
# plesk repair db -y

That will fix some field definitions like date and time fields in the Plesk database.
 
root@vps1:~# plesk repair db -y
Checking the Plesk database using the native database server tools .. [OK]
Checking the structure of the Plesk database ........................ [OK]
Checking the consistency of the Plesk database ...................... [OK]
Error messages: 0; Warnings: 0; Errors resolved: 0

Thanks so much for Support!!!
 
But now there is another error in the Plesk GUI:
1659113069231.png

And:

root@vps1:~# apt-get update
Hit:1 Index of /ubuntu/PMM_0.1.10 bionic InRelease
Hit:2 Index of /pool/PSA_18.0.45_9299 bionic InRelease
Hit:3 Index of /PHP70_17 bionic InRelease
Hit:4 Index of /pool/PHP_7.1.33_98 bionic InRelease
Hit:5 Index of /pool/PHP_7.2.34_151 bionic InRelease
Ign:6 http://dl.google.com/linux/mod-pagespeed/deb stable InRelease
Hit:7 Index of /pool/PHP_7.3.33_248 bionic InRelease
Get:8 Index of /PHP74_17 bionic InRelease [3,547 B]
Hit:9 Index of /PHP80_17 bionic InRelease
Hit:10 http://dl.google.com/linux/mod-pagespeed/deb stable Release
Hit:11 http://mirror.truenetwork.ru/mariadb/repo/10.5/ubuntu bionic InRelease
Hit:12 Index of /ubuntu bionic-security InRelease
Hit:13 http://mirror.truenetwork.ru/mariadb/repo/10.6/ubuntu bionic InRelease
Hit:14 Index of /ubuntu bionic InRelease
Hit:15 Index of /ubuntu bionic-updates InRelease
Hit:16 Index of /kernelcare-debian/8/ stable InRelease
Hit:17 Index of /ubuntu bionic-backports InRelease
Err:18 http://dl.google.com/linux/mod-pagespeed/deb stable Release.gpg
The following signatures were invalid: EXPKEYSIG 78BD65473CB3BD13 Google Inc. (Linux Packages Signing Authority) <[email protected]>
Fetched 3,547 B in 2s (2,307 B/s)
Reading package lists... Done
W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: http://dl.google.com/linux/mod-pagespeed/deb stable Release: The following signatures were invalid: EXPKEYSIG 78BD65473CB3BD13 Google Inc. (Linux Packages Signing Authority) <[email protected]>
W: Failed to fetch http://dl.google.com/linux/mod-pagespeed/deb/dists/stable/Release.gpg The following signatures were invalid: EXPKEYSIG 78BD65473CB3BD13 Google Inc. (Linux Packages Signing Authority) <[email protected]>
W: Some index files failed to download. They have been ignored, or old ones used instead.
 
You must log in or register to reply here.

Similar threads

G
Issue Upgrade 18.0.46 to 18.0.60 fails
Replies
9
Views
6K
GPDCenter
G
J
Issue Need advice on upgrading Plesk Obsidian Version 18.0.44 to latest version to have DKIM 2048 key length
Replies
7
Views
354
AgustinLorenzo
A
Z
Resolved Update Components greyed out
Replies
3
Views
265
AYamshanov
AYamshanov
M
Issue unable to add component PLESK-PHP8.2.
Replies
1
Views
129
Nikolay
Nikolay
N
Issue Can't update plesk
Replies
7
Views
737
Peter Debik
P
Back
Top