Affects Version/s: None
Fix Version/s: None
**Reported in Launchpad by Roman Kalab last update 04-12-2017 06:27:17
i have the problem with Percona XtraDB Cluster. Sometimes after clean shutdown, sometimes after crash the (random) node(s) of the cluster are not able to start.
Commandline used: "service mysql start" or "/usr/bin/mysqld_safe -v"
mysqld Ver 5.7.19-17-57 for debian-linux-gnu on x86_64 (Percona XtraDB Cluster (GPL), Release rel17, Revision 35cdc81, WSREP version 29.22, wsrep_29.22)
Output of the "mysqld_safe -v":
- /usr/bin/mysqld_safe -v
2017-11-16T17:37:18.048298Z mysqld_safe Logging to '/var/log/mysql/error.log'.
Logging to '/var/log/mysql/error.log'.
2017-11-16T17:37:18.089616Z mysqld_safe Starting mysqld daemon with databases from /var/lib/mysql
2017-11-16T17:37:18.113637Z mysqld_safe WSREP: Running position recovery with --log_error='/var/lib/mysql/wsrep_recovery.mzgffn' --pid-file='/var/lib/mysql/puma-recover.pid'
Then the process dies, with exit code 0. The error log is not even created, so no info there. WSREP recovery log attached. Syslog contains no data.
The situation can be solved by removing whole content of "/var/lib/mysql/". Then the server does full SST and starts normally.
Please let me know if you need any other information.