Details
-
Bug
-
Status: Closed (View Workflow)
-
Major
-
Resolution: Fixed
-
10.3.24, 10.4.14, 10.5.5
-
None
-
Debian, Ubuntu
Description
wsrep_sst_mariabackup has the following lines:
if [[ $ssyslog -ne -1 ]];then
|
if $MY_PRINT_DEFAULTS mysqld_safe | tr '_' '-' | grep -q -- "--syslog";then
|
ssyslog=1
|
fi
|
fi
|
So when it finds a
{[mysqld_safe]}section in the configuration files with a
{syslog}option, it will also make the SST script log everything to syslog, regardless of actual
{[sst]}configuration section settings.
Now the problem is that this even happens when
{mysqld_safe} isn't actually used, e.g. as someone switched to using SystemD, but didn't bother to remove the {mysqld_safe}settings from the configuration.
Especially if that someone is us, and still delivers a /etc/mysql/conf.d/mysqld_safe_syslog.cnf file ( or /etc/mysql/mariadb.conf.d/50-mysqld_safe.cnf in 10.5 packages) with contents
[mysqld_safe]
|
skip_log_error
|
syslog
|
as part of Debian and Ubuntu packages.
Due to this files content the [sst] settings for sst-syslog, sst-log-archive and sst-log-archive can't be changed. sst-syslog will always be enabled, and the later two settings are ignored when it is. Even explicitly setting
{sst-syslog=0}whill not change this due to the sst script logic.
Attachments
Issue Links
- is part of
-
MDEV-25669 SST scripts should check all server groups in configuration files
- Closed