Uploaded image for project: 'MariaDB Server'
  1. MariaDB Server
  2. MDEV-10491

log_error does not take precedence over syslog in wsrep_sst_xtrabackup-v2

Details

    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?

      Attachments

        Activity

          Ascending order - Click to sort in descending order
          GeoffMontee Geoff Montee (Inactive) added a comment -

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

          GeoffMontee Geoff Montee (Inactive) added a comment - Patch: https://github.com/MariaDB/server/pull/209
          nirbhay_c Nirbhay Choubey (Inactive) added a comment -

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

          nirbhay_c Nirbhay Choubey (Inactive) added a comment - As we are moving more toward systemd, so let's better stick with the existing behavior.

          People

            nirbhay_c Nirbhay Choubey (Inactive)
            GeoffMontee Geoff Montee (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Git Integration

                Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.