[Support] MariaDB Official

[mgutt]

23 minutes ago, 4n0nyM said:

Found the mariadb.cnf file, but don't know how to edit it

Don't need to. Instead you create a new cnf file:

https://forums.unraid.net/topic/110019-support-mariadb-official/?do=findComment&comment=1024598

 

 

Note this post:

https://forums.unraid.net/topic/110019-support-mariadb-official/?do=findComment&comment=1039530

 

 

 

[4n0nyM]

1 hour ago, mgutt said:

I don't know if it's active by default, but try to disable binary logging:

https://geekflare.com/disable-binary-log-mariadb/

Wow, thank you so much 😊.
That actually solved the problem. I completely re-downloaded the data from Nextcloud on my PC and I didn't get the error once. The loading bar has always remained nice and green.

[srepper]

On 8/16/2021 at 1:24 PM, mgutt said:

 

Create the file "nextcloud.cnf" in the folder "/mnt/user/appdata/mariadb-official/config" with the following content:

[mysqld]
innodb_read_only_compressed = "OFF"

 

Tried it, but on Adminer I got the error if I upload my backup.sql.

 

[mgutt]

25 minutes ago, srepper said:

Tried it, but on Adminer I got the error if I upload my backup.sql.

Did you restart the container?

 

PS there is an easier method available. Add this to the post arguments:

--skip-innodb-read-only-compressed

 

Or add :10.5 to the repo name like this:

mariadb:10.5

 

By that the container does not update to an incompatible version.

[srepper]

16 minutes ago, mgutt said:

Did you restart the container?

 

 

yes

 

16 minutes ago, mgutt said:

 

 

PS there is an easier method available. Add this to the post arguments:

--skip-innodb-read-only-compressed

where can I add this post argument ?

 

 

16 minutes ago, mgutt said:

Or add :10.5 to the repo name like this:

mariadb:10.5

 

By that the container does not update to an incompatible version.

the last step right ?

better is to have the newest version, for the full protection.

 

 

Edit: thank you, mate

 

Edited December 4, 2021 by srepper

[CaptainTivo]

Hi,

Not sure if this is right place to ask this, if not, please tell me where 🙂

So, I have been running the Kodi/Xbmc database on the Mariadb docker on Unraid since version 6 dropped.  I have both PC (Windows) and Android (Fire TV) clients that use the database to find movies and TV.  This all worked fine until I updated Mariadb in December.  Instantly, the Android clients now show "unknown error" to queries in their logs. The PC clients still worked fine. 

Here is a fragment of the Kodi log file:

2022-02-19 13:25:22.154 T:7641  NOTICE: Running database version Addons27
2022-02-19 13:25:23.029 T:7641  NOTICE: Running database version ViewModes6
2022-02-19 13:25:23.568 T:7641  NOTICE: Running database version Textures13
2022-02-19 13:25:23.614 T:7641  NOTICE: MYSQL: Connected to version 10.5.13-MariaDB-log
2022-02-19 13:25:23.627 T:7641   ERROR: SQL: [MyMusic72] An unknown error occurred
                                            Query: SELECT idVersion FROM version

I asked the Kodi people and did not get much help.  I don't understand why the Kodi apps on the PCs don't get errors and the Android apps do.

So I thought I would just try to install an older version of Mariadb on Unraid and see if that fixed the problem.

I did a bit of searching but I have yet to find a recipe for finding the older version and then installing it on unRaid.

 

Any help is much appreciated.

 

[mgutt]

9 hours ago, CaptainTivo said:

try to install an older version of Mariadb on Unraid and see if that fixed the problem.

This will solve it. See here:

https://forum.kodi.tv/showthread.php?tid=364255&pid=3057766#pid3057766

 

But I think it's the same bug as with Nextcloud. So simply add this to the Post Arguments (visible through advanced view) of the maria db Container:

--skip-innodb-read-only-compressed

 

 

 

[CaptainTivo]

8 hours ago, mgutt said:

This will solve it. See here:

https://forum.kodi.tv/showthread.php?tid=364255&pid=3057766#pid3057766

 

But I think it's the same bug as with Nextcloud. So simply add this to the Post Arguments (visible through advanced view) of the maria db Container:

--skip-innodb-read-only-compressed

 

Mgut, thanks for your reply.

Here is what I did.

1. I stopped the mariadb application.

2. Clicked on the icon and selected "Edit"

3. Clicked "basic View" to select "Advanced View"

4. pasted "--skip-innodb-read-only-compressed" into the "Post Arguments" field.

5. Click the "Apply" button 

This takes me to the "Update Container" page which has this message:

Removing container: mariadb
Successfully removed container 'mariadb'
Command:
root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='mariadb' --net='bridge' -e TZ="America/Chicago" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'MYSQL_ROOT_PASSWORD'='hunter' -p '3306:3306/tcp' -v '/mnt/user/appdata/mariadb':'/config':'rw' 'linuxserver/mariadb' --skip-innodb-read-only-compressed
fbb8d5298685a6cf20a0ae12c1bac659abb34288f1777e0296e110b3aa1b184a

The command finished successfully!

6. clicked the "Done' button. which takes me back to the "Docker Containers" page

7. clicked the mariadb icon and selected "Start"

Unfortunately, this did not work.  In fact, the Kodi app on my PC now hangs.   Here is the log file:

 

2022-02-20 10:11:50.823 T:58056  NOTICE: Running database version Addons27
2022-02-20 10:11:50.824 T:58056  NOTICE: Running database version ViewModes6
2022-02-20 10:11:50.824 T:58056  NOTICE: Running database version Textures13
2022-02-20 10:11:52.863 T:58056   ERROR: Unable to open database: MyMusic72 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:11:54.906 T:58056   ERROR: Unable to open database: MyMusic71 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:11:56.936 T:58056   ERROR: Unable to open database: MyMusic70 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:11:58.965 T:58056   ERROR: Unable to open database: MyMusic69 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:12:01.007 T:58056   ERROR: Unable to open database: MyMusic68 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:12:03.050 T:58056   ERROR: Unable to open database: MyMusic67 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:12:05.091 T:58056   ERROR: Unable to open database: MyMusic66 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))
2022-02-20 10:12:07.133 T:58056   ERROR: Unable to open database: MyMusic65 [2002](Can't connect to MySQL server on '192.168.1.3' (10061))

This would seem to indicate that the database server is not running, but the Unraid page shows that it is.

I then clicked the mariadb icon and selected "Logs".  Here are the last lines from that log:

[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.
ifelse: fatal: unable to exec --skip-innodb-read-only-compressed: No such file or directory
[cmd] --skip-innodb-read-only-compressed exited 127
Caught SIGTERM signal!
cat: /var/run/mysqld/mysqld.pid: No such file or directory
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
220220 10:21:35 mysqld_safe Logging to '/config/databases/fbb8d5298685.err'.
220220 10:21:35 mysqld_safe Starting mariadbd daemon with databases from /config/databases
[s6-finish] sending all processes the TERM signal.
[s6-finish] sending all processes the KILL signal and exiting.

 

the line

"ifelse: fatal: unable to exec --skip-innodb-read-only-compressed: No such file or directory:"

Does this mean I did not add the option to the correct box (Post Arguments) field?  It seems like the "docker create" command does not see it as an option. 

Also, weirdly, when I select "Stop" from the mariadb icon, an error box pops up with a large circle with and X in it and the message

"Execution Error  Container already started"  What does that mean? 

 

Anyway, I clicked "OK", went back and deleted the option line "--skip-innodb-read-only-compressed" and restarted the docker and the Kodi app on the PC works again.

 

As you can see, I am no expert on dockers nor on database managers.  I read the post on the Kodi forum that you referred to and did not really understand it.

 

The original poster wrote:

Quote

"I recently moved the MariaDB docker container to a different host. When starting it it possibly pulled a newer version. I tried running the command but that didn't help.
I then spun up a new container, copied over the databases and the messages stopped occurring. The Android versions of Kodi then also worked again.
So, thank you very much for the hint!"

 

His original problem is also not the same as mine.  He says:

 

Quote

the other day I noticed Kodi on my Android TV has updated to 19.1 so I updated the installation on my FireTV Stick 4K as well and now I'm encountering a strange issue on both devices. They fail to use my MariaDB Server for video and music databases and output these messages:
 

This indicates that his Android TV updated itself to a newer version of Kodi.  I don't know of any way this can happen.  You have to sideload Kodi to get it run on Android and this is a manual operation.  The messages in the log file are the same ones that I get.  Kodi does not seem to be able to connect to the database server.

I also don't understand his solution:

Quote

I recently moved the MariaDB docker container to a different host. When starting it it possibly pulled a newer version. I tried running the command but that didn't help.
 

So he thinks that mariadb was somehow updated to a new version.

Quote

I then spun up a new container, copied over the databases and the messages stopped occurring. The Android versions of Kodi then also worked again.
So, thank you very much for the hint!

This seems to indicate that an update to mariadb caused the problem and that he reverted to an earlier version and that solved the problem.  Unclear.

If so, then I guess I still need to find a way to revert to an earlier version of mariadb.

 

Again, thanks for any help you can give.

 

 

 

 

 

 

 

[mgutt]

You are not using the official MariaDB Container. Ask linuxserver for support regarding their container.

[CaptainTivo]

1 hour ago, mgutt said:

You are not using the official MariaDB Container. Ask linuxserver for support regarding their container.

Ah.  I had not realized until now that there even was more than one version.  I had set this up when I upgraded to version 6 Unraid in 2018 and this must have been the default in user apps then?

Anyway, here is another question: can I simply switch to the official container or will this mess up the database? 

Also, I found this: https://forum.kodi.tv/showthread.php?tid=360717&pid=3020992#pid3020992

He has the same error that I have.  So, apparently updating the mariadb docker does not automatically convert the database.  I find it odd that updates to a program like this would not be backwards compatible with existing databases but whatever.

The solution for him was to run mysql_update  but I am at a lost to see what good that did since hhe also dropped the databases and essentially re-created them from scratch.

Anyway, thanks for your help.

[mgutt]

33 minutes ago, CaptainTivo said:

can I simply switch to the official container

You need to create a dump and import the dump on the official container:

https://gist.github.com/spalladino/6d981f7b33f6e0afe6bb

 

 

https://davejansen.com/how-to-dump-and-restore-a-mariadb-mysql-database-from-a-docker-container/

 

 

[Profezor]

Weird!!

 

Had to reinstall and now I get this instead of a successful install. How do I correct it? -

 

docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/init": stat /init: no such file or directory: unknown.

The command failed.

[Profezor]

On 2/21/2022 at 4:00 PM, Profezor said:

Weird!!

 

Had to reinstall and now I get this instead of a successful install. How do I correct it? -

 

docker: Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/init": stat /init: no such file or directory: unknown.

The command failed.

Update; same error as I continue to try to reinstall. Any ideas?

[mgutt]

On 2/21/2022 at 4:00 PM, Profezor said:

Had to reinstall and now I get this instead of a successful install. How do I correct it? -

Did you totally remove the appdata/mariadb dir (If does not contain important databases).

[Profezor]

8 minutes ago, mgutt said:

Did you totally remove the appdata/mariadb dir (If does not contain important databases).

Tried to use rmdir to delete the dir but it says it is read only and will not let me. 😞 

There has to be a way to override that and delete it.

[mgutt]

15 minutes ago, Profezor said:

Tried to use rmdir to delete

Use the appdata cleanup plugin.

[Profezor]

On 2/23/2022 at 5:02 PM, mgutt said:

Use the appdata cleanup plugin.

Done.

Reinstalled with the same error as above.

[mgutt]

On 2/25/2022 at 3:55 PM, Profezor said:

Reinstalled with the same error

Remove the Container, then go to Apps > Previuos Apps and delete the MariaDB Official result. This deletes the template file from your USB flash drive. Now search for MariaDB Official again and install it with the default settings (set only a random password for testing).

 

Or are you using an outdated unRAID Version?

[Giorgio]

On 10/6/2021 at 8:45 PM, mgutt said:

Don't need to. Instead you create a new cnf file:

https://forums.unraid.net/topic/110019-support-mariadb-official/?do=findComment&comment=1024598

 

 

Note this post:

https://forums.unraid.net/topic/110019-support-mariadb-official/?do=findComment&comment=1039530

 

 

 

Hello,

I don't understand how to create a new file, since nano or other editor are not available and mariadb console is isolated from unraid console.

I need to edit 50-server.cnf with kodi settings

tnx for the help

[trurl]

23 minutes ago, Giorgio said:

I don't understand how to create a new file

Does that new file not belong with the other .cnf files, in the appdata which you can access from unraid?

[Giorgio]

24 minutes ago, trurl said:

Does that new file not belong with the other .cnf files, in the appdata which you can access from unraid?

Can't create new file in mariadb-official.conf.d because I can't find an editor using docker console.

Don't see any file in /mnt/user/appdata/mariadb-official/config using unraid console.

[mgutt]

8 hours ago, Giorgio said:

,

I don't understand how to create a new file, since nano or other editor are not available and mariadb console is isolated from unraid console

If you need to create Files inside a Container, you need to edit the container settings and add a file path which is linked to Appdata.

[Giorgio]

On 3/3/2022 at 7:56 AM, mgutt said:

If you need to create Files inside a Container, you need to edit the container settings and add a file path which is linked to Appdata.

The situation now is:

 

/var/lib/mysql <--> /mnt/user/appdata/mariadb-official/data

/etc/mysql/conf.d <--> /mnt/user/appdata/mariadb-official/config

 

Exploring /etc/mysql/conf.d with mariadb terminal results in empty directory while /etc/mysql/mariadb.conf.d contains 50-client.cnf 50-mysql-clients.cnf 50-mysqld_safe.cnf 50-server.cnf 60-galera.cnf 99-enable-encription.cnf.preset

 

I need to edit 50-server.cnf so I tried to add the link /etc/mysql/mariadb.conf.d <--> /mnt/user/appdata/mariadb-official/config/ (modifing /etc/mysql/conf.d <--> /mnt/user/appdata/mariadb-official/ to avoid possible conflict).

Connecting by unraid terminal the /mnt/user/appdata/mariadb-official/config directory still appear empty

 

I don't understand why the link does't work. For example with snapshot container I don't have any issue and I can edit configuration file with nano using unraid terminal .

 

Tnx for the support

[Giorgio]

On 3/4/2022 at 1:48 PM, Giorgio said:

The situation now is:

 

/var/lib/mysql <--> /mnt/user/appdata/mariadb-official/data

/etc/mysql/conf.d <--> /mnt/user/appdata/mariadb-official/config

 

Exploring /etc/mysql/conf.d with mariadb terminal results in empty directory while /etc/mysql/mariadb.conf.d contains 50-client.cnf 50-mysql-clients.cnf 50-mysqld_safe.cnf 50-server.cnf 60-galera.cnf 99-enable-encription.cnf.preset

 

I need to edit 50-server.cnf so I tried to add the link /etc/mysql/mariadb.conf.d <--> /mnt/user/appdata/mariadb-official/config/ (modifing /etc/mysql/conf.d <--> /mnt/user/appdata/mariadb-official/ to avoid possible conflict).

Connecting by unraid terminal the /mnt/user/appdata/mariadb-official/config directory still appear empty

 

I don't understand why the link does't work. For example with snapshot container I don't have any issue and I can edit configuration file with nano using unraid terminal .

 

Tnx for the support

no idea on what i'm doing wrong?

[michielvv]

All,

 

First of all: thanks for making the MariaDB docker available. Got a challenge though. Fresh out of the box (with the only change of port 3306 >> 3307 due to an existing MariaDB for nextcloud running on 3306 already) I get the following log with errors (and not working database):

 

 

2022-03-10 11:39:35+01:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.7.3+maria~focal started.
2022-03-10 11:39:36+01:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-03-10 11:39:36+01:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-03-10 11:39:36 0 [Note] mariadbd (server 10.7.3-MariaDB-1:10.7.3+maria~focal) starting as process 1 ...
2022-03-10 11:39:36 0 [ERROR] mariadbd: Can't lock aria control file '/var/lib/mysql/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds
2022-03-10 11:40:06 0 [ERROR] mariadbd: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/var/lib/mysql/aria_log_control'
2022-03-10 11:40:06 0 [ERROR] Plugin 'Aria' init function returned error.
2022-03-10 11:40:06 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.
2022-03-10 11:40:06 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-03-10 11:40:06 0 [Note] InnoDB: Number of transaction pools: 1
2022-03-10 11:40:06 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-03-10 11:40:06 0 [Note] InnoDB: Using Linux native AIO
2022-03-10 11:40:06 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
2022-03-10 11:40:06 0 [Note] InnoDB: Completed initialization of buffer pool
2022-03-10 11:40:06 0 [Note] InnoDB: Starting crash recovery from checkpoint LSN=33207616354,33207616354
2022-03-10 11:40:06 0 [ERROR] InnoDB: Malformed log record; set innodb_force_recovery=1 to ignore.
2022-03-10 11:40:06 0 [Note] InnoDB: Dump from the start of the mini-transaction (LSN=33207616354) to 100 bytes after the record:
len 100; hex 66696c655f6c6f636b7302075052494d415259030473697a6500350206806c20bc270120063e590000033924df00205e0082b9030d070f20000120063ee0590000033924df096e657874636c6f75640d6f635f66696c655f6c6f636b73075052494d4152; asc file_locks PRIMARY size 5 l ' >Y 9$ ^ > Y 9$ nextcloud oc_file_locks PRIMAR;
2022-03-10 11:40:06 0 [Warning] InnoDB: Log scan aborted at LSN 33207681024
2022-03-10 11:40:06 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-03-10 11:40:06 0 [Note] InnoDB: Starting shutdown...
2022-03-10 11:40:06 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-03-10 11:40:06 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-03-10 11:40:06 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-03-10 11:40:06 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
2022-03-10 11:40:06 0 [ERROR] Failed to initialize plugins.
2022-03-10 11:40:06 0 [ERROR] Aborting

 

What does this mean and how to fix this? I have searched a lot and usually succeed, but I cannot solve this one...

 

Thanks in advance!