[MDEV-23911] wsrep_sst_mariabackup acts on mysqld_settings even when it's not used Created: 2020-10-07  Updated: 2022-02-18  Resolved: 2022-02-18

Status: Closed
Project: MariaDB Server
Component/s: Galera SST
Affects Version/s: 10.3.24, 10.4.14, 10.5.5
Fix Version/s: 10.6.1, 10.2.39, 10.3.30, 10.4.20, 10.5.11

Type: Bug Priority: Major
Reporter: Hartmut Holzgraefe Assignee: Julius Goryavsky
Resolution: Fixed Votes: 0
Labels: None
Environment:

Debian, Ubuntu

Issue Links:
PartOf
is part of MDEV-25669 SST scripts should check all server g... Closed

 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.

 Comments   
Comment by Julius Goryavsky [ 2022-02-18 ]

Already fixed by MDEV-25669

Generated at Thu Feb 08 09:26:00 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.