MySQL - BAD CONFIGURATION DETECTED

I notice when I log in as an administrator I am getting this error:

Code: [Select]
Danger: MySQL - BAD CONFIGURATION DETECTED
MySQL bad configuration detected, check from the console by using mysql command !!!

This is my MySQL configuration file contents:

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Disabling symbolic-links is recommended to prevent assorted security risks
symbolic-links=0
# Settings user and group are ignored when systemd is used.
# If you need to run mysqld under a different user or group,
# customize your systemd unit file for mariadb according to the
# instructions in http://fedoraproject.org/wiki/Systemd

[mysqld_safe]
log-error=/var/log/mariadb/mariadb.log
pid-file=/var/run/mariadb/mariadb.pid

#
# include all files from the config directory
#
!includedir /etc/my.cnf.d

Too bad there's no reply. I have the same issue.
I love that there would be a warning of misconfiguration, but not an iota of information about what the issue is...

Is that the default Fedora my.cnf?

Did you run mysql_secure_installation?

Here is a sample my.cnf, lightly tuned for WP and other CMS platforms:

Code: [Select]

[mysqld]
performance-schema=0
max_connections=100
max_user_connections=75
query_cache_size=32M
skip-external-locking
key_buffer_size=32M
table_open_cache=128
sort_buffer_size=512K
net_buffer_length=8K
read_buffer_size=256K
read_rnd_buffer_size=512K
myisam_sort_buffer_size=16M
innodb_file_per_table=1
tmp_table_size=32M
max_heap_table_size=32M
thread_cache_size=4
open_files_limit=10000
local-infile=0
max_allowed_packet=500M

# InnoDB
innodb_locks_unsafe_for_binlog=1
innodb_fast_shutdown = 1
# Recovery mode options
#innodb_force_recovery = 5
#innodb_purge_threads=0

#
# This group is read both both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d

Similar issue. I didn't even do anything and suddenly getting this error and updating is also failing

have you tuned your MySQL configuration or are you running defaults? Posting your / etc / my.cnf and version information would be helpful...

Oh shit, here we go again:

MySQL bad configuration detected, check from the console by using mysql command !!!

Code: [Select]

#
# This group is read both by the client and the server
# use it for options that affect everything
#
[client-server]

#
# include *.cnf from the config directory
#
!includedir /etc/my.cnf.d

server.cnf
#
# These groups are read by MariaDB server.
# Use it for options that only the server (but not clients) should see
#

# this is read by the standalone daemon and embedded servers
[server]

# This group is only read by MariaDB servers, not by MySQL.
# If you use the same .cnf file for MySQL and MariaDB,
# you can put MariaDB-only options here
[mariadb]

# This group is read by both MariaDB and MySQL servers
[mysqld]

#
# * Galera-related settings
#
[galera]
# Mandatory settings
#wsrep_on=ON
#wsrep_provider=
#wsrep_cluster_address=
#binlog_format=row
#default_storage_engine=InnoDB
#innodb_autoinc_lock_mode=2
#
# Allow server to accept connections on all interfaces.
#
#bind-address=0.0.0.0
#
# Optional setting
#wsrep_slave_threads=1
#innodb_flush_log_at_trx_commit=0

# this is only for embedded server
[embedded]

# This group is only read by MariaDB servers, not by MySQL.
# If you use the same .cnf file for MySQL and MariaDB,
# you can put MariaDB-only options here
[mariadb]

# This group is only read by MariaDB-10.11 servers.
# If you use the same .cnf file for MariaDB of different versions,
# use this group for options that older servers don't understand
[mariadb-10.11]
Checked all other files, all of them are with empty sections, so everything by default

Version is:
mariadb from 11.4.5-MariaDB, client 15.2 for Linux (x86_64) using  EditLine wrapper

Check the config file (or its directories) isn't group or other writeable but also make sure the file is readable by the mysql user. The easy way to check the last bit is with

Code: [Select]

sudo -u mysql my_print_defaults --mariadbd so see what configuration options are read. Also run

Code: [Select]

journalctl -u mariadb.service -n 30 -- failing to read configuration files is normally a warning.