11 minutes ago, mgutt said:

Enable advanced view. I think there will be a list of unused containers which use the same image. Delete them first.

I did this and found 8 orphaned images. I removed all of them. MariaDB still will not start.

43 minutes ago, loosenut76 said:

The container name "/MariaDB-Official" is already in use by container "a36ecc17e0f22dbb129841b053be336e40b191694e58d36bddd64d3bdb274325". 

Do you still have this error message? The I would say stop/start the array to force stopping all containers.

4 hours ago, mgutt said:

Do you still have this error message? The I would say stop/start the array to force stopping all containers.

Yes I still have the error. I rebooted my Unraid box, and still got the same error.

One item I noticed, is that turning on advanced view listed a Container ID fofor each container. The container listed in the error message starts with the Container ID from the advanced view.

"Container ID: a36ecc17e0f2"

And at which step do you get the error? For me it sounds like you don't edit the container, instead you try to add the same container, which obviously is not possible.

It stopped working without me doing anything. I thought it was working after upgrading to 7.0.0, but I don't know for sure. I just happened to notice it wasn't running when I couldn't get into Photo Prism.

 

All editing and deletion attempts were after the issue was found on an attempt to fix it.

On 3/31/2025 at 8:47 PM, kitten-kiwi said:

Hi, I am running the newest version Of MDB Official, or at least i try. Since the Update the container wont start, but i cant loose the database. any idea how to fix it?
 

Log:

 

2025-03-31 20:19:39 0 [Note] Starting MariaDB 11.7.2-MariaDB-ubu2404 source revision 80067a69feaeb5df30abb1bfaf7d4e713ccbf027 server_uid Tnq7keT8GKDxmAtaGW699QQYKjk= as process 1
2025-03-31 20:19:39 0 [Note] InnoDB: Compressed tables use zlib 1.3
2025-03-31 20:19:39 0 [Note] InnoDB: Using transactional memory
2025-03-31 20:19:39 0 [Note] InnoDB: Number of transaction pools: 1
2025-03-31 20:19:39 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-03-31 20:19:39 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 0
2025-03-31 20:19:39 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
2025-03-31 20:19:39 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2025-03-31 20:19:39 0 [Note] InnoDB: Completed initialization of buffer pool
2025-03-31 20:19:39 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-03-31 20:19:39 0 [Note] InnoDB: End of log at LSN=37776
2025-03-31 20:19:39 0 [Note] InnoDB: Opened 3 undo tablespaces
2025-03-31 20:19:39 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2025-03-31 20:19:39 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2025-03-31 20:19:39 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2025-03-31 20:19:39 0 [Note] InnoDB: log sequence number 37776; transaction id 4
2025-03-31 20:19:39 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-03-31 20:19:39 0 [Note] Plugin 'wsrep-provider' is disabled.
2025-03-31 20:19:39 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2025-03-31 20:19:39 0 [Note] InnoDB: Buffer pool(s) load completed at 250331 20:19:39
2025-03-31 20:19:39 0 [ERROR] Can't open and lock privilege tables: Can't find file: './mysql/servers.MAI' (errno: 2 "No such file or directory")
2025-03-31 20:19:41 0 [Note] Server socket created on IP: '0.0.0.0'.
2025-03-31 20:19:41 0 [Note] Server socket created on IP: '::'.
2025-03-31 20:19:41 0 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/db.MAI' (errno: 2 "No such file or directory")
2025-03-31 20:19:41 0 [ERROR] Aborting
2025-03-31 20:19:38+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.7.2+maria~ubu2404 started.
2025-03-31 20:19:39+02:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting

** Press ANY KEY to close this window ** 

 

Start Command:
 

docker run
  -d
  --name='MariaDB-Official'
  --net='bridge'
  --pids-limit 2048
  --privileged=true
  -e TZ="Europe/Berlin"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="VOID"
  -e HOST_CONTAINERNAME="MariaDB-Official"
  -e 'MARIADB_DATABASE'='REDACTED'
  -e 'MARIADB_USER'='REDACTED'
  -e 'MARIADB_PASSWORD'='REDACTED'
  -e 'MARIADB_ROOT_PASSWORD'='REDACTED'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://github.com/mgutt/unraid-docker-templates/raw/main/mgutt/images/mariadb.png'
  -p '3306:3306/tcp'
  -v '/mnt/user/appdata/mariadb-official-nc/data':'/var/lib/mysql':'rw'
  -v '/mnt/user/appdata/mariadb-official-nc/config':'/etc/mysql/conf.d':'rw'
  --user=99:100
  --memory=2G 'mariadb'

 

 

Does anyone know what i can do to fix it?

 

What i already ckecked:

- Forced update did not helped.

- Parity is valid.

- rebooted Server

- removed power from server for more than 15 min

 

Specs:

- Unraid Version 7.0.1
- M/B: ASUSTeK COMPUTER INC. PRIME X299-A II Version Rev 1.xx s/n 190857319200374

- BIOS: American Megatrends Inc. Version 1403 Dated 05/23/2022

- CPU: Intel® Core™ i9-9940X CPU @ 3.30GHz

- HVM: Enabled

- IOMMU: Enabled

- Cache: L1-Cache: 0 KiB, L2-Cache: 0 KiB, L3-Cache: 0 KiB

- Memory: 32 GiB DDR4 (max. installable capacity 3072 GiB)

- Network: bond0: fault-tolerance (active-backup), mtu 1500

- Kernel: Linux 6.6.78-Unraid x86_64

- OpenSSL: 3.4.1

 

As i said, if anyone kows something, please help.

Hi @mgutt, i know you might be head over toes in other troubleshooting procedures, but can you please have a look at this as well? Currently 3 of my services are down, because they depend on this database. If you dont have time, you may know someone elde to ask? 

 

Best Regards 

Kiwi

 

Ps: sorry for being annoying or if this is already solved and i am just to blind to find it. 

1 hour ago, mgutt said:

And at which step do you get the error? For me it sounds like you don't edit the container, instead you try to add the same container, which obviously is not possible.

I just re-read your message, and I don't think I answered it clearly. I get different errors depending on what I try to do. My first post had images of the errors. I get a different error trying to start, Delete, or save a configuration change (link move to a different network). Deleting orphaned images from Docker didn't change anything. Rebooting UnRaid did not change anything.

1 hour ago, kitten-kiwi said:

skipped due to $MARIADB_AUTO_UPGRADE setting

Do you have this variable? If not, create it:

 

26 minutes ago, loosenut76 said:

Deleting orphaned images from Docker didn't change anything. Rebooting UnRaid did not change anything.

Delete the container. Then check for orphaned containers. Delete them, too. Finally re-add the container through "add container" and select the container's template from the dropdown.

8 hours ago, loosenut76 said:

 I do have auto update for docker containers enabled

A comment regarding this: Never use auto update in combination with :latest containers. It's a guarantee for incidents. At least you should limit it to a major version like :10 so you won't hit the most alpha release of an upgrade which often contains bugs. That's the reason why I'm still not using Unraid 7 😉

29 minutes ago, mgutt said:

Do you have this variable? If not, create it:

 

I added your variable and it just gave me a new error, but the old error is still there

 

2025-04-02  1:16:12 0 [Note] Starting MariaDB 11.7.2-MariaDB-ubu2404 source revision 80067a69feaeb5df30abb1bfaf7d4e713ccbf027 server_uid kHDchnVZSkxlm6ySc12huKSFRik= as process 1
2025-04-02  1:16:12 0 [Note] InnoDB: Compressed tables use zlib 1.3
2025-04-02  1:16:12 0 [Note] InnoDB: Using transactional memory
2025-04-02  1:16:12 0 [Note] InnoDB: Number of transaction pools: 1
2025-04-02  1:16:12 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-04-02  1:16:12 0 [Note] InnoDB: Using liburing
2025-04-02  1:16:12 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2025-04-02  1:16:12 0 [Note] InnoDB: Completed initialization of buffer pool
2025-04-02  1:16:12 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)
2025-04-02  1:16:12 0 [Note] InnoDB: End of log at LSN=37776
2025-04-02  1:16:12 0 [Note] InnoDB: Opened 3 undo tablespaces
2025-04-02  1:16:12 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.
2025-04-02  1:16:12 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
2025-04-02  1:16:12 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
2025-04-02  1:16:12 0 [Note] InnoDB: log sequence number 37776; transaction id 4
2025-04-02  1:16:12 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-04-02  1:16:12 0 [Note] Plugin 'wsrep-provider' is disabled.
2025-04-02  1:16:12 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
2025-04-02  1:16:12 0 [Note] InnoDB: Buffer pool(s) load completed at 250402  1:16:12
2025-04-02  1:16:12 0 [ERROR] Can't open and lock privilege tables: Can't find file: './mysql/servers.MAI' (errno: 2 "No such file or directory")
2025-04-02  1:16:13 0 [Note] Server socket created on IP: '0.0.0.0'.
2025-04-02  1:16:13 0 [Note] Server socket created on IP: '::'.
2025-04-02  1:16:13 0 [ERROR] Fatal error: Can't open and lock privilege tables: Can't find file: './mysql/db.MAI' (errno: 2 "No such file or directory")
2025-04-02  1:16:13 0 [ERROR] Aborting
2025-04-02 01:16:11+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.7.2+maria~ubu2404 started.
2025-04-02 01:16:12+02:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade or creating healthcheck users) required, but skipped due to $MARIADB_AUTO_UPGRADE setting

** Press ANY KEY to close this window ** 

 

I will attach all my variables

7 hours ago, kitten-kiwi said:

I added your variable

Strange, should work. Key is set the same? (Name is irrelevant, it's only a description of the var)

 

Usually the logs changes while an upgrade to the following lines:

 

2025-03-23 11:02:38+01:00 [Note] [Entrypoint]: Starting mariadb-upgrade
The --upgrade-system-tables option was used, user tables won't be touched.
Major version upgrade detected from 11.6.2-MariaDB to 11.7.2-MariaDB. Check required!
Phase 1/8: Checking and upgrading mysql database
Processing databases
mysql
mysql.column_stats                                 OK
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.global_priv                                  OK
mysql.gtid_slave_pos                               OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.index_stats                                  OK
mysql.innodb_index_stats                           OK
mysql.innodb_table_stats                           OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.roles_mapping                                OK
mysql.servers                                      OK
mysql.table_stats                                  OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.transaction_registry                         OK
Phase 2/8: Installing used storage engines... Skipped
Phase 3/8: Running 'mysql_fix_privilege_tables'
Phase 4/8: Fixing views... Skipped
Phase 5/8: Fixing table and database names ... Skipped
Phase 6/8: Checking and upgrading tables... Skipped
Phase 7/8: uninstalling plugins
Phase 8/8: Running 'FLUSH PRIVILEGES'
OK
2025-03-23 11:02:49+01:00 [Note] [Entrypoint]: Finished mariadb-upgrade

 

 

And after (so the variable can be used permanently):

 

 

2025-04-01 04:01:23+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.7.2+maria~ubu2404 started.
2025-04-01 04:01:24+02:00 [Note] [Entrypoint]: MariaDB upgrade not required

 

Documentation:

https://hub.docker.com/_/mariadb

8 hours ago, mgutt said:

Strange, should work. Key is set the same? (Name is irrelevant, it's only a description of the var)

 

Usually the logs changes while an upgrade to the following lines:

 

2025-03-23 11:02:38+01:00 [Note] [Entrypoint]: Starting mariadb-upgrade
The --upgrade-system-tables option was used, user tables won't be touched.
Major version upgrade detected from 11.6.2-MariaDB to 11.7.2-MariaDB. Check required!
Phase 1/8: Checking and upgrading mysql database
Processing databases
mysql
mysql.column_stats                                 OK
mysql.columns_priv                                 OK
mysql.db                                           OK
mysql.event                                        OK
mysql.func                                         OK
mysql.global_priv                                  OK
mysql.gtid_slave_pos                               OK
mysql.help_category                                OK
mysql.help_keyword                                 OK
mysql.help_relation                                OK
mysql.help_topic                                   OK
mysql.index_stats                                  OK
mysql.innodb_index_stats                           OK
mysql.innodb_table_stats                           OK
mysql.plugin                                       OK
mysql.proc                                         OK
mysql.procs_priv                                   OK
mysql.proxies_priv                                 OK
mysql.roles_mapping                                OK
mysql.servers                                      OK
mysql.table_stats                                  OK
mysql.tables_priv                                  OK
mysql.time_zone                                    OK
mysql.time_zone_leap_second                        OK
mysql.time_zone_name                               OK
mysql.time_zone_transition                         OK
mysql.time_zone_transition_type                    OK
mysql.transaction_registry                         OK
Phase 2/8: Installing used storage engines... Skipped
Phase 3/8: Running 'mysql_fix_privilege_tables'
Phase 4/8: Fixing views... Skipped
Phase 5/8: Fixing table and database names ... Skipped
Phase 6/8: Checking and upgrading tables... Skipped
Phase 7/8: uninstalling plugins
Phase 8/8: Running 'FLUSH PRIVILEGES'
OK
2025-03-23 11:02:49+01:00 [Note] [Entrypoint]: Finished mariadb-upgrade

 

 

And after (so the variable can be used permanently):

 

 

2025-04-01 04:01:23+02:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.7.2+maria~ubu2404 started.
2025-04-01 04:01:24+02:00 [Note] [Entrypoint]: MariaDB upgrade not required

 

Documentation:

https://hub.docker.com/_/mariadb

So, i checked and i made a mistake with the var... changed it but the container still crashes. Screenshots attached.

 

 

Throw the error lines into an ai chat. I'd say it's broken. Not sure what to try next.

 

Did you probably set appdata to use both, array and cache? Maybe something got corrupt while moving files. 

I have used MariaDB for several years and every time I go to configure it anew, I loose more hair. I am bald now.

First I cannot get it to create my kodi database even though I setup the user name and password as in the same for the advancedsetting.xml.

Skipping on that failure, I tried using the default generated password where I am supposed to find it in the log. Not finding it in the log below.

text error warn system array login

2025-06-27 17:51:11 0 [Note] Starting MariaDB 11.8.2-MariaDB-ubu2404 source revision 8d36cafe4fc700e6e577d5a36650c58707e76b92 server_uid Tnq7keT8GKDxmAtaGW699QQYKjk= as process 1

2025-06-27 17:51:11 0 [Note] InnoDB: Compressed tables use zlib 1.3

2025-06-27 17:51:11 0 [Note] InnoDB: Number of transaction pools: 1

2025-06-27 17:51:11 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions

2025-06-27 17:51:11 0 [Warning] mariadbd: io_uring_queue_init() failed with EPERM: sysctl kernel.io_uring_disabled has the value 2, or 1 and the user of the process is not a member of sysctl kernel.io_uring_group. (see man 2 io_uring_setup).

2025-06-27 17:51:11 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF

2025-06-27 17:51:11 0 [Note] InnoDB: innodb_buffer_pool_size_max=128m, innodb_buffer_pool_size=128m

2025-06-27 17:51:11 0 [Note] InnoDB: Completed initialization of buffer pool

2025-06-27 17:51:11 0 [Note] InnoDB: Buffered log writes (block size=512 bytes)

2025-06-27 17:51:11 0 [Note] InnoDB: End of log at LSN=47763

2025-06-27 17:51:11 0 [Note] InnoDB: Opened 3 undo tablespaces

2025-06-27 17:51:11 0 [Note] InnoDB: 128 rollback segments in 3 undo tablespaces are active.

2025-06-27 17:51:11 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...

2025-06-27 17:51:11 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.

2025-06-27 17:51:11 0 [Note] InnoDB: log sequence number 47763; transaction id 14

2025-06-27 17:51:11 0 [Note] Plugin 'FEEDBACK' is disabled.

2025-06-27 17:51:11 0 [Note] Plugin 'wsrep-provider' is disabled.

2025-06-27 17:51:11 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool

2025-06-27 17:51:11 0 [Note] InnoDB: Buffer pool(s) load completed at 250627 17:51:11

2025-06-27 17:51:11 0 [Note] Server socket created on IP: '0.0.0.0'.

2025-06-27 17:51:11 0 [Note] Server socket created on IP: '::'.

2025-06-27 17:51:11 0 [Note] mariadbd: Event Scheduler: Loaded 0 events

2025-06-27 17:51:11 0 [Note] mariadbd: ready for connections.

Version: '11.8.2-MariaDB-ubu2404' socket: '/run/mysqld/mysqld.sock' port: 3306 mariadb.org binary distribution

2025-06-27 17:51:10-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:11.8.2+maria~ubu2404 started.

2025-06-27 17:51:10-07:00 [Note] [Entrypoint]: MariaDB upgrade not required

4 hours ago, RaidPC said:

First I cannot get it to create my kodi database even though I setup the user name and password as in the same for the advancedsetting.xml.

Are you sure Kodi can reach mariadb? Where is Kodi running? If it is outside of unraid: test external access with an application like Heidi SQL. If it is an internal container: Which networks are both using?

Your right of course. After four hours last night of trying and trying, giving my user account kodi different passwords, going into terminal and giving kodi complete permissions and such, I went to bed with a thought on my mind.

Instead of setting up a new account, I took the easy approach and gave in and tried using the default root account. In 10 minutes I had Kodi up and running pulling in the media. May not be the 'professional' thing to do using the root account of MariaDB, but since it only is used for Kodi, I thought why not? None of this is open to the WAN and I do not run any VPN.

I don't know how Kodi does the setup, but maybe it needs root to create a database, before creating the tables and data?! And yes, finally it's irrelevant if you use one mariadb container per application if you use the root login.

can someone help me in resetting the root password. I've tried all the recommended solutions: Adding --skip-grant-tables to Post Arguments results in an error. Adding mysql_safe --skip-grant-tables or mariadbd-safe --skip-grant-tables makes the container not start. I've modified the custom.cnf file to add skip-grant-tables to the mysqld block, this lets the container start but still can't access mysql to reset the password.

Any more suggestions? Do I just have to nuke the install and start over? If so how can I backup my databases?

On 6/10/2021 at 3:33 AM, mgutt said:

Set Root Password

 

If you like to manually set your root password remove the word "yes" from "Generate Random Password":

 

Then set your password through "Show more settings":

 

Note: This does not allow to change the password.

 

Reset Root Password

 

Edit the container, enable advanced view and add "mysqld_safe --skip-grant-tables" to the Post Arguments and start the container:

 

Open the cotnainer's console and execute the following commands:

mariadb -u root

 

Now you are connected to MariaDB. Execute this:

FLUSH PRIVILEGES;

 

And finally this:

SET PASSWORD FOR root@'localhost' = PASSWORD('your_new_password');

 

 

Finally edit the container and remove the "mysqld_safe --skip-grant-tables" part again.

Just in case someone runs into this too while trying to reset the password with a newer version of MariaDB. Don't use mysqld_safe --skip-grant-tables use mariadbd-safe --skip-grant-tables. Everything else stays the same.

Summary: Wordpress not connecting to mariadb, and I'm not getting anywhere yet.

Newly installed MariaDB.Official and Wordpress dockers today.

Wordpress will not launch from the machine's local network IP address:8080

I've attached logs of both dockers and their configs, as well as diagnostics.

I can't see any glaring errors in configs, mariadb log perhaps?

Diagnostics file for docker is empty, and other dockers appear to be fully functional.

Any help would be greatly appreciated...

2025-10-06 local-logterminal-MariaDB-Official.log.txt 2025-10-06 logterminal-WordPress.log.log.txt sagittarius-diagnostics-20251006-1847.zip

DB runs on 3306 but you gave 8080 on the DB host line in the WP template.

Edited October 6, 2025Oct 6 by Kilrah

Doh!😆Thanks Kilrah very muchly.

Thought I was going bananas,cheers😄

Hi all

I'm running a Wordpress website with MariaDB and am having issues with slow access time. I've narrowed it down to the database since loading static webpages is instant. It's only when I try and load my wordpress site, I usually experience about 3 seconds of lag time.

Swag is my web server with nginx handling reverse proxy.

Hosted on an i7-6700k with 32gb ram. Appdata/docker is all on an SSD cache drive.

What's the best way to start troubleshooting this? Thanks

19 hours ago, nesburf said:

What's the best way to start troubleshooting this

Create slow.cnf in your config directory:

[mysqld]
slow_query_log = 1
slow_query_log_file = /var/lib/mysql/slow.log
long_query_time = 2
log_output = FILE

Change perms:

chmod -v "0600" /mnt/user/appdata/*mariadb*/config/slow.cnf

• Stop web containers using mariadb.

• Restart mariadb container.

• Start web containers.

• Check if any queries are logged (the slow.log file will be created even if no slow query has been captured by now).