ctdb status get UNHEALTHY after node rebooted

Solution Verified - Updated -


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

    Number of nodes:3
    pnn:0         UNHEALTHY (THIS NODE)
    pnn:1         UNHEALTHY
    pnn:2         UNHEALTHY
    hash:0 lmaster:0
    hash:1 lmaster:1
    hash:2 lmaster:2
    Recovery mode:RECOVERY (1)
    Recovery master:2


  • 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, 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