PXC 5.7.19 node not starting when log_error_verbosity lower than 3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC |
New
|
Undecided
|
EvgeniyPatlan |
Bug Description
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-
How to repeat:
Requirements: 2 node PXC Cluster 5.7.19 on Ubuntu 16.04 (Xenial)
1) Config log_error_
2) Restart the node.
root@xenial:
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:
● mysql.service - Start and stop the mysql (Percona XtraDB Cluster) daemon
Loaded: loaded (/lib/systemd/
Active: activating (start-pre) since Tue 2017-10-03 17:24:04 UTC; 1s ago
Process: 5717 ExecStop=
Process: 10321 ExecStart=
Main PID: 5096 (code=killed, signal=KILL); : 10689 (mysql-systemd-s)
Tasks: 20
Memory: 194.3M
CPU: 237ms
CGroup: /system.
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.
tags: | added: i206732 |
PXC node can be started with the log_error_ verbosity= 2 through binary. Possibly a packaging problem.