Aha, thank you very much. Checking back to the node in question then I find 'service gluster status' returning ok. Although the process controlling my volume wasn't running (maybe status could be a little more thorough), the error I found was: [2011-04-26 11:10:03.461515] W [glusterfsd.c:700:cleanup_and_exit] (-->/lib64/libc.so.6(clone+0x6d) [0x7fa620587c2d] (-->/lib64/libpthread.so.0(+0x6ccb) [0x7fa620849ccb] (-->/opt/glusterfs/3.2.0/sbin/glusterfsd(glusterfs_sigwaiter+0xd5) [0x405bf5]))) 0-: received signum (15), shutting down I've done a restart and now have a working node again. Thanks again Amar, > 2-distribute-client-1 -> 2 here (ie, the first number) means the graph > id. (Graph id changes when ever some changes in volume file happens). > 'distribute' is your volume name, and if you go through the volume > file, (which will be logged in log file too), you can see a > protocol/client volume with name 'distribute-client-1'. > > See its definition, and get remote-host IP and check if the brick is > running in that particular node. > > Mean time, with 3.2.x onwards these logs will be changed to print the > IP:port of the remote host too, so one can get to the remote machine > without much of greping around. > > Regards, > Amar > >
