Upgrade cannot start mariadb

Help and Support Raspberry Pi
1

Hi, just done the update to 19.4 and since then mariadb will not start and load the libraries. Running systemctl status mariadb.service gives the following:

osmc@osmc2:~$ sudo systemctl start mariadb.service
Job for mariadb.service failed because the control process exited with error code.
See “systemctl status mariadb.service” and “journalctl -xe” for details.
osmc@osmc2:~$ systemctl status mariadb.service

  • mariadb.service - MariaDB 10.3.31 database server
    Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
    Active: failed (Result: exit-code) since Sat 2022-03-19 12:15:10 GMT; 1min 43s ago
    Docs: man:mysqld(8)
    systemd - MariaDB Knowledge Base
    Process: 1068 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
    Process: 1069 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
    Process: 1071 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=
    Process: 1119 ExecStart=/usr/sbin/mysqld $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
    Main PID: 1119 (code=exited, status=1/FAILURE)
    Status: “MariaDB server is down”

Mar 19 12:15:08 osmc2 systemd[1]: Starting MariaDB 10.3.31 database server…
Mar 19 12:15:08 osmc2 mysqld[1119]: 2022-03-19 12:15:08 0 [Note] /usr/sbin/mysqld (mysqld 10.3.31-MariaDB-0+deb10u1) starting as process 1119 …
Mar 19 12:15:10 osmc2 systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
Mar 19 12:15:10 osmc2 systemd[1]: mariadb.service: Failed with result ‘exit-code’.
Mar 19 12:15:10 osmc2 systemd[1]: Failed to start MariaDB 10.3.31 database server.

Anyone have any ideas on how to fix (very much a non-expert dabler here)? Thanks!

3

Do you still have space available on the SD Card?
Also maybe the SD Card went into write only mode? Try to write a file to it then reboot and see if the file is still there.

4

Thanks for help. Still have 27G free on sdcard and can create and save a file successfully (and still there after reboot).

5

Hi,

What does journalctl -xe report?

Thanks Tom.

6

Hi Tom,

journalctl -xe reports:

osmc@osmc2:~$ journalctl -xe
--
-- The job identifier is 1.
Mar 20 07:45:57 osmc2 systemd[3119]: Startup finished in 365ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The user manager instance for user 1000 has been started. All services queued
-- for starting have been started. Note that other services might still be start
-- up or be started at any later time.
--
-- Startup of the manager took 365786 microseconds.
Mar 20 07:45:57 osmc2 systemd[1]: Started Session 3 of user osmc.
-- Subject: A start job for unit session-3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-3.scope has finished successfully.
--
-- The job identifier is 604.
Mar 20 07:45:58 osmc2 sudo[3139]:     osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=r
Mar 20 07:45:58 osmc2 sudo[3139]: pam_unix(sudo:session): session opened for use
Mar 20 07:45:58 osmc2 sudo[3139]: pam_unix(sudo:session): session closed for use
lines 1352-1374/1374 (END)
--
-- The job identifier is 1.
Mar 20 07:45:57 osmc2 systemd[3119]: Startup finished in 365ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The user manager instance for user 1000 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
--
-- Startup of the manager took 365786 microseconds.
Mar 20 07:45:57 osmc2 systemd[1]: Started Session 3 of user osmc.
-- Subject: A start job for unit session-3.scope has finished successfully
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit session-3.scope has finished successfully.
--
-- The job identifier is 604.
Mar 20 07:45:58 osmc2 sudo[3139]:     osmc : TTY=pts/0 ; PWD=/home/osmc ; USER=root ; COMMAND=/usr/bin/getent shadow osmc
Mar 20 07:45:58 osmc2 sudo[3139]: pam_unix(sudo:session): session opened for user root by osmc(uid=0)
Mar 20 07:45:58 osmc2 sudo[3139]: pam_unix(sudo:session): session closed for user root

Thanks for any help you can give

7

Thanks for your help, have managed to fix the issue (although not idea why it occurred).

Solution:

Delete (or rename) ib_logfile0 and ib_logfile1 located in /var/lib/mysql/

Was then immediately able to start mariadb service, and a reboot has all my libraries back into kodi

2 Likes