[MDEV-10491] log_error does not take precedence over syslog in wsrep_sst_xtrabackup-v2 Created: 2016-08-03  Updated: 2016-10-24  Resolved: 2016-10-24

Status: Closed
Project: MariaDB Server
Component/s: Galera, Galera SST, wsrep
Affects Version/s: 10.0.24-galera
Fix Version/s: N/A

Type: Bug Priority: Major
Reporter: Geoff Montee (Inactive) Assignee: Nirbhay Choubey (Inactive)
Resolution: Won't Do Votes: 0
Labels: galera, sst, wsrep


 Description   

If the syslog option of mysqld_safe and the log_error mysqld option are both set, the log_error option takes precedence, so mysqld will log its log entries to its own log file, not to syslog.

However, wsrep_sst_xtrabackup-v2 does not have the same behavior. If the syslog option of mysqld_safe is enabled, it will log to the syslog, regardless of whether log_error is also enabled. You can see the responsible check here:

https://github.com/MariaDB/server/blob/370a2cbe96e026fdb8966d8e58e7c93f75597cb8/scripts/wsrep_sst_xtrabackup-v2.sh#L335

Would this be considered a bug, or is this acceptable behavior?



 Comments   
Comment by Geoff Montee (Inactive) [ 2016-08-03 ]

Patch: https://github.com/MariaDB/server/pull/209

Comment by Nirbhay Choubey (Inactive) [ 2016-10-24 ]

As we are moving more toward systemd, so let's better stick with the existing behavior.

Generated at Thu Feb 08 07:42:37 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.