5.6.35-26.20-1.xenial fails to start after reboot

Bug #1672641 reported by Robert Sanderson
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Percona XtraDB Cluster moved to https://jira.percona.com/projects/PXC
Fix Released
Undecided
EvgeniyPatlan

Bug Description

After updating 5.6.34-26.19-1.xenial to 5.6.35-26.20-1.xenial Percona XtraDB Cluster started properly, but, after a reboot it did not start. I found that the /var/run/mysqld/ directory was not being (re)created. If I create the /var/run/mysqld/ directory manually, mysql will start.

The packages installed are:
ii percona-release 0.1-4.xenial
ii percona-xtrabackup 2.3.7-2.xenial
ii percona-xtradb-cluster-56 5.6.35-26.20-1.xenial
ii percona-xtradb-cluster-client-5.6 5.6.35-26.20-1.xenial
ii percona-xtradb-cluster-common-5.6 5.6.35-26.20-1.xenial
ii percona-xtradb-cluster-galera-3 3.20-1.xenial
ii percona-xtradb-cluster-galera-3.x 3.20-1.xenial
ii percona-xtradb-cluster-server-5.6 5.6.35-26.20-1.xenial

Changed in percona-xtradb-cluster:
assignee: nobody → EvgeniyPatlan (evgeniy-patlan)
Revision history for this message
Roman Pertl (roock) wrote :

Same Issue on Debian Wheezy and Jessie on several mysql-xdb servers.

Revision history for this message
Hrvoje Matijakovic (hrvojem) wrote :

New packages have been pushed to repositories with incremented package version (-2) to address this bug.

Changed in percona-xtradb-cluster:
status: New → Fix Released
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-1961

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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