XtraDB CLuster can not start after restart server

Bug #1691905 reported by duc
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Expired
Undecided
Unassigned

Bug Description

OS: CentOS 7.x 64 bit, After restart servers I can not start XtraDB Cluster:
[root@iti-vn-82-vm ~]# sestatus
SELinux status: disabled
[root@iti-vn-82-vm ~]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; disabled; vendor preset: enabled)
   Active: inactive (dead)
     Docs: man:firewalld(1)

[root@iti ~]# systemctl start mysql@bootstrap
Job for <email address hidden> failed because the control process exited with error code. See "systemctl status <email address hidden>" and "journalctl -xe" for details.
[root@iti-vn-82-vm ~]# systemctl status mysql@bootstrap -1
systemctl: invalid option -- '1'
[root@iti ~]# systemctl status mysql@bootstrap -l
● <email address hidden> - Percona XtraDB Cluster with config /etc/sysconfig/mysql.bootstrap
   Loaded: loaded (/usr/lib/systemd/system/mysql@.service; disabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2017-05-18 11:21:10 ICT; 21h ago
  Process: 17111 ExecStopPost=/usr/bin/mysql-systemd stop-post (code=exited, status=0/SUCCESS)
  Process: 17069 ExecStop=/usr/bin/mysql-systemd stop (code=exited, status=2)
  Process: 16913 ExecStartPost=/usr/bin/mysql-systemd start-post $MAINPID (code=exited, status=1/FAILURE)
  Process: 16912 ExecStart=/usr/bin/mysqld_safe --basedir=/usr ${EXTRA_ARGS} (code=exited, status=0/SUCCESS)
  Process: 16852 ExecStartPre=/usr/bin/mysql-systemd start-pre (code=exited, status=0/SUCCESS)
 Main PID: 16912 (code=exited, status=0/SUCCESS)

May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: Fatal error in defaults handling. Program aborted
May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: [93B blob data]
May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: Fatal error in defaults handling. Program aborted
May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: [93B blob data]
May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: Fatal error in defaults handling. Program aborted
May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: WARNING: mysql pid file /var/lib/mysql/iti-vn-82-vm.pid empty or not readable
May 18 11:21:10 iti-vn-82-vm mysql-systemd[17111]: WARNING: mysql may be already dead
May 18 11:21:10 iti-vn-82-vm systemd[1]: Failed to start Percona XtraDB Cluster with config /etc/sysconfig/mysql.bootstrap.
May 18 11:21:10 iti-vn-82-vm systemd[1]: Unit <email address hidden> entered failed state.
May 18 11:21:10 iti-vn-82-vm systemd[1]: <email address hidden> failed.

Tags: cluster xtradb
Revision history for this message
Jericho Rivera (jericho-rivera) wrote :

Please share full mysql error log, my.cnf and exact Percona XtraDB Cluster version used.

Changed in percona-server:
status: New → Incomplete
affects: percona-server → percona-xtradb-cluster
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Percona XtraDB Cluster because there has been no activity for 60 days.]

Changed in percona-xtradb-cluster:
status: Incomplete → Expired
Revision history for this message
Shahriyar Rzayev (rzayev-sehriyar) wrote :

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXC-1979

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.