Mailing List Archive: Unable to start mariadb after Debian system upgrade

Unable to start mariadb after Debian system upgrade

Jan 22, 2023, 1:26 AM

Post #1 of 6 (353 views)

Hello!

Yesterday I updated from Debian Buster to Bullseye and I did not see any
errors during the update. But after a reboot I am no longer able to
start MariaDB.

Any help would be appreciated to fix this problem.

Best regards,
Peter Carlsson

server:/etc# 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.

server:/etc# systemctl status mariadb.service
? mariadb.service - MariaDB 10.5.18 database server
Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Sun 2023-01-22 10:20:31 CET; 49s ago
Docs: man:mariadbd(8)
https://mariadb.com/kb/en/library/systemd/
Process: 23847 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=0/SUCCESS)
Process: 23848 ExecStartPre=/bin/sh -c systemctl unset-environment _WSREP_START_POSITION (code=exited, status=0/SUCCESS)
Process: 23850 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: 23901 ExecStart=/usr/sbin/mariadbd $MYSQLD_OPTS $_WSREP_NEW_CLUSTER $_WSREP_START_POSITION (code=exited, status=1/FAILURE)
Main PID: 23901 (code=exited, status=1/FAILURE)
Status: "MariaDB server is down"
CPU: 107ms

jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Starting shutdown...
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' init function returned error.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] Plugin 'FEEDBACK' is disabled.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Aborting
jan 22 10:20:31 server systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with result 'exit-code'.
jan 22 10:20:31 server systemd[1]: Failed to start MariaDB 10.5.18 database server.

jan 22 10:20:31 server systemd[1]: Starting MariaDB 10.5.18 database server...
?? Subject: A start job for unit mariadb.service has begun execution
?? Defined-By: systemd
?? Support: https://www.debian.org/support
??
?? A start job for unit mariadb.service has begun execution.
??
?? The job identifier is 19499.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] /usr/sbin/mariadbd (mysqld 10.5.18-MariaDB-0+deb11u1) starting as process 23901 ...
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Uses event mutexes
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Number of pools: 1
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Using SSE4.2 crc32 instructions
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Using Linux native AIO
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Completed initialization of buffer pool
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] InnoDB: Space id and page no stored in the page, read in are [page id: space=0, page number=32824], should be [page id: space=0, page number=1081400]
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] InnoDB: invalid undo header offset 65535
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Retry with innodb_force_recovery=5
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Starting shutdown...
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' init function returned error.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] Plugin 'FEEDBACK' is disabled.
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Aborting
jan 22 10:20:31 server systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
?? Subject: Unit process exited
?? Defined-By: systemd
?? Support: https://www.debian.org/support
??
?? An ExecStart= process belonging to unit mariadb.service has exited.
??
?? The process' exit code is 'exited' and its exit status is 1.
jan 22 10:20:31 server audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=unconfined msg='unit=mariadb comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with result 'exit-code'.
?? Subject: Unit failed
?? Defined-By: systemd
?? Support: https://www.debian.org/support
??
?? The unit mariadb.service has entered the 'failed' state with result 'exit-code'.
jan 22 10:20:31 server systemd[1]: Failed to start MariaDB 10.5.18 database server.
?? Subject: A start job for unit mariadb.service has failed
?? Defined-By: systemd
?? Support: https://www.debian.org/support
??
?? A start job for unit mariadb.service has finished with a failure.
??
?? The job identifier is 19499 and the job result is failed.
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: Unable to start mariadb after Debian system upgrade [ In reply to ]

jharbestonus at gmail

Jan 22, 2023, 6:46 AM

Post #2 of 6 (352 views)

Permalink

>
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Starting shutdown...
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' init function returned error.
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] Plugin 'FEEDBACK' is disabled.
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Aborting
> jan 22 10:20:31 server systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
> jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with result 'exit-code'.
> jan 22 10:20:31 server systemd[1]: Failed to start MariaDB 10.5.18 database server.
>

The first line in the above error is indicating that your database is messed up so that InnoDB cannot start. Looks like you need to fix the db first.

Regards
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: Unable to start mariadb after Debian system upgrade [ In reply to ]

mikep at randomtraveller

Jan 22, 2023, 7:07 AM

Post #3 of 6 (352 views)

Permalink

On 22/01/2023 14:46, Jay Harbeston wrote:
>>
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] InnoDB: Plugin initialization aborted with error Data structure corruption
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] InnoDB: Starting shutdown...
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' init function returned error.
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note] Plugin 'FEEDBACK' is disabled.
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Unknown/unsupported storage engine: InnoDB
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Aborting
>> jan 22 10:20:31 server systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE
>> jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with result 'exit-code'.
>> jan 22 10:20:31 server systemd[1]: Failed to start MariaDB 10.5.18 database server.
>>
>
> The first line in the above error is indicating that your database is messed up so that InnoDB cannot start. Looks like you need to fix the db first.
>
I think you missed the other erorr message:

jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Unknown/unsupported storage
engine: InnoDB

If the db is Innodb and Innodb hasn't been installed, I could easily see this error happening.

--

Mike Perkins

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: Unable to start mariadb after Debian system upgrade [ In reply to ]

justin at jalcorn

Jan 22, 2023, 7:24 AM

Post #4 of 6 (352 views)

Permalink

>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
Plugin 'InnoDB' init function returned error.
>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

looks like InnoDB is installed but corrupt. See if you can remove and
reinstall just InnoDB, if not reinstall mariadb
--
Justin B. Alcorn
The views expressed are not necessarily my own, much less anyone else's
PGP Fingerprint CCEB F776 C3FD 1050 C8DB 532E B8B9 BED7 7764 406C

On Sun, Jan 22, 2023 at 10:07 AM Mike Perkins <mikep@randomtraveller.org.uk>
wrote:

> On 22/01/2023 14:46, Jay Harbeston wrote:
> >>
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> InnoDB: Plugin initialization aborted with error Data structure corruption
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note]
> InnoDB: Starting shutdown...
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> Plugin 'InnoDB' init function returned error.
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note]
> Plugin 'FEEDBACK' is disabled.
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> Unknown/unsupported storage engine: InnoDB
> >> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> Aborting
> >> jan 22 10:20:31 server systemd[1]: mariadb.service: Main process
> exited, code=exited, status=1/FAILURE
> >> jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with result
> 'exit-code'.
> >> jan 22 10:20:31 server systemd[1]: Failed to start MariaDB 10.5.18
> database server.
> >>
> >
> > The first line in the above error is indicating that your database is
> messed up so that InnoDB cannot start. Looks like you need to fix the db
> first.
> >
> I think you missed the other erorr message:
>
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> Unknown/unsupported storage
> engine: InnoDB
>
> If the db is Innodb and Innodb hasn't been installed, I could easily see
> this error happening.
>
> --
>
> Mike Perkins
>
>
> _______________________________________________
> mythtv-users mailing list
> mythtv-users@mythtv.org
> http://lists.mythtv.org/mailman/listinfo/mythtv-users
> http://wiki.mythtv.org/Mailing_List_etiquette
> MythTV Forums: https://forum.mythtv.org
>

Re: Unable to start mariadb after Debian system upgrade [ In reply to ]

mythtv at mythqml

Jan 22, 2023, 8:09 AM

Post #5 of 6 (352 views)

Permalink

On 22/01/2023 15:07, Mike Perkins wrote:

> On 22/01/2023 14:46, Jay Harbeston wrote:
>>>
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
>>> [ERROR] InnoDB: Plugin initialization aborted with error Data
>>> structure corruption
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note]
>>> InnoDB: Starting shutdown...
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
>>> [ERROR] Plugin 'InnoDB' init function returned error.
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
>>> [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [Note]
>>> Plugin 'FEEDBACK' is disabled.
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
>>> [ERROR] Unknown/unsupported storage engine: InnoDB
>>> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
>>> [ERROR] Aborting
>>> jan 22 10:20:31 server systemd[1]: mariadb.service: Main process
>>> exited, code=exited, status=1/FAILURE
>>> jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with
>>> result 'exit-code'.
>>> jan 22 10:20:31 server systemd[1]: Failed to start MariaDB 10.5.18
>>> database server.
>>>
>>
>> The first line in the above error is indicating that your database
>> is messed up so that InnoDB cannot start. Looks like you need to fix
>> the db first.
>>
> I think you missed the other erorr message:
>
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> Unknown/unsupported storage engine: InnoDB
>
> If the db is Innodb and Innodb hasn't been installed, I could easily
> see this error happening.
>

There is also this error

jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
Plugin 'InnoDB' init function returned error.

So it may be installed but failing to start?

One guess is maybe the on disk format has changed and Maria DB wants you
to run an update to fix it? Although I would have expected something in
the logs to say this is required though \0/

Paul H.

_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org

Re: Unable to start mariadb after Debian system upgrade [ In reply to ]

peter.jm.carlsson at gmail

Jan 22, 2023, 2:02 PM

Post #6 of 6 (351 views)

Permalink

On Sun, Jan 22, 2023 at 04:09:20PM +0000, Paul Harrison wrote:
> On 22/01/2023 15:07, Mike Perkins wrote:
>
> > On 22/01/2023 14:46, Jay Harbeston wrote:
> > > >
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [ERROR] InnoDB: Plugin initialization aborted with error Data
> > > > structure corruption
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [Note] InnoDB: Starting shutdown...
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [ERROR] Plugin 'InnoDB' init function returned error.
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [Note] Plugin 'FEEDBACK' is disabled.
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [ERROR] Unknown/unsupported storage engine: InnoDB
> > > > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0
> > > > [ERROR] Aborting
> > > > jan 22 10:20:31 server systemd[1]: mariadb.service: Main process
> > > > exited, code=exited, status=1/FAILURE
> > > > jan 22 10:20:31 server systemd[1]: mariadb.service: Failed with
> > > > result 'exit-code'.
> > > > jan 22 10:20:31 server systemd[1]: Failed to start MariaDB
> > > > 10.5.18 database server.
> > > >
> > >
> > > The first line in the above error is indicating that your database
> > > is messed up so that InnoDB cannot start. Looks like you need to fix
> > > the db first.
> > >
> > I think you missed the other erorr message:
> >
> > jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR]
> > Unknown/unsupported storage engine: InnoDB
> >
> > If the db is Innodb and Innodb hasn't been installed, I could easily see
> > this error happening.
> >
>
> There is also this error
>
> jan 22 10:20:31 server mariadbd[23901]: 2023-01-22 10:20:31 0 [ERROR] Plugin
> 'InnoDB' init function returned error.
>
>
> So it may be installed but failing to start?
>
>
> One guess is maybe the on disk format has changed and Maria DB wants you to
> run an update to fix it? Although I would have expected something in the
> logs to say this is required though \0/

I have tried to reinstall the following all packages but it is the same
error.

server:~# apt list --installed | grep mariadb

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

libmariadb-dev/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
libmariadb3/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
libmariadbd-dev/stable,now 1:10.5.18-0+deb11u1 i386 [installerat]
libmariadbd19/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
mariadb-client-10.5/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
mariadb-client-core-10.5/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
mariadb-client/stable,stable,now 1:10.5.18-0+deb11u1 all [installerat]
mariadb-common/stable,stable,now 1:10.5.18-0+deb11u1 all [installerat,automatiskt]
mariadb-server-10.5/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
mariadb-server-core-10.5/stable,now 1:10.5.18-0+deb11u1 i386 [installerat,automatiskt]
mariadb-server/stable,stable,now 1:10.5.18-0+deb11u1 all [installerat]

I have a backup of all database files and I can see that there have been
changes to some. Maybe I should restore the backup and then reinstalling
mariadb.

/Peter
_______________________________________________
mythtv-users mailing list
mythtv-users@mythtv.org
http://lists.mythtv.org/mailman/listinfo/mythtv-users
http://wiki.mythtv.org/Mailing_List_etiquette
MythTV Forums: https://forum.mythtv.org