Author Topic: MySQL - BAD CONFIGURATION DETECTED  (Read 1834 times)

0 Members and 1 Guest are viewing this topic.

Offline
*
MySQL - BAD CONFIGURATION DETECTED
« on: November 15, 2022, 08:36:24 PM »
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

Offline
*
Re: MySQL - BAD CONFIGURATION DETECTED
« Reply #1 on: April 02, 2023, 02:12:50 PM »
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...

Offline
****
Re: MySQL - BAD CONFIGURATION DETECTED
« Reply #2 on: April 02, 2023, 02:39:46 PM »
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

Offline
*
Re: MySQL - BAD CONFIGURATION DETECTED
« Reply #3 on: March 23, 2024, 08:34:56 PM »
Similar issue. I didn't even do anything and suddenly getting this error and updating is also failing :(

Offline
****
Re: MySQL - BAD CONFIGURATION DETECTED
« Reply #4 on: March 24, 2024, 04:19:32 AM »
have you tuned your MySQL configuration or are you running defaults? Posting your / etc / my.cnf and version information would be helpful...