[Support] Linuxserver.io - MariaDB

[scubieman]

Need help resetting the MYSQL_ROOT_PASSWORD i have tried to follow turtiols and nothing. https://www.digitalocean.com/community/tutorials/how-to-reset-your-mysql-or-mariadb-root-password

 

I show on the page that i can use files with ENV variables? Not sure what that means. 

[Der_Eine]

Hi!

I am using this MariaDB Docker with Photoprism. I just faced the following error messages:

2023-05-25 00:15:40 ERRO photo: Error 1366: Incorrect string value: '\xD9\x85\xD8\xB9\xD8\xA8...' for column `photoprism`.`cells`.`cell_name` at row 1 (find location)

2023-05-25 00:15:40 ERRO cell: record not found (find s2:143662db2c8c)

2023-05-25 00:15:40 ERRO cell: Error 1366: Incorrect string value: '\xD9\x85\xD8\xB9\xD8\xA8...' for column `photoprism`.`cells`.`cell_name` at row 1 (create s2:143662db2c8c)

2023-05-25 00:15:40 ERRO cell: Error 1366: Incorrect string value: '\xD9\x82\xD8\xB1\xD9\x8A...' for column `photoprism`.`places`.`place_city` at row 1 while creating place eg:Rh1HvnaYJdpT

 

This repeates very very often. I read that this has something to do with UTF-8 support. Can someone please help me how I can fix this?

 

PS: I took this screenshot of the Database.

[Fredrick]

On 7/18/2022 at 5:51 AM, cenzar said:

Hello, randomly out of the blue I was no longer able to log in to mariadb with root via adminer. I tried with phpmyadmin and via the terminal and also no luck. I also tried to edit the root password on the edit page of the docker container but no luck. Here is the exact error: 

ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: YES)

It would appear normal connections still work. I'm running 2 instances of photoprism and they are running with no issues and connecting to mariadb. I found online there is a way to skip grant tables, flush privileges, and create a new login but I couldn't find a way to do it for lscr.io/linuxserver/mariadb. Is there anyway I can fix this?

 

Did you ever fix this ? I'm having the same issue on my installation. It works with Nextcloud, but I cant access either nextcloud or root account in commandline/adminer.

[elmuziko]

Having problems with MariaDB too. I too clicked upgrade just this Saturday past, and now Kodi won't start.

 

In the logs, I get this, every second or two.

 

Any ideas? I can't log in any more via phpmyadmin or through the console. Definitely know the root password.

 

Quote

230530 14:08:43 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
230530 14:08:44 mysqld_safe Logging to '/config/databases/bc1b4b81309e.err'.
230530 14:08:44 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
230530 14:08:46 mysqld_safe Logging to '/config/databases/bc1b4b81309e.err'.
230530 14:08:46 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
230530 14:08:48 mysqld_safe Logging to '/config/databases/bc1b4b81309e.err'.
230530 14:08:48 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
230530 14:08:49 mysqld_safe Logging to '/config/databases/bc1b4b81309e.err'.
230530 14:08:49 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
230530 14:08:51 mysqld_safe Logging to '/config/databases/bc1b4b81309e.err'.
230530 14:08:51 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!

 

 

[Martintheshred]

On 5/30/2023 at 10:02 PM, elmuziko said:

Having problems with MariaDB too. I too clicked upgrade just this Saturday past, and now Kodi won't start.

 

In the logs, I get this, every second or two.

 

Any ideas? I can't log in any more via phpmyadmin or through the console. Definitely know the root password.

 

 

Just did the Mariadb upgrade and getting the same issue and my Nextcloud will not work looking in my MariaDB Logs and keep getting the same recurring Issue

[silentbob]

10 hours ago, Martintheshred said:

Just did the Mariadb upgrade and getting the same issue and my Nextcloud will not work looking in my MariaDB Logs and keep getting the same recurring Issue

Having a similar issue after updating. Changing the docker repositry to linuxserver/mariadb:10.6.13 gets things running again.

 

230601 01:17:37 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2023-06-01  1:17:37 0 [Note] Starting MariaDB 10.11.3-MariaDB-log source revision 0bb31039f54bd6a0dc8f0fc7d40e6b58a51998b0 as process 5244
2023-06-01  1:17:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-06-01  1:17:37 0 [Note] InnoDB: Number of transaction pools: 1
2023-06-01  1:17:37 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-06-01  1:17:37 0 [Note] InnoDB: Using Linux native AIO
2023-06-01  1:17:37 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000MiB, chunk size = 4.000MiB
2023-06-01  1:17:37 0 [Note] InnoDB: Completed initialization of buffer pool
2023-06-01  1:17:37 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2023-06-01  1:17:37 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.
2023-06-01  1:17:37 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2023-06-01  1:17:37 0 [Note] InnoDB: Starting shutdown...
2023-06-01  1:17:38 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-06-01  1:17:38 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-06-01  1:17:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-01  1:17:38 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-06-01  1:17:38 0 [ERROR] Aborting
230601 01:17:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

 

Edited June 1, 2023 by silentbob

[elmuziko]

6 hours ago, silentbob said:

Having a similar issue after updating. Changing the docker repositry to linuxserver/mariadb:10.6.13 gets thins running again.

 

230601 01:17:37 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2023-06-01  1:17:37 0 [Note] Starting MariaDB 10.11.3-MariaDB-log source revision 0bb31039f54bd6a0dc8f0fc7d40e6b58a51998b0 as process 5244
2023-06-01  1:17:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-06-01  1:17:37 0 [Note] InnoDB: Number of transaction pools: 1
2023-06-01  1:17:37 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-06-01  1:17:37 0 [Note] InnoDB: Using Linux native AIO
2023-06-01  1:17:37 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000MiB, chunk size = 4.000MiB
2023-06-01  1:17:37 0 [Note] InnoDB: Completed initialization of buffer pool
2023-06-01  1:17:37 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2023-06-01  1:17:37 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.
2023-06-01  1:17:37 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2023-06-01  1:17:37 0 [Note] InnoDB: Starting shutdown...
2023-06-01  1:17:38 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-06-01  1:17:38 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-06-01  1:17:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-01  1:17:38 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-06-01  1:17:38 0 [ERROR] Aborting
230601 01:17:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

 

 

 

 

Maaaaaaaaaate. 

My hero. Switching it back to 10.6.13 worked for me. Everything back up like nothing happened. Worst week ever and you smash it out of the park. Thank you.

[Martintheshred]

7 hours ago, silentbob said:

Having a similar issue after updating. Changing the docker repositry to linuxserver/mariadb:10.6.13 gets thins running again.

 

230601 01:17:37 mysqld_safe Starting mariadbd daemon with databases from /config/databases
2023-06-01  1:17:37 0 [Note] Starting MariaDB 10.11.3-MariaDB-log source revision 0bb31039f54bd6a0dc8f0fc7d40e6b58a51998b0 as process 5244
2023-06-01  1:17:37 0 [Note] InnoDB: Compressed tables use zlib 1.2.13
2023-06-01  1:17:37 0 [Note] InnoDB: Number of transaction pools: 1
2023-06-01  1:17:37 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2023-06-01  1:17:37 0 [Note] InnoDB: Using Linux native AIO
2023-06-01  1:17:37 0 [Note] InnoDB: Initializing buffer pool, total size = 256.000MiB, chunk size = 4.000MiB
2023-06-01  1:17:37 0 [Note] InnoDB: Completed initialization of buffer pool
2023-06-01  1:17:37 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2023-06-01  1:17:37 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.12. You must start up and shut down MariaDB 10.7 or earlier.
2023-06-01  1:17:37 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2023-06-01  1:17:37 0 [Note] InnoDB: Starting shutdown...
2023-06-01  1:17:38 0 [ERROR] Plugin 'InnoDB' init function returned error.
2023-06-01  1:17:38 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2023-06-01  1:17:38 0 [Note] Plugin 'FEEDBACK' is disabled.
2023-06-01  1:17:38 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2023-06-01  1:17:38 0 [ERROR] Aborting
230601 01:17:38 mysqld_safe mysqld from pid file /var/run/mysqld/mysqld.pid ended

 

Thanks for this Silentbob this is probably a stupid newbie question how do I do that?
Do I just open up the Unraid template and change it there?

 

  

[elmuziko]

1 minute ago, Martintheshred said:

Thanks for this Silentbob this is probably a stupid newbie question how do I do that?
Do I just open up the Unraid template and change it there?

 

I know you didn't ask me but on the offchance Silentbob is in the US and asleep for 12 hours, here's the answer.

Forgive me for using Emby as my example. Different unraid box but the fix is exactly the same.

 

 

[Martintheshred]

3 minutes ago, Martintheshred said:

Thanks for this Silentbob this is probably a stupid newbie question how do I do that?
Do I just open up the Unraid template and change it there?

 

  

It was a stupid Question Thanks Silentbob all I had to do was open up the template and type linuxserver/mariadb:10.6.13 into the repository section and it work. just need to remember that for nexttime 

[Martintheshred]

3 minutes ago, elmuziko said:

 

I know you didn't ask me but on the offchance Silentbob is in the US and asleep for 12 hours, here's the answer.

Forgive me for using Emby as my example. Different unraid box but the fix is exactly the same.

 

 

Cheers for this Elmuziko thats what I did on the off chance that well if its broken I cannot make it any worse (LOL) and change it to this below I was just reply but you beet me to it hope they get the update sorted though 

[elmuziko]

1 minute ago, Martintheshred said:

Cheers for this Elmuziko thats what I did on the off chance that well if its broken I cannot make it any worse (LOL) and change it to this below I was just reply but you beet me to it hope they get the update sorted though 

Like you, my friend, I've made a mental note on how to fix this (and any other docker issues) in the future. Rollback! ha!

[silentbob]

After rolling back, I can see this in the logs 

 

mariadb-upgrade -u root -p<PASSWORD>

 

I had to run it twice, not sure if this is the reason the update broke my system.

Edited June 1, 2023 by silentbob

[Joshwaaa]

I am continually getting this error in the log in mariadb

cat: /var/run/mysqld/mysqld.pid: No such file or directory
230606 18:04:03 mysqld_safe Logging to '/config/databases/66cb7795ae82.err'.
230606 18:04:03 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!

Anyone know what this is or how to fix it? Every search I do turns up nothing at all.

[Joshwaaa]

On 8/13/2017 at 9:50 AM, CHBMB said:

OK, so if you're finding the container not starting up and seeing this in the logs repeatedly, (the cause I believe is an unclean shutdown of the container)

 

170801 17:54:53 mysqld_safe Logging to syslog.
170801 17:54:53 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:54:56 mysqld_safe Logging to syslog.
170801 17:54:56 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:00 mysqld_safe Logging to syslog.
170801 17:55:00 mysqld_safe Starting mysqld daemon with databases from /config/databases
170801 17:55:03 mysqld_safe Logging to syslog.
170801 17:55:03 mysqld_safe Starting mysqld daemon with databases from /config/databases

There are two ways to remedy this.  Firstly and my preferred method, is to restore from a backup.  Secondly you can try this by opening a terminal on your Unraid server.

 

docker exec -it mariadb bash
mv /config/log/ /config/log-old/
exit
docker restart mariadb

I can't promise this second method won't result in some loss of data but it may get you out of a fix.

@CHBMB I am continually getting the same error

cat: /var/run/mysqld/mysqld.pid: No such file or directory
230606 18:23:41 mysqld_safe Logging to '/config/databases/66cb7795ae82.err'.
230606 18:23:41 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!

 

I can't seem to find any info on the .err  I see you told someone that if they reinstalled mariadb that their nextcloud files should be intact? I just want to make sure before I go that route. Will the data from different accounts all be preserved? 

[guyola]

Hello
My Mariadb with a lot of data has stopped working.
The log shows this:

230616 15:27:19 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:19 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:21 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:21 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:23 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:23 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:25 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:25 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:27 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:27 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:29 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:29 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:31 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:31 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:33 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:33 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:35 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:35 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
UMASK corrected from 022 to 0640 ...
230616 15:27:37 mysqld_safe Logging to '/config/databases/d6aa3db4b812.err'.
230616 15:27:37 mysqld_safe Starting mariadbd daemon with databases from /config/databases
Caught SIGTERM signal!
 

When I turn on the docker of mariadb the log shows this ina indefinte loop!!!

 

Does anyone knows how to resolve this?

Is there a guide to reinstall mariadb an keep the databases?

 

Thanks

[Joshwaaa]

@guyola I posted the same thing on June 6. No one has responded to it at all. I hope you find help. I'm going to start over but preserve anything I can. Hope you find help!

[Joshwaaa]

I created a cache pool but pulled a disc out of order which deleted my dockers. I then mistakenly re-added them from apps thus downloading the latest version. I should have immediately done docker system df -v or docker inspect mariadb and got my exact version I last used. Should have done the same with nextcloud. I have tried pulling from the repositories, tried deleting images and templates. Nothing has worked. I am trying now to just preserve the nextcloud database in mariadb. I'd like to start fresh but preserve the data that is still in the old mariadb. I have 3 questions:

Could or should I copy this nextcloud folder somewhere and delete everything else?

Is there any other place to delete files that may contain files that could corrupt a new download?

If I am able to copy and then move the nextcloud database back into mariadb will it preserve the users and their data I setup? I had 2 other users using it.

Thanks!

 

[SRB]

I was getting upload errors to Nextcloud, consistent with what everyone is reporting here. Unclear if it was the update to MariaDB, Unraid 6.12 or the combination of the both that broke everything. Either way, I was able to fix everything through the following steps.

 

1. Update MariaDB to the latest docker version. Check the docker log, and if you see the message @silentbob noted, perform the upgrade.

 

On 6/1/2023 at 4:51 AM, silentbob said:

After rolling back, I can see this in the logs 

 

mariadb-upgrade -u root -p<PASSWORD>

 

I had to run it twice, not sure if this is the reason the update broke my system.

 

2. Restart MariaDB and Nextcloud dockers. Try to upload a document to Nextcloud. In my case all uploads were failing (both through browser and desktop client). My Nextcloud log (which you can check at Administration setting > Logging on your Nextcloud site) was filled with

 

Doctrine\DBAL\Exception\DriverException: An exception occurred while executing a query: SQLSTATE[HY000]: General error: 1034 Index for table 'oc_filecache' is corrupt; try to repair it

 

so I figured I needed to repair the oc_filecache table in my MariaDB nextcloud database.

 

3. Stop the Nextcloud docker or put it into maintenance (unsure which is best practice, maybe some from the LS team can chime in)

 

docker exec -it nextcloud occ maintenance:mode --on

 

4. Access your MariaDB container's console and truncate your oc_filecache table. Be careful, there is no heading back from this. I believe you will lose all file shares and labels (metadata type stuff).

 

docker exec -it mariadb bash
mysql -u root -p<ROOTPASSWORD>
USE <NEXTCLOUDDB>;
TRUNCATE TABLE oc_filecache;

 

5. Restart your Nextcloud docker or take it out of maintenance mode

 

docker exec -it nextcloud occ maintenance:mode --off

 

6. Run the occ files:scan command to rebuild your file cahce. This could take a while (especially if you have a big install). The webgui may be unresponsive, just let it run and everything should eventually come back.

 

docker exec -it nextcloud occ files:scan --all -vvv

Edited June 21, 2023 by SRB

[jademonkee]

Hi there,

I remember after this image was rebased to Apline that my start up log (the one accessed when clicking on the mariadb icon in the Unraid Docker UI) started producing the following each time it started:

[custom-init] No custom files found, skipping...
230720 11:04:18 mysqld_safe Logging to '/config/databases/98d77ae0f2c7.err'.
230720 11:04:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases
[ls.io-init] done

Everything seemed to work correctly, so I didn't really think much about that mention of a .err file.

Fast forward a couple years (maybe?), and I just realised that my mariadb appdata directory is about 4GB in size, while my db backups are only about 80MB. I was worried that the backups weren't running correctly, so started digging around in the 'db-backup' Docker that I use to back it up. I couldn't find anything in the logs.

Long story short, I have just under 4GB of .err files in the mariadb appdata directory.

Opening up the .err file that is referenced in the above log, I see that it's constantly filling with:

2023-07-20 13:43:56 362 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2023-07-20 13:43:56 362 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).

Over and over and over again.

How do I fix this?

The only app I use mariadb for is Nextcloud, which I also use the LSIO Docker for.

Thanks for your help.

[jademonkee]

21 hours ago, jademonkee said:

Hi there,

I remember after this image was rebased to Apline that my start up log (the one accessed when clicking on the mariadb icon in the Unraid Docker UI) started producing the following each time it started:

[custom-init] No custom files found, skipping...
230720 11:04:18 mysqld_safe Logging to '/config/databases/98d77ae0f2c7.err'.
230720 11:04:18 mysqld_safe Starting mariadbd daemon with databases from /config/databases
[ls.io-init] done

Everything seemed to work correctly, so I didn't really think much about that mention of a .err file.

Fast forward a couple years (maybe?), and I just realised that my mariadb appdata directory is about 4GB in size, while my db backups are only about 80MB. I was worried that the backups weren't running correctly, so started digging around in the 'db-backup' Docker that I use to back it up. I couldn't find anything in the logs.

Long story short, I have just under 4GB of .err files in the mariadb appdata directory.

Opening up the .err file that is referenced in the above log, I see that it's constantly filling with:

2023-07-20 13:43:56 362 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'hist_type' at position 9 to have type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB','JSON_HB'), found type enum('SINGLE_PREC_HB','DOUBLE_PREC_HB').
2023-07-20 13:43:56 362 [ERROR] Incorrect definition of table mysql.column_stats: expected column 'histogram' at position 10 to have type longblob, found type varbinary(255).

Over and over and over again.

How do I fix this?

The only app I use mariadb for is Nextcloud, which I also use the LSIO Docker for.

Thanks for your help.

I Googled the error this morning and it seems to be a problem from a poor upgrade between mariadb versions (ie the container updated the version, but there were manual steps needed inside the container that I was not aware of).

This thread shed some light on it:

https://github.com/photoprism/photoprism/issues/2382

Specifically, I ran the following command, and now the error isn't constantly spamming the .err logfiles.

mysql_upgrade --user=root --password=<root_pwd>

Does anyone know if I can just delete all the .err files from the folder now?

[jademonkee]

2 hours ago, jademonkee said:

Does anyone know if I can just delete all the .err files from the folder now?

FWIW, I copied all the .err files to a new directory (just in case), I then deleted all of them except the one listed in the logs at start-up.

I then renamed the active log file to <filename>.err.old

I then logged into the mysql console by opening the mariadb console via the Unraid GUI, then issuing the command:

mysql -uroot -p

As per https://mariadb.com/kb/en/flush/, I then issued the command to close and reopen the .err file (basically recreate it)

flush error logs;

Now the .err file is KB in size, and I have recovered 3GB of space on the cache drive by clearing the errors that have been accumulating for a couple years now.

Fingers crossed I haven't messed anything up!

[showstopper]

I am getting some very strange results trying a fresh MariaDB and NextCloud install. Everything seems to work until the nextcloud install. I check the mariadb logs and I can no longer log into the database and the log keeps getting filled with *.err files. I have tried maybe 4 times with the same result each time. I am now going to try a fresh install with the official docker versions.

[Killabee44]

Hi all,

 

I recently lost all of my containers and had to reinstall them (long story) but now mariadb isn't working and I don't have a .sock file either. I do see my databases in the app folder though.

I am getting the following error:

 

ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)

 

 Thanks!

 

[DrSiva2022]

I stopped all services , restarted mariadb , even went to older version as mentioned , still its outputting this ins log.

 

Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
UMASK must be a 3-digit mode with an additional leading 0 to indicate octal.
The first digit will be corrected to 6, the others may be 0, 2, 4, or 6.
UMASK corrected from 022 to 0640 ...
230809 22:46:55 mysqld_safe Logging to '/config/databases/f4e153d31abe.err'.
230809 22:46:55 mysqld_safe Starting mariadbd daemon with databases from /config/databases

 

last time it was nextcloud update which screwed and it was down for long time since i didnt time to fix , now mariadb.

Why is even simple updates are causing such a huge headache ?