[Support] MariaDB Official

trurl · March 10, 2022

30 minutes ago, michielvv said:

due to an existing MariaDB for nextcloud running

You don't need multiple instances. You can have multiple databases in one.

michielvv · March 10, 2022

15 minutes ago, michielvv said:

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!

...and fixed it: my Nextcloud installation used /mnt/user/appdata/mariadb-official/ which is what the mariadb-official installer by default refers to. Because the Nextcloud Mysql is running, the filelock prevented havoc. My bad - though maybe an error as in 'data dir already exists!' or have the name of the data-dir rely on the name of the docker in Unraid would be convenient (though you might get other user errors )!

michielvv · March 10, 2022

42 minutes ago, trurl said:

You don't need multiple instances. You can have multiple databases in one.

Thanks, i know. Just want to be absolutely sure i do not somehow screw up the Nextcloud database, so used the docker convenience to separate those databases as much as possible

mgutt · March 10, 2022

1 hour ago, michielvv said:

so used the docker convenience to separate those databases as much as possible

I'll do the same. Is even easier if you need to restore something as you don't need to rely on SQL dumps.

Giorgio · March 25, 2022

I finally did it.

Now kodi database works on mariadb docker.

I had installed mariadb official setting:

Generate random password - yes (remember on the first run to read and save the password from the log)

Database name: kodi

Database User: kodi

Database password: set a password

after the installation I entered by mariadb console and copied all files in mariadb.conf.d to conf.d (cp not mv)

then modified the path in the link from /etc/mysql/conf.d to /etc/mysql/mariadb.conf.d activating advanced settings

(I had to copy the files because if i didn't the mariadb.conf.d after changing the link resulted empty, I don't know why)

from UNRAID console I edited the 50-server.cnf setting the bind address to 0.0.0.0

from mariadb console:

mysql -u root -p (entering the root random password)

GRANT ALL ON *.* TO 'kodi';

remember to setting up kodi with proper advancedsettings.xml

vaeyl · May 9, 2022

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

Reset Root Password

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

Now open the console of the container and execute the following commands:

After changing this setting and saving, I see the container init seem to work:

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 'MYSQL_ROOT_PASSWORD'='XXX' -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='0640' -p '3306:3306/tcp' -v '/mnt/user/appdata/mariadb':'/config':'rw' 'lscr.io/linuxserver/mariadb' --skip-grant-tables
afe5b0a7c10e60b6cad6575c99e0ddddbe21a9e32a3560e0e0f6bcb11a002c93

The command finished successfully!

When I check the container afterward, it's stopped with the following log message:

[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-grant-tables: No such file or directory
[cmd] --skip-grant-tables 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.
220508 12:24:32 mysqld_safe Logging to '/config/databases/ec61d38e0ea8.err'.
220508 12:24:32 mysqld_safe Starting mariadbd daemon with databases from /config/databases

It seems to be attempting exec the --skip-grant-tables that I placed in Post Arguments. Any idea what I might have done incorrectly?

mgutt · May 12, 2022

On 5/9/2022 at 3:22 AM, vaeyl said:

It seems to be attempting exec the --skip-grant-tables that I placed in Post Arguments

Which is usually correct, but it seems not working anymore. Please try this instead:

mysqld_safe --skip-grant-tables

God_TM · May 23, 2022

I recently updated to Unraid 6.10 and subsequently to 6.10.1. Not many issues for the most part, but today, I noticed mariadb had an update available. I ran the update on the container, but now it won't start. The logs have this:

2022-05-23 12:29:19-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-05-23 12:29:20-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-05-23 12:29:20-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-05-23 12:29:20 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ...
2022-05-23 12:29:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-23 12:29:20 0 [Note] InnoDB: Number of transaction pools: 1
2022-05-23 12:29:20 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-05-23 12:29:20 0 [Note] InnoDB: Using liburing
2022-05-23 12:29:20 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-05-23 12:29:20 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-23 12:29:20 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4.
2022-05-23 12:29:20 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-05-23 12:29:20 0 [Note] InnoDB: Starting shutdown...
2022-05-23 12:29:20 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-05-23 12:29:20 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-05-23 12:29:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-05-23 12:29:20 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-05-23 12:29:20 0 [ERROR] Aborting
2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-05-23 12:40:25 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ...
2022-05-23 12:40:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-23 12:40:25 0 [Note] InnoDB: Number of transaction pools: 1
2022-05-23 12:40:25 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-05-23 12:40:25 0 [Note] InnoDB: Using liburing
2022-05-23 12:40:25 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-05-23 12:40:25 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-23 12:40:25 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4.
2022-05-23 12:40:25 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-05-23 12:40:25 0 [Note] InnoDB: Starting shutdown...
2022-05-23 12:40:25 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-05-23 12:40:25 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-05-23 12:40:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-05-23 12:40:25 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-05-23 12:40:25 0 [ERROR] Aborting

Any idea on how to fix this?

mgutt · May 23, 2022

25 minutes ago, God_TM said:

Any idea on how to fix this?

1.) try to force an older version with a version tag. After it starts create a dump, install the recent mariadb and restore the dump.

2.) try these steps: https://github.com/MariaDB/mariadb-docker/issues/413

JAnguita · May 24, 2022

16 hours ago, God_TM said:

I recently updated to Unraid 6.10 and subsequently to 6.10.1. Not many issues for the most part, but today, I noticed mariadb had an update available. I ran the update on the container, but now it won't start. The logs have this:

2022-05-23 12:29:19-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-05-23 12:29:20-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-05-23 12:29:20-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-05-23 12:29:20 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ...
2022-05-23 12:29:20 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-23 12:29:20 0 [Note] InnoDB: Number of transaction pools: 1
2022-05-23 12:29:20 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-05-23 12:29:20 0 [Note] InnoDB: Using liburing
2022-05-23 12:29:20 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-05-23 12:29:20 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-23 12:29:20 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4.
2022-05-23 12:29:20 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-05-23 12:29:20 0 [Note] InnoDB: Starting shutdown...
2022-05-23 12:29:20 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-05-23 12:29:20 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-05-23 12:29:20 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-05-23 12:29:20 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-05-23 12:29:20 0 [ERROR] Aborting
2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-05-23 12:40:25-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-05-23 12:40:25 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ...
2022-05-23 12:40:25 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
2022-05-23 12:40:25 0 [Note] InnoDB: Number of transaction pools: 1
2022-05-23 12:40:25 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2022-05-23 12:40:25 0 [Note] InnoDB: Using liburing
2022-05-23 12:40:25 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
2022-05-23 12:40:25 0 [Note] InnoDB: Completed initialization of buffer pool
2022-05-23 12:40:25 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.5.4.
2022-05-23 12:40:25 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2022-05-23 12:40:25 0 [Note] InnoDB: Starting shutdown...
2022-05-23 12:40:25 0 [ERROR] Plugin 'InnoDB' init function returned error.
2022-05-23 12:40:25 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.
2022-05-23 12:40:25 0 [Note] Plugin 'FEEDBACK' is disabled.
2022-05-23 12:40:25 0 [ERROR] Unknown/unsupported storage engine: InnoDB
2022-05-23 12:40:25 0 [ERROR] Aborting

Any idea on how to fix this?

I'm having the same problem!!!

rhodo · May 26, 2022

On 5/24/2022 at 8:32 AM, JAnguita said:

I'm having the same problem!!!

Me too... To resolve the problem I rolled back to an earlier version. I didn't go through the rollback / dump / upgrade / restore process. I'll stick with the older version for now. Just happy to have it working again.

To rollback... I set the repository to mariadb:10.6.8 in the docker edit settings page.

JIll · May 27, 2022

23 hours ago, rhodo said:

Me too... To resolve the problem I rolled back to an earlier version. I didn't go through the rollback / dump / upgrade / restore process. I'll stick with the older version for now. Just happy to have it working again.

To rollback... I set the repository to mariadb:10.6.8 in the docker edit settings page.

Save my life, thanks bro

YsarKain · June 19, 2022

I just upgraded Unraid to 6.10.3 and everything is fine EXCEPT for MariaDB 😞

Here's the error I'm getting:

[code]

2022-06-19 12:17:21 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ...
2022-06-19 12:17:21 0 [Warning] Can't create test file /var/lib/mysql/a42249648c38.lower-test
2022-06-19 12:17:21 0 [ERROR] mariadbd: Can't create/write to file './ddl_recovery.log' (Errcode: 13 "Permission denied")
2022-06-19 12:17:21 0 [ERROR] DDL_LOG: Failed to create ddl log file: ./ddl_recovery.log
2022-06-19 12:17:21 0 [ERROR] Aborting
2022-06-19 12:17:33 0 [Note] mariadbd (server 10.8.3-MariaDB-1:10.8.3+maria~jammy) starting as process 1 ...
2022-06-19 12:17:33 0 [Warning] Can't create test file /var/lib/mysql/a42249648c38.lower-test
2022-06-19 12:17:33 0 [ERROR] mariadbd: Can't create/write to file './ddl_recovery.log' (Errcode: 13 "Permission denied")
2022-06-19 12:17:33 0 [ERROR] DDL_LOG: Failed to create ddl log file: ./ddl_recovery.log
2022-06-19 12:17:33 0 [ERROR] Aborting
2022-06-19 12:17:19-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-06-19 12:17:21-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-06-19 12:17:21-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting
2022-06-19 12:17:33-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-06-19 12:17:33-07:00 [Note] [Entrypoint]: MariaDB upgrade information missing, assuming required
2022-06-19 12:17:33-07:00 [Note] [Entrypoint]: MariaDB upgrade (mariadb-upgrade) required, but skipped due to $MARIADB_AUTO_UPGRADE setting

[/code]

So it looks like a permission error, but how do I get to it to reset the perms?

YsarKain · June 19, 2022

Nevermind I got it!

The /mnt/user/appdata/mariadb-official/data and /config directories were set to root:root

I chown them to nobody:users and it looks like it's back in business!

lhw1221 · June 25, 2022

hello i did the unriad update today and marinaDB stopt working (not even starting)

i have an backup of the my unraid flash, but MariaDB dies even if i do an update of the Container itselve.
until now i just ignor the problem and just did not do an update of the container.
But it seems i can´t even update unraid.
I have no plan About DB Server in General
Pls help

Protokoll:

022-06-25  6:27:38 0 [Warning] Can't create test file /var/lib/mysql/0c5318a0e27e.lower-test
/usr/sbin/mariadbd: Can't change dir to '/var/lib/mysql/' (Errcode: 13 "Permission denied")
2022-06-25  6:27:38 0 [ERROR] Aborting
2022-06-25  6:28:11 0 [Warning] Can't create test file /var/lib/mysql/0c5318a0e27e.lower-test
/usr/sbin/mariadbd: Can't change dir to '/var/lib/mysql/' (Errcode: 13 "Permission denied")
2022-06-25  6:28:11 0 [ERROR] Aborting

    shell> /usr/sbin/mariadbd --skip-grant-tables --general-log &

and use the command line tool /usr/bin/mariadb
to connect to the mysql database and look at the grant tables:

    shell> /usr/bin/mysql -u root mysql
    mysql> show tables;

Try 'mysqld --help' if you have problems with paths.  Using
--general-log gives you a log in /var/lib/mysql/ that may be helpful.

The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss

Please check all of the above before submitting a bug report
at https://mariadb.org/jira

2022-06-25 06:27:38-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-06-25 06:27:38-07:00 [Note] [Entrypoint]: Initializing database files

Installation of system tables failed!  Examine the logs in
/var/lib/mysql/ for more information.

The problem could be conflicting information in an external
my.cnf files. You can ignore these by doing:

    shell> /usr/bin/mariadb-install-db --defaults-file=~/.my.cnf

You can also try to start the mysqld daemon with:

    shell> /usr/sbin/mariadbd --skip-grant-tables --general-log &

and use the command line tool /usr/bin/mariadb
to connect to the mysql database and look at the grant tables:

    shell> /usr/bin/mysql -u root mysql
    mysql> show tables;

Try 'mysqld --help' if you have problems with paths.  Using
--general-log gives you a log in /var/lib/mysql/ that may be helpful.

The latest information about mysql_install_db is available at
https://mariadb.com/kb/en/installing-system-tables-mysql_install_db
You can find the latest source at https://downloads.mariadb.org and
the maria-discuss email list at https://launchpad.net/~maria-discuss

Please check all of the above before submitting a bug report
at https://mariadb.org/jira

2022-06-25 06:28:11-07:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.8.3+maria~jammy started.
2022-06-25 06:28:11-07:00 [Note] [Entrypoint]: Initializing database files

Edited June 25, 2022 by lhw1221

GeurtsWebdesign · June 29, 2022

On 6/10/2021 at 9: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:

Now open the console of the container and execute the following commands:
mariadb -u root
FLUSH PRIVILEGES;
SET PASSWORD FOR root@'localhost' = PASSWORD('your_new_password');
Edit the container and remove the "mysqld_safe --skip-grant-tables" part again.

Hi I tried to do this but if i do the FLUSH PRIVILEGES; i get a error:

"MariaDB [(none)]> FLUSH PRIVILEGES;
ERROR 1146 (42S02): Table 'mysql.db' doesn't exist"

and when i try the SET PASSWORD i get also a error:

"MariaDB [(none)]> SET PASSWORD FOR root@'192.168.1.167' = PASSWORD('removed for security');
ERROR 1290 (HY000): The MariaDB server is running with the --skip-grant-tables option so it cannot execute this statement"

what i'm i missing/doing wrong??

Regards Danny

kirk69 · July 9, 2022

Hello,

I installed via Docker mariadb install is ok, but when i try in the console, mariadb -u
i have

root@04fdddaa8c18:/# mariadb -u root
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

error when i connecting with telnet:

Trying 192.168.1.11...
Connected to 192.168.1.11.
Escape character is '^]'.
]
5.5.5-10.5.16-MariaDB-logz#:9Oc##��!'9*c7)eDb@Vsmysql_native_passwordConnection closed by foreign host.

What is wrong please?

best regards

Edited July 9, 2022 by kirk69

mgutt · July 12, 2022

On 7/9/2022 at 3:20 PM, kirk69 said:

root@04fdddaa8c18:/# mariadb -u root
ERROR 1045 (28000): Access denied for user 'root'@'localhost' (using password: NO)

How did you connect to the container? If you did something as follows:

docker exec -it --user root MariaDB-Official /bin/bash

Then you are logged in as root user, but MariaDB still needs a password:

root@0ced77772c12:/# mariadb -p                                   
Enter password: 
Welcome to the MariaDB monitor.  Commands end with ; or \g.
Your MariaDB connection id is 12
Server version: 10.8.3-MariaDB-1:10.8.3+maria~jammy mariadb.org binary distribution

Copyright (c) 2000, 2018, Oracle, MariaDB Corporation Ab and others.

Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.

MariaDB [(none)]> quit
Bye

One-liner:

docker exec -it MariaDB-Official mariadb -u root -p

mgutt · July 12, 2022

On 6/19/2022 at 9:37 PM, YsarKain said:

Nevermind I got it!

The /mnt/user/appdata/mariadb-official/data and /config directories were set to root:root

Do you know why this happened?

mgutt · July 12, 2022

On 6/29/2022 at 3:12 PM, GeurtsWebdesign said:

ERROR 1146 (42S02): Table 'mysql.db' doesn't exist"

Regarding this page I would say your installation got broken:

https://imrecsige.dev/snippets/fix-mariadb-missing-tables-on-manjaro-arch-linux/

The user suggests to remove all files in /var/lib/mysql (which is linked to /mnt/user/appdata/mariadb-official/data), but this contains all important database files, so this should never be done! So I would say your /mnt/user/appdata/mariadb-official/data path is empty or was broken by changing the cache settings of the appdata to in invalid value (like prefer to only while there were still files on the array).

YsarKain · July 16, 2022

On 7/12/2022 at 10:10 AM, mgutt said:

Do you know why this happened?

I believe it was caused by upgrading Unraid, there were a couple other instances where permissions were changed.

kirk69 · July 16, 2022

Hi,
thanks for your help.
I did connect manually the container.
I install it and it's start.

for this code :
docker exec -it MariaDB-Official mariadb -u root -p

i have a error:
Error: No such container: MariaDB-Official

kirk69 · July 16, 2022

I will make a upgrade from 5.05 but i was bad.

before to make the upgrade i make new permissions.

how can i repare the permissions?

thanks

kirk69 · July 16, 2022

I already installed lms plugin ans it's woks fine.

mgutt · July 16, 2022

38 minutes ago, kirk69 said:

Error: No such container: MariaDB-Official

Then you changed the Name of the Container. The default is MariaDB-Official:

image.png.44a4dfc5ae90af0b18cc3795ce1aac16.png

[Support] MariaDB Official

Recommended Posts

Link to comment

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

x3n0n

Autchirion

mgutt

Posted Images

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Link to comment

Join the conversation