Galera fails to start after rebooting one of the controllers due to 'Unable to detect last known write sequence number'

Solution Verified - Updated -

Issue

  • Galera cluster not starting.
  • How to restart failed galera cluster node
Failed Actions:
* galera_start_0 on overcloud-controller-0 'unknown error' (1): call=220, status=complete, exitreason='Unable to detect last known write sequence number',
    last-rc-change='Fri Jan 22 09:26:03 2016', queued=0ms, exec=2533ms

Environment

  • Red Hat Enterprise Linux OpenStack Platfrom 5.0
  • Red Hat Enterprise Linux OpenStack Platfrom 6.0
  • Red Hat Enterprise Linux OpenStack Platfrom 7.0
  • pacemaker resource-agents

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content