Database configuration: 1 database check is failing
I find this message/warning inappropriate because I did not (intentionally) enable this option. So this is not a configuration issue but rather a choice I made for a small instance.
I’m seeing the same on a test instance running Debian 13 with MariaDB 11.8 from the MariaDB repositories, and I would assume this is a bug or a false positive in this check.
I checked the following:
SHOW REPLICA STATUS\G
-- Empty set
SHOW SLAVE STATUS\G
-- Empty set
SHOW GLOBAL STATUS LIKE 'Slave_running';
-- Slave_running | OFF
SHOW GLOBAL STATUS LIKE 'Slave_IO_Running';
-- Empty set
SHOW GLOBAL STATUS LIKE 'Slave_SQL_Running';
-- Empty set
SHOW VARIABLES LIKE 'read_only';
-- read_only | OFF
SHOW VARIABLES LIKE 'log_bin';
-- log_bin | OFF
SHOW VARIABLES LIKE 'server_id';
-- server_id | 1
I’m not a MariaDB expert, but to me this looks like a normal standalone server with no replication configured. SHOW REPLICA STATUS and SHOW SLAVE STATUS return no replication configuration, read_only is disabled, and binary logging is disabled as well.
I therefore suspect that the check incorrectly assumes that a replica must be configured simply because the Slave_running status exists, and then interprets the returned OFF as an error. As far as I understand it, however, Slave_running can also be present in a standalone setup and simply return OFF when no replication or replicas are configured at all, and therefore should not be treated as an error.
In the context of the forum, marking a post as a “solution” means that the question asked by the OP has been answered in that post, so the thread can be considered resolved. However, this does not necessarily mean that the issue that the thread is about has been resolved.
By the way, as far as I know, anyone can mark a post in a forum thread as ‘solution’, so if you have any new information or a solution to the acual issue, you can post it here and then mark your post as the solution.