ctdb status get UNHEALTHY after node rebooted

Solution Verified - Updated -

Issue

  • After reboot gluster server nodes, CTDB didn't start normally and all of the nodes status is UNHEALTHY

    Number of nodes:3
    pnn:0 9.0.0.51         UNHEALTHY (THIS NODE)
    pnn:1 9.0.0.52         UNHEALTHY
    pnn:2 9.0.0.53         UNHEALTHY
    Generation:INVALID
    Size:3
    hash:0 lmaster:0
    hash:1 lmaster:1
    hash:2 lmaster:2
    Recovery mode:RECOVERY (1)
    Recovery master:2
    

Environment

  • Red Hat Enterprise Linux Server release 7.3
  • Red Hat Gluster Storage Server 3.1 Update 3 and later

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.