[Support] Linuxserver.io - MariaDB

[exico]

21 minutes ago, sonic6 said:

So,... i updated the container a few minutes ago... and now i got this:

 

 

Some ideas, how i can solve this?

Yeah. mine too. I was wondering why one of the services just died and i checked the db connection...

Not sure why it worked but i changed the repo from linuxserver/mariadb to linuxserver/mariadb:alpine-version-10.5.12-r0 (an older version) and then changed it to linuxserver/mariadb:latest and works. Not ideal i know but works.

 

Logs for the error points to a fail in innodb

210825 18:56:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Warning: World-writable config file '/etc/my.cnf.d/custom.cnf' is ignored
2021-08-25 18:56:18 0 [Note] /usr/bin/mariadbd (mysqld 10.5.12-MariaDB) starting as process 4703 ...
2021-08-25 18:56:18 0 [Note] InnoDB: Uses event mutexes
2021-08-25 18:56:18 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2021-08-25 18:56:18 0 [Note] InnoDB: Number of pools: 1
2021-08-25 18:56:18 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2021-08-25 18:56:18 0 [Note] mariadbd: O_TMPFILE is not supported on /var/tmp (disabling future attempts)
2021-08-25 18:56:18 0 [Note] InnoDB: Using Linux native AIO
2021-08-25 18:56:18 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2021-08-25 18:56:18 0 [Note] InnoDB: Completed initialization of buffer pool
2021-08-25 18:56:18 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.21.
2021-08-25 18:56:18 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2021-08-25 18:56:18 0 [Note] InnoDB: Starting shutdown...
2021-08-25 18:56:18 0 [ERROR] Plugin 'InnoDB' init function returned error.
2021-08-25 18:56:18 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2021-08-25 18:56:18 0 [Note] Plugin 'FEEDBACK' is disabled.
2021-08-25 18:56:18 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2021-08-25 18:56:18 0 [ERROR] Aborting
210825 18:56:18 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

 

Edited August 25, 2021 by exico

[sonic6]

@exico

here is my workaround,

 

try using this

Repository: linuxserver/mariadb:110.4.21mariabionic-ls31

[ich777]

How do I migrate to the alpine image:

******************************************************
******************************************************
* *
* *
* This image will soon be rebased *
* from ubuntu to alpine. *
* Please be aware, this may cause issues *
* It is strongly recommended to make backups *
* of your config and databases before *
* updating your image to the alpine base. *
* *
* *
******************************************************
******************************************************

 

[goosetrousers]

7 hours ago, sonic6 said:

Repository: linuxserver/mariadb:110.4.21mariabionic-ls31

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

[Simmer]

2 hours ago, goosetrousers said:

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

This worked for me as well.

[jademonkee]

I updated this morning and have this in the logs:

Quote

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 40-initialise-db: executing...
[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
210826 10:05:52 mysqld_safe Logging to '/config/databases/98571c4a56a9.err'.
210826 10:05:52 mysqld_safe Starting mariadbd daemon with databases from /config/databases

It's not adding any extra lines (like, they're not repeating), and Swag + NextCloud are working fine (the only things that use it - and I don't even remeber if they both do, or just NC... heh)). Is that safe mode anything to worry about? Or is it all good?

[jimmy898]

8 hours ago, goosetrousers said:

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

 

This worked for me too. 

 

7 minutes ago, jademonkee said:

I updated this morning and have this in the logs:

It's not adding any extra lines (like, they're not repeating), and Swag + NextCloud are working fine (the only things that use it - and I don't even remeber if they both do, or just NC... heh)). Is that safe mode anything to worry about? Or is it all good?

 

After the "fix" I have the same logs:

 

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing...
[cont-init.d] 30-config: exited 0.
[cont-init.d] 40-initialise-db: executing...
[cont-init.d] 40-initialise-db: exited 0.
[cont-init.d] 90-custom-folders: executing...
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
210826 10:27:08 mysqld_safe Logging to '/config/databases/1e9a6a6ee3d8.err'.
210826 10:27:08 mysqld_safe Starting mariadbd daemon with databases from /config/databases

 

[j0nnymoe]

18 hours ago, sonic6 said:

@exico

here is my workaround,

 

try using this

Repository: linuxserver/mariadb:110.4.21mariabionic-ls31

Be aware that this will no longer get updates.

[j0nnymoe]

17 hours ago, ich777 said:

How do I migrate to the alpine image:

******************************************************
******************************************************
* *
* *
* This image will soon be rebased *
* from ubuntu to alpine. *
* Please be aware, this may cause issues *
* It is strongly recommended to make backups *
* of your config and databases before *
* updating your image to the alpine base. *
* *
* *
******************************************************
******************************************************

 

Upgrading to `:latest` will put you on alpine.

[j0nnymoe]

On 8/23/2021 at 5:55 PM, Tucubanito07 said:

When ever the tag gets update to ALPINE = LATEST, what will happen to the application if we update it then? Will it corrupt the database or would we have to do something before we update to make sure it does not corrupt the databases or mess up anything when updating? Also, why are you guys going to Alpine? What's the benefits?

Less so benefits for unraid users (x86_64) but better for our armhf / aarch64 users as mariadb don't release up to date versions for those platforms on ubuntu base.

[ich777]

45 minutes ago, j0nnymoe said:

Upgrading to `:latest` will put you on alpine.

Only asking because I got the same issue while upgrading to latest as @sonic6.

 

A downgrade to: 'linuxserver/mariadb:110.4.21mariabionic-ls31' and upgrade after the downgrade solved the issue, everything is now up and running on alpine.

[fithwum]

still getting the error after update and fix but at least it works again

[Tucubanito07]

7 hours ago, j0nnymoe said:

Less so benefits for unraid users (x86_64) but better for our armhf / aarch64 users as mariadb don't release up to date versions for those platforms on ubuntu base.

When we update the container to the latest? Will it break anything on the database? If you know. Any recommendations on updating it so it does not mess up any of the databases we have already working. 

[nekromantik]

same here

[Froberg]

"Fix" worked for me, at least I can access the db through phpmyadmin again. Nextcloud is still b0rked though. Have to get some rest, but specifically the fix that worked in my case: 

 

And then switching to :latest. 

[nekromantik]

not really a fix if nextcloud breaks 

[dougiefresh]

22 hours ago, goosetrousers said:

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

Worked for me.  

[Roxedus]

This "fix", is needed because the container gets forcefully shut down, before mariadb has successfully shutdown, this is usually isn't a problem, as mariadb is nice, and usually manages to recover from a dirty shutdown.  The docker update plugin uses 10s as the default time before killing a container, which does not suffice. 

[Froberg]

15 hours ago, nekromantik said:

not really a fix if nextcloud breaks 

Agreed.. been unsuccesful thus far in reviving it.. 502 Bad Gateway. 

The DB is up, as I could upgrade it through console, which I assume required DB connectivity.. so I'm a bit stumped atm. 

[thunderclap]

16 hours ago, nekromantik said:

not really a fix if nextcloud breaks 

 

16 hours ago, Froberg said:

"Fix" worked for me, at least I can access the db through phpmyadmin again. Nextcloud is still b0rked though. Have to get some rest, but specifically the fix that worked in my case: 

 

And then switching to :latest. 

 

16 hours ago, nekromantik said:

not really a fix if nextcloud breaks 

 

This fix worked for me. 

Nextcloud is back up and running without issue.

 

[uByte]

On 8/25/2021 at 1:30 PM, sonic6 said:

@exico

here is my workaround,

 

try using this

Repository: linuxserver/mariadb:110.4.21mariabionic-ls31

I had the same issue and this is what fixed it for me. Thank you @sonic6

[Bob Junks]

If you are getting the following error in the logs 

 

"Unknown/unsupported storage engine: InnoDB"

 

Then doing this resolved may resolve your issue.  It resolved mine.  I updated mariadb and then nextcloud.

 

For the future.  Before upgrading mariadb, stop the next cloud docker container, then stop mariadb container.  Then apply updates.  

 

Basically I opened a console on the mariadb docker.  

 

ran the following commands

 

> cd /config/databases

> rm ib_logfile0

> rm ib_logfile1 (note: You may get "rm : Cannot remove 'ib_logfile1': No such file or directory) on this command

 

Then stop both the containers and restart both the containers

This seemed to have resolved my issue.

 

Credit where it's due: https://serverfault.com/questions/379714/unknown-unsupported-storage-engine-innodb-mysql-ubuntu

 

[tvd1]

On 8/25/2021 at 8:36 PM, goosetrousers said:

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

+1. same exact issue for me and this worked too. Thanks!

[HaOz Ong]

On 8/26/2021 at 8:36 AM, goosetrousers said:

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

this worked for me as well. both mariadb service and nextcloud up and running again. thanks !!

[dellorianes]

On 8/26/2021 at 2:36 AM, goosetrousers said:

I did this, everything worked again. Then I updated to 

linuxserver/mariadb:latest

and everything continued to work, but with an Alpine base. Saved me from migrating, I guess I'll sit on my backups and see how this plays out.

It has also worked for me. Thank you very much