• We value your experience with Plesk during 2024
    Plesk strives to perform even better in 2025. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2024.
    Please take this short survey:
    https://pt-research.typeform.com/to/AmZvSXkx
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.
  • We’re working on enhancing the Monitoring feature in Plesk, and we could really use your expertise! If you’re open to sharing your experiences with server and website monitoring or providing feedback, we’d love to have a one-hour online meeting with you.

Resolved Upgrade Mariadb 10.3 to 10.6 completes but trying to start MariaDB fails with error "systemctl status mariadb.service" and "journalctl -xe"

P

PeterK900

Basic Pleskian
Server operating system version
AlmaLinux 8.10 (Cerulean Leopard)
Plesk version and microupdate number
Plesk Obsidian v18.0.62_build1800240724.11 os_RedHat el8
I have completed the install of MariadB 10.6 , server, client, common and shared without any error messages. [see below]. However when I try and start MariaDB
sudo systemctl start mariadb , I get this error message...
.
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.

I found this post dealing with this error MySQL (MariaDB) Not Starting and ran this code...
cd /var/lib/mysql
ls
rm -r *
mysql_install_db --user=mysql --basedir=/usr --datadir=/var/lib/mysql
systemctl start mysqld
systemctl start mysql.service
systemctl start mariadb

But trying to start mariadb gives this message Job for mariadb.service failed because the control process exited with error code.

It seems to me I'm nearly there with the install. Please can someone help point what I'm doing wrong which is stopping the service starting. Thanks.

Here's part of the install process...

Install 8 Packages

Total download size: 43 M
Downloading Packages:
(1/8): boost-program-options-1.66.0-13.el8.x86_ 1.7 MB/s | 140 kB 00:00
(2/8): socat-1.7.4.1-1.el8.x86_64.rpm 2.1 MB/s | 322 kB 00:00
(3/8): perl-DBI-1.641-4.module_el8.6.0+2823+173 4.7 MB/s | 739 kB 00:00
(4/8): MariaDB-client-10.6.19-1.el8.x86_64.rpm 47 MB/s | 15 MB 00:00
(5/8): MariaDB-server-10.6.19-1.el8.x86_64.rpm 60 MB/s | 26 MB 00:00
(6/8): MariaDB-common-10.6.19-1.el8.x86_64.rpm 198 kB/s | 88 kB 00:00
(7/8): MariaDB-shared-10.6.19-1.el8.x86_64.rpm 430 kB/s | 128 kB 00:00
(8/8): galera-4-26.4.19-1.el8.x86_64.rpm 8.8 MB/s | 1.7 MB 00:00
--------------------------------------------------------------------------------
Total 40 MB/s | 43 MB 00:01
MariaDB 190 kB/s | 15 kB 00:00
Importing GPG key 0x1BB943DB:
Userid : "MariaDB Package Signing Key <[email protected]>"
Fingerprint: 1993 69E5 404B D5FC 7D2F E43B CBCB 082A 1BB9 43DB
From : https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
Key imported successfully
Importing GPG key 0xC74CD1D8:
Userid : "MariaDB Signing Key <[email protected]>"
Fingerprint: 177F 4010 FE56 CA33 3630 0305 F165 6F24 C74C D1D8
From : https://yum.mariadb.org/RPM-GPG-KEY-MariaDB
Key imported successfully
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Running scriptlet: MariaDB-shared-10.6.19-1.el8.x86_64 1/1
Installing : MariaDB-shared-10.6.19-1.el8.x86_64 1/14
Running scriptlet: MariaDB-shared-10.6.19-1.el8.x86_64 1/14
Installing : MariaDB-common-10.6.19-1.el8.x86_64 2/14
warning: /etc/my.cnf created as /etc/my.cnf.rpmnew

Installing : socat-1.7.4.1-1.el8.x86_64 3/14
Installing : perl-DBI-1.641-4.module_el8.6.0+2823+173faa7e.x86_ 4/14
Installing : MariaDB-client-10.6.19-1.el8.x86_64 5/14
Installing : boost-program-options-1.66.0-13.el8.x86_64 6/14
Running scriptlet: boost-program-options-1.66.0-13.el8.x86_64 6/14
Running scriptlet: galera-4-26.4.19-1.el8.x86_64 7/14
Installing : galera-4-26.4.19-1.el8.x86_64 7/14
Running scriptlet: galera-4-26.4.19-1.el8.x86_64 7/14
Running scriptlet: MariaDB-server-10.6.19-1.el8.x86_64 8/14
Installing : MariaDB-server-10.6.19-1.el8.x86_64 8/14
Running scriptlet: MariaDB-server-10.6.19-1.el8.x86_64 8/14
Obsoleting : mariadb-3:10.3.39-1.module_el8.8.0+3609+204d4ab0.x 9/14
Running scriptlet: mariadb-server-3:10.3.39-1.module_el8.8.0+3609+204 10/14
Obsoleting : mariadb-server-3:10.3.39-1.module_el8.8.0+3609+204 10/14
Running scriptlet: mariadb-server-3:10.3.39-1.module_el8.8.0+3609+204 10/14
Obsoleting : mariadb-connector-c-3.1.11-2.el8_3.x86_64 11/14
Obsoleting : mariadb-errmsg-3:10.3.39-1.module_el8.8.0+3609+204 12/14
Obsoleting : mariadb-common-3:10.3.39-1.module_el8.8.0+3609+204 13/14
Obsoleting : mariadb-connector-c-config-3.1.11-2.el8_3.noarch 14/14
Running scriptlet: MariaDB-server-10.6.19-1.el8.x86_64 14/14
Running scriptlet: mariadb-connector-c-config-3.1.11-2.el8_3.noarch 14/14
Verifying : boost-program-options-1.66.0-13.el8.x86_64 1/14
Verifying : perl-DBI-1.641-4.module_el8.6.0+2823+173faa7e.x86_ 2/14
Verifying : socat-1.7.4.1-1.el8.x86_64 3/14
Verifying : MariaDB-client-10.6.19-1.el8.x86_64 4/14
Verifying : mariadb-3:10.3.39-1.module_el8.8.0+3609+204d4ab0.x 5/14
Verifying : MariaDB-common-10.6.19-1.el8.x86_64 6/14
Verifying : mariadb-common-3:10.3.39-1.module_el8.8.0+3609+204 7/14
Verifying : mariadb-errmsg-3:10.3.39-1.module_el8.8.0+3609+204 8/14
Verifying : MariaDB-server-10.6.19-1.el8.x86_64 9/14
Verifying : mariadb-server-3:10.3.39-1.module_el8.8.0+3609+204 10/14
Verifying : MariaDB-shared-10.6.19-1.el8.x86_64 11/14
Verifying : mariadb-connector-c-3.1.11-2.el8_3.x86_64 12/14
Verifying : mariadb-connector-c-config-3.1.11-2.el8_3.noarch 13/14
Verifying : galera-4-26.4.19-1.el8.x86_64 14/14

Installed:
MariaDB-client-10.6.19-1.el8.x86_64
MariaDB-common-10.6.19-1.el8.x86_64
MariaDB-server-10.6.19-1.el8.x86_64
MariaDB-shared-10.6.19-1.el8.x86_64
boost-program-options-1.66.0-13.el8.x86_64
galera-4-26.4.19-1.el8.x86_64
perl-DBI-1.641-4.module_el8.6.0+2823+173faa7e.x86_64
socat-1.7.4.1-1.el8.x86_64

Complete!
[peterkaye@128 ~]$ sudo dnf install galera-4 MariaDB-client MariaDB-shared MariaDB-backup MariaDB-common -y
Last metadata expiration check: 0:02:01 ago on Fri 04 Oct 2024 08:49:51 AM UTC.
Package galera-4-26.4.19-1.el8.x86_64 is already installed.
Package MariaDB-client-10.6.19-1.el8.x86_64 is already installed.
Package MariaDB-shared-10.6.19-1.el8.x86_64 is already installed.
Package MariaDB-common-10.6.19-1.el8.x86_64 is already installed.
Dependencies resolved.
================================================================================
Package Architecture Version Repository Size
================================================================================
Installing:
MariaDB-backup x86_64 10.6.19-1.el8 mariadb 7.2 M

Transaction Summary
================================================================================
Install 1 Package

Total download size: 7.2 M
Installed size: 28 M
Downloading Packages:
MariaDB-backup-10.6.19-1.el8.x86_64.rpm 25 MB/s | 7.2 MB 00:00
--------------------------------------------------------------------------------
Total 25 MB/s | 7.2 MB 00:00
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
Preparing : 1/1
Installing : MariaDB-backup-10.6.19-1.el8.x86_64 1/1
Running scriptlet: MariaDB-backup-10.6.19-1.el8.x86_64 1/1
Verifying : MariaDB-backup-10.6.19-1.el8.x86_64 1/1

Installed:
MariaDB-backup-10.6.19-1.el8.x86_64

Complete!
[peterkaye@128 ~]$ sudo systemctl start mariadb
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
[peterkaye@128 ~]$
 
Would
See "systemctl status mariadb.service" and "journalctl -xe" for details.
Click to expand...
give some more details on it? MariaDB has probably logged the reason why it doesn't want to start. Most frequently there is an error in /etc/my.cnf.
 
Bitpalast said:
Would

give some more details on it? MariaDB has probably logged the reason why it doesn't want to start. Most frequently there is an error in /etc/my.cnf.
Click to expand...
Thanks Bitpalast. You were spot on - it includes an error message! Here's the content of my.cnf...

# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

[mysqld]
sql_mode=ERROR_FOR_DIVISION_BY_ZERO,NO_AUTO_CREATE_USER,NO_ENGINE_SUBSTITUTION
bind-address = ::ffff:127.0.0.1
local-infile=0

Can you help by telling me what it means and what I need to do to make the service restart work? Thanks for your help so far.
 
If you could please provide the log message(s) that describe the startup issue, I am sure that other experts here or myself will be able to help.
 
Bitpalast said:
If you could please provide the log message(s) that describe the startup issue, I am sure that other experts here or myself will be able to help.
Click to expand...
Thanks. Is this what you want?
[peterkaye@128 mysql]$ sudo systemctl start mysqld
Job for mariadb.service failed because the control process exited with error code.
See "systemctl status mariadb.service" and "journalctl -xe" for details.
 
Bitpalast said:
journalctl -xe -u mariadb
Click to expand...
[peterkaye@128 etc]$ journalctl -xe -u mariadb
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.

-- Logs begin at Fri 2024-10-04 11:13:25 UTC, end at Fri 2024-10-04 15:06:26 UT>
-- No entries --
lines 1-2/2 (END)
 
That's not possible when MariaDB is on your system. It must log start/stop actions. Maybe try "journalctl -xe" without the unit parameter and scroll through the actions. You can also check /var/log/messages or /var/log/syslog for entries related to MariaDB. Generally: When MariaDB starts or stops, it logs its actions to the system log. You need these entries to identify the issue. If there are no log entries, check Error Log whether you need to enable logging (maybe it's turned off?).
 
Another approach can be to contact official Plesk support. They'll most likely succeed in identifying and solving the issue.
 
Thanks Bitpalast. The outputs for journalctl -xe and /var/log/messages are shown below. /var/log/syslog produces no output. I'm afraid the output gives me no clues as to the problem or how to solve it.
Plesk support is a paid for option and may not be possible as my Plesk licence is in the name of the web hosting company.
Unless you or another Pleskian can spot something, I fear I'm at a dead end on this. Is the procedure I followed to install the new new MariaDB version causing the problem? It is is based on this post How to Upgrade MariaDB on Linux (AlmaLinux) | Liquid Web

"journalctl -xe" produces....
[peterkaye@128 etc]$ journalctl -xe
Hint: You are currently not seeing messages from other users and the system.
Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
Pass -q to turn off this notice.
Oct 04 11:37:10 128.201.148.37.host.secureserver.net sudo[24435]: pam_unix(sudo>
Oct 04 11:39:31 128.201.148.37.host.secureserver.net sudo[24435]: pam_unix(sudo>
Oct 04 11:41:43 128.201.148.37.host.secureserver.net sudo[55600]: peterkaye : T>
Oct 04 11:41:43 128.201.148.37.host.secureserver.net sudo[55600]: pam_unix(sudo>
Oct 04 11:45:00 128.201.148.37.host.secureserver.net sudo[55600]: pam_unix(sudo>
Oct 04 11:46:17 128.201.148.37.host.secureserver.net sudo[55725]: peterkaye : T>
Oct 04 11:46:17 128.201.148.37.host.secureserver.net sudo[55725]: pam_unix(sudo>
Oct 04 11:46:17 128.201.148.37.host.secureserver.net sudo[55725]: pam_unix(sudo>
Oct 04 11:46:46 128.201.148.37.host.secureserver.net sudo[55735]: peterkaye : T>
Oct 04 11:46:46 128.201.148.37.host.secureserver.net sudo[55735]: pam_unix(sudo>
Oct 04 11:46:47 128.201.148.37.host.secureserver.net sudo[55735]: pam_unix(sudo>
Oct 04 11:47:33 128.201.148.37.host.secureserver.net sudo[55763]: peterkaye : T>
Oct 04 11:47:33 128.201.148.37.host.secureserver.net sudo[55763]: pam_unix(sudo>
Oct 04 11:48:30 128.201.148.37.host.secureserver.net sudo[55763]: pam_unix(sudo>
Oct 04 11:50:17 128.201.148.37.host.secureserver.net sudo[56747]: peterkaye : T>
Oct 04 11:50:17 128.201.148.37.host.secureserver.net sudo[56747]: pam_unix(sudo>
Oct 04 11:50:20 128.201.148.37.host.secureserver.net sudo[56747]: pam_unix(sudo>
Oct 04 11:50:57 128.201.148.37.host.secureserver.net sudo[56761]: peterkaye : T>
Oct 04 11:50:57 128.201.148.37.host.secureserver.net sudo[56761]: pam_unix(sudo>
Oct 04 11:50:57 128.201.148.37.host.secureserver.net sudo[56761]: pam_unix(sudo>
Oct 04 11:51:21 128.201.148.37.host.secureserver.net sudo[56821]: peterkaye : T>
Oct 04 11:51:21 128.201.148.37.host.secureserver.net sudo[56821]: pam_unix(sudo>
Oct 04 15:06:26 128.201.148.37.host.secureserver.net sudo[56821]: pam_unix(sudo>
lines 257-279/279 (END)
Oct 04 11:37:10 128.201.148.37.host.secureserver.net sudo[24435]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:39:31 128.201.148.37.host.secureserver.net sudo[24435]: pam_unix(sudo:session): session closed for user root
Oct 04 11:41:43 128.201.148.37.host.secureserver.net sudo[55600]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/vi /etc/yum.repos.d/mariadb.re>
Oct 04 11:41:43 128.201.148.37.host.secureserver.net sudo[55600]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:45:00 128.201.148.37.host.secureserver.net sudo[55600]: pam_unix(sudo:session): session closed for user root
Oct 04 11:46:17 128.201.148.37.host.secureserver.net sudo[55725]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/dnf remove MariaDB-server -y
Oct 04 11:46:17 128.201.148.37.host.secureserver.net sudo[55725]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:46:17 128.201.148.37.host.secureserver.net sudo[55725]: pam_unix(sudo:session): session closed for user root
Oct 04 11:46:46 128.201.148.37.host.secureserver.net sudo[55735]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/dnf clean all
Oct 04 11:46:46 128.201.148.37.host.secureserver.net sudo[55735]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:46:47 128.201.148.37.host.secureserver.net sudo[55735]: pam_unix(sudo:session): session closed for user root
Oct 04 11:47:33 128.201.148.37.host.secureserver.net sudo[55763]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/dnf install MariaDB-server -y
Oct 04 11:47:33 128.201.148.37.host.secureserver.net sudo[55763]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:48:30 128.201.148.37.host.secureserver.net sudo[55763]: pam_unix(sudo:session): session closed for user root
Oct 04 11:50:17 128.201.148.37.host.secureserver.net sudo[56747]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/dnf install galera-4 MariaDB-c>
Oct 04 11:50:17 128.201.148.37.host.secureserver.net sudo[56747]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:50:20 128.201.148.37.host.secureserver.net sudo[56747]: pam_unix(sudo:session): session closed for user root
Oct 04 11:50:57 128.201.148.37.host.secureserver.net sudo[56761]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/systemctl start mariadb
Oct 04 11:50:57 128.201.148.37.host.secureserver.net sudo[56761]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 11:50:57 128.201.148.37.host.secureserver.net sudo[56761]: pam_unix(sudo:session): session closed for user root
Oct 04 11:51:21 128.201.148.37.host.secureserver.net sudo[56821]: peterkaye : TTY=pts/0 ; PWD=/etc ; USER=root ; COMMAND=/bin/vi /etc/my.cnf
Oct 04 11:51:21 128.201.148.37.host.secureserver.net sudo[56821]: pam_unix(sudo:session): session opened for user root by peterkaye(uid=1000)
Oct 04 15:06:26 128.201.148.37.host.secureserver.net sudo[56821]: pam_unix(sudo:session): session closed for user root

/var/log/messages produces this...
[peterkaye@128 etc]$ sudo vi /var/log/messages

Oct 4 10:54:37 128 kernel: Command line: BOOT_IMAGE=(hd0,msdos1)/boot/vmlinuz-4.18.0-553.8.1.el8_10.x86_64 root=UUID=84978f19-30c0-48ee-b103-b1006cc2ce58 ro console=ttyS0,115200n8 no_timer_check net.ifnames=0 crashkernel=auto rhgb quiet net.ifnames=0 biosdevname=0 console=ttyS0,115200n8 console=tty1
Oct 4 10:54:37 128 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Oct 4 10:54:37 128 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Oct 4 10:54:37 128 kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Oct 4 10:54:37 128 kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Oct 4 10:54:37 128 kernel: x86/fpu: Enabled xstate features 0x7, context size is 832 bytes, using 'compacted' format.
Oct 4 10:54:37 128 kernel: signal: max sigframe size: 1776
Oct 4 10:54:37 128 kernel: BIOS-provided physical RAM map:
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x00000000000f0000-0x00000000000fffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x0000000000100000-0x000000007ffdbfff] usable
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x000000007ffdc000-0x000000007fffffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x00000000b0000000-0x00000000bfffffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x00000000feffc000-0x00000000feffffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x00000000fffc0000-0x00000000ffffffff] reserved
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x0000000100000000-0x000000017fffffff] usable
Oct 4 10:54:37 128 kernel: BIOS-e820: [mem 0x000000fd00000000-0x000000ffffffffff] reserved
Oct 4 10:54:37 128 kernel: NX (Execute Disable) protection: active
Oct 4 10:54:37 128 kernel: SMBIOS 2.8 present.
Oct 4 10:54:37 128 kernel: DMI: Optimized Hosting KVM, BIOS 1.16.3-2.el9 04/01/2014
Oct 4 10:54:37 128 kernel: Hypervisor detected: KVM
Oct 4 10:54:37 128 kernel: kvm-clock: Using msrs 4b564d01 and 4b564d00
Oct 4 10:54:37 128 kernel: kvm-clock: using sched offset of 13859256557 cycles
Oct 4 10:54:37 128 kernel: clocksource: kvm-clock: mask: 0xffffffffffffffff max_cycles: 0x1cd42e4dffb, max_idle_ns: 881590591483 ns
Oct 4 10:54:37 128 kernel: tsc: Detected 2349.998 MHz processor
Oct 4 10:54:37 128 kernel: last_pfn = 0x180000 max_arch_pfn = 0x400000000
Oct 4 10:54:37 128 kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Oct 4 10:54:37 128 kernel: last_pfn = 0x7ffdc max_arch_pfn = 0x400000000
Oct 4 10:54:37 128 kernel: found SMP MP-table at [mem 0x000f53e0-0x000f53ef]
Oct 4 10:54:37 128 kernel: Using GB pages for direct mapping
Oct 4 10:54:37 128 kernel: RAMDISK: [mem 0x3474c000-0x3639dfff]
Oct 4 10:54:37 128 kernel: ACPI: Early table checksum verification disabled
Oct 4 10:54:37 128 kernel: ACPI: RSDP 0x00000000000F51A0 000014 (v00 BOCHS )
Oct 4 10:54:37 128 kernel: ACPI: RSDT 0x000000007FFE26D5 000034 (v01 BOCHS BXPC 00000001 BXPC 00000001)
Oct 4 10:54:37 128 kernel: ACPI: FACP 0x000000007FFE24FD 0000F4 (v03 BOCHS BXPC 00000001 BXPC 00000001)
Oct 4 10:54:37 128 kernel: ACPI: DSDT 0x000000007FFE0040 0024BD (v01 BOCHS BXPC 00000001 BXPC 00000001)
Oct 4 10:54:37 128 kernel: ACPI: FACS 0x000000007FFE0000 000040
Oct 4 10:54:37 128 kernel: ACPI: APIC 0x000000007FFE25F1 000080 (v01 BOCHS BXPC 00000001 BXPC 00000001)
Oct 4 10:54:37 128 kernel: ACPI: MCFG 0x000000007FFE2671 00003C (v01 BOCHS BXPC 00000001 BXPC 00000001)
Oct 4 10:54:37 128 kernel: ACPI: WAET 0x000000007FFE26AD 000028 (v01 BOCHS BXPC 00000001 BXPC 00000001)
 
Hi,

Please refer to the official Plesk Support articles for managing Plesk:

Regarding the output of the # journalctl -xe -u mariadb command, it seems you're not logged in as root, which is why you're unable to view the relevant information.

If you purchased your license from a reseller, they should be providing support. If the reseller is unable to assist, here is an alternative: the first 30 days are free:
 
Maarten said:
Hi,

Please refer to the official Plesk Support articles for managing Plesk:

Regarding the output of the # journalctl -xe -u mariadb command, it seems you're not logged in as root, which is why you're unable to view the relevant information.

If you purchased your license from a reseller, they should be providing support. If the reseller is unable to assist, here is an alternative: the first 30 days are free:
Click to expand...
Thanks Maarten for the point about login credentials. And also about Plesk support. I'll check both these out.
 
I've managed to complete the update with OS Ubuntu 20.x rather than AlmaLinux8.

Here are two articles that helped...
How to Upgrade MariaDB Server to a Newer Version in Ubuntu
https://community.hetzner.com/tutorials/how-to-install-mariadb-10-6-on-ubuntu-20-04

I started with the first article. Then I hit a problem with the command sudo mariadb-secure-installation which required a root password - which is not as I first thought the server root but the mysql root user password. Having no idea what it was I used this link to set it to a new value. This done I continued with the upgrade procedure described in the second link above. All went well until I checked the Mariadb status sudo systemctl status mariadb. This produced a series of responses including code=exited and ending with a message Failed to start Mariadb 10.6.20 database server. [This shows the version is now 10.6.20].

When I run sudo systemctl start mariadb I get failure message saying the process exited with an error code and pointing to systemctl status mariadb.service and jourmal -xe. The message that started this post! The first string produced more errors and ended with the message that the server failed to start. The second string started with "The unit mariadb.service has entered the 'failed' state with result 'exit-code' None of the responses indicated errors.

Interesting the server wasn't brokem - Plesk working fine. I rebooted the server. Plesk still showed the Mariadb version as 10.3 but mysql -V showed the version of 10.6.20! And installing software that requires a Mariadb version > 10.3 works. So all seems good. Was it jourmal -xe or the reboot?

Success! The only remaining thing seems to be to tell Plesk that ther version is now 10.6.20. This link provides two ways of doing this. The UI method - Tools & Settings > Database Servers, click Upgrade doesn't work because I can't find an upgrade button. So I guess I'll have to use the command-line route. Thanks to everyone who inspired me to continue with this.
 
You must log in or register to reply here.

Similar threads

N
Resolved Update MariaDB from 10.4.32 to 10.5
2
Replies
28
Views
9K
NITROFOX
N
Dene Wilby
Resolved Upgrading my MariaDB. Issues.
Replies
8
Views
430
Dene Wilby
Dene Wilby
J
Issue Update MariaDB 5.5 to 10.5 failed, system crash
Replies
1
Views
755
JuanCar
J
davidds64
Question How to upgrade MariaDB to latest version with Plesk Obsidian on Alma Linux 9
Replies
5
Views
1K
davidds64
davidds64
Franco
Resolved CentOs2Alma conversion failed - disk space?
Replies
7
Views
1K
Bitpalast
Bitpalast
Back
Top