Why gstatus command returns UNHEALTHY?

Solution Verified - Updated -

Issue

  • Why gstatus command returns UNHEALTHY even RHGS is healthy?
# gstatus -a

Updating volume information

     Status: UNHEALTHY                     15.00 GiB(raw used)
   Glusterfs: 3.12.2                        14.00 GiB(usable from volumes)
  OverCommit: No                Snapshots:   0

   Nodes       :  3/  3       Volumes:   1 Up
   Self Heal   :  0/  3                  0 Up(Degraded)
   Bricks      :  3/  3                  0 Up(Partial)
   Connections :  3/   9                     0 Down

Volume Information


    glfs1            UP - 3/3 bricks up - Replicate
                     Capacity: (36% used) 5.00 GiB/14.00 GiB (used/total)
                     Snapshots: 0
                     Self Heal:  0/ 3
                     Tasks Active: None
                     Protocols: glusterfs:on  NFS:off  SMB:on
                     Gluster Connectivty: 3 hosts, 9 tcp connections


Status Messages
  - Cluster is HEALTHY, all_bricks checks successful

Environment

  • Red Hat Gluster Storage 3.4

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