Uploaded image for project: 'Percona XtraDB Cluster'
  1. Percona XtraDB Cluster
  2. PXC-2006

LP #1721090: PXC 5.7.19 node not starting when log_error_verbosity lower than 3

    Details

    • Type: Bug
    • Status: Done
    • Priority: Low
    • Resolution: Cannot Reproduce
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      **Reported in Launchpad by Juan Pablo Arruti last update 15-12-2017 12:08:31

      On Ubuntu 16.04 (Xenial) PXC nodes failed to start when log_error_verbosity variable is lower than 3. It works fine when doing SST, but when it tries to execute IST "mysql-systemd-start pre" it fails because it can't find start recover position in the temporary output file. You can find in the attached file an example when executing "mysql-systemd-start pre" command using log_error_verbosity 2 and 3:

      How to repeat:

      Requirements: 2 node PXC Cluster 5.7.19 on Ubuntu 16.04 (Xenial)

      1) Config log_error_verbosity=2 in one node.
      2) Restart the node.

      root@xenial:/var/lib/mysql# service mysql restart
      Job for mysql.service failed because the control process exited with error code. See "systemctl status mysql.service" and "journalctl -xe" for details.

      There is no much information in systemctl status output:

      root@xenial:/var/lib/mysql# systemctl status mysql.service
      mysql.service - Start and stop the mysql (Percona XtraDB Cluster) daemon
      Loaded: loaded (/lib/systemd/system/mysql.service; enabled; vendor preset: enabled)
      Active: activating (start-pre) since Tue 2017-10-03 17:24:04 UTC; 1s ago
      Process: 5717 ExecStop=/etc/init.d/mysql stop (code=exited, status=0/SUCCESS)
      Process: 10321 ExecStart=/etc/init.d/mysql start (code=exited, status=1/FAILURE)
      Main PID: 5096 (code=killed, signal=KILL); : 10689 (mysql-systemd-s)
      Tasks: 20
      Memory: 194.3M
      CPU: 237ms
      CGroup: /system.slice/mysql.service
      control
      10689 /bin/bash /usr/share/mysql/mysql-systemd-start pre
      10728 /usr/sbin/mysqld --user=mysql --wsrep_recover --log-error=/var/lib/mysql-files/tmp.2KIyLyGjoh.log

      Workaround:

      Set log_error_verbosity variable value to 3 (default value).

      Suggested fix:

      Override log_error_verbosity variable value in my.cnf option file when searching for start recover position.

        Smart Checklist

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                lpjirasync lpjirasync (Inactive)
              • Votes:
                1 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: