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 of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In
Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.