Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Glusterfs, while being a nice distributed filesystem, provides almost no way to monitor it's integrity. Servers can come and go, bricks might get stale or fail and I afraid to know about that when it is probably too late.

Recently we had an strange failure when everything appeared working, but one brick fell out from the volume (found by pure coincidence).

Is there a simple and reliable way (cron script?) that will let me know about health status of my GlusterFS 3.2 volume?

share|improve this question
For now we use an dirty shell script based monitoring: – Arie Skliarouk Aug 1 '11 at 16:56
Have a look at – quanta Aug 1 '11 at 17:12
I checked the and it looks like it is for old versions of glusterfs, which were configuration-file controlled. I will clarify my question to represent glusterfs 3.2. – Arie Skliarouk Aug 3 '11 at 13:34

This has been a request to the GlusterFS developers for a while now and there is nothing out-of-the-box solution you can use. However, with a few scripts it's not impossible.

Pretty much entire Gluster system is managed by a single gluster command and with a few options, you can write yourself health monitoring scripts. See here for listing info on bricks and volumes --

To monitor performance, look at this link --

UPDATE: Do consider upgrading to

You are always better off with being on the latest release since they seem to have more bug fixes and well supported. Ofcourse, run your own tests before moving to a newer release -- :)

There is an admin guide with specific section for monitoring your GlusterFS 3.3 installation in Chapter 10 --

See here for another nagios script --

share|improve this answer
Thanks Chida, I guess what's got me hung up is that some folks ( are monitoring gluster via the proc table ('--with-brick', etc) and logfiles (egrep ' E ' for error), and some people are using the CLI and I have no idea which is more likely to accurately report gluster's state. – r_2 Aug 14 '12 at 16:44
I'd recommend using the CLI since that's the one GlusterFS recommends and is bound to be up-to-date. – Chida Aug 14 '12 at 16:51

There is a nagios plugin available for monitoring. You may have to edit it for your version though.

share|improve this answer

@Arie Skliarouk, your has a typo—on the last line, you grep for exitst instead of exist. I went ahead and rewrote it to be a bit more compact, and to remove the requirement for a temporary file.


# Ensure that all peers are connected
gluster peer status | grep -q Disconnected && echo "Peer disconnected." && exit 1

# Ensure that all bricks have a running log file (i.e., are sending/receiving)
for vol in $(gluster volume info | awk '/Volume Name/ {print $3}'); do
  for brick in $(gluster volume info "$vol" | awk '/^Brick[0-9]*:/ {print $2}'); do
    gluster volume log locate "$vol" "$brick";
done |
 grep -qE "does not (exist|exitst)" &&
 echo "Log file missing - $vol/$brick ." &&
 exit 1
share|improve this answer
The "exitst" typo is what is written in the logs. I don't buy the "compact" advantage - the script is much harder to understand when lines are overloaded. Temporary file is cheap price to pay for the easy-to-understand code. – Arie Skliarouk Feb 20 '13 at 16:13
@ArieSkliarouk: Updated to cover both cases, but be forewarned that the relevant message was removed in November 2011; see… . Thus, this is likely not going to work on newer Glusters. If you find the shorter code harder to understand, that's fine, but it is significantly more robust than using a temporary file, so consider refactoring it for readability instead of dismissing it for perceived lack of that attribute. – BMDan Mar 18 '13 at 15:54

I was able to configure the nagios monitoring for glusterfs as mentioned below :

share|improve this answer
Because links go dead over time, we would prefer it if you could include the essence of the answer here on ServerFault. – Ladadadada Nov 19 '14 at 13:12

Please check the attached script at for gluster 3.3; it's probably easily adaptable to gluster 3.2.


# This Nagios script was written against version 3.3 of Gluster.  Older
# versions will most likely not work at all with this monitoring script.
# Gluster currently requires elevated permissions to do anything.  In order to
# accommodate this, you need to allow your Nagios user some additional
# permissions via sudo.  The line you want to add will look something like the
# following in /etc/sudoers (or something equivalent):
# Defaults:nagios !requiretty
# nagios ALL=(root) NOPASSWD:/usr/sbin/gluster peer status,/usr/sbin/gluster volume list,/usr/sbin/gluster volume heal [[\:graph\:]]* info
# That should give us all the access we need to check the status of any
# currently defined peers and volumes.

# define some variables
ME=$(basename -- $0)
PEERSTATUS="peer status"
VOLLIST="volume list"
VOLHEAL1="volume heal"

# check for commands
for cmd in $SUDO $PIDOF $GLUSTER; do
    if [ ! -x "$cmd" ]; then
        echo "$ME UNKNOWN - $cmd not found"
        exit 3

# check for glusterd (management daemon)
if ! $PIDOF glusterd &>/dev/null; then
    echo "$ME CRITICAL - glusterd management daemon not running"
    exit 2

# check for glusterfsd (brick daemon)
if ! $PIDOF glusterfsd &>/dev/null; then
    echo "$ME CRITICAL - glusterfsd brick daemon not running"
    exit 2

# get peer status
peerstatus="peers: "
for peer in $(sudo $GLUSTER $PEERSTATUS | grep '^Hostname: ' | awk '{print $2}'); do
    state=$(sudo $GLUSTER $PEERSTATUS | grep -A 2 "^Hostname: $peer$" | grep '^State: ' | sed -nre 's/.* \(([[:graph:]]+)\)$/\1/p')
    if [ "$state" != "Connected" ]; then
    peerstatus+="$peer/$state "

# get volume status
volstatus="volumes: "
for vol in $(sudo $GLUSTER $VOLLIST); do
    for entries in $(sudo $GLUSTER $VOLHEAL1 $vol $VOLHEAL2 | grep '^Number of entries: ' | awk '{print $4}'); do
        if [ "$entries" -gt 0 ]; then
            let $((thisvolerror+=entries))
    volstatus+="$vol/$thisvolerror unsynchronized entries "

# drop extra space

# set status according to whether any errors occurred
if [ "$peererror" ] || [ "$volerror" ]; then

# actual Nagios output
echo "$ME $status $peerstatus $volstatus"

# exit with appropriate value
if [ "$peererror" ] || [ "$volerror" ]; then
    exit 2
    exit 0
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.