> > > Client 1 > [2011-04-26 12:25:07.178381] I [client.c:1883:client_rpc_notify] > 2-distribute-client-1: disconnected > [2011-04-26 12:25:10.188056] I [client.c:1883:client_rpc_notify] > 2-distribute-client-1: disconnected > > Client 2 > [2011-04-26 12:24:57.749822] I [client.c:1883:client_rpc_notify] > 0-distribute-client-1: disconnected > [2011-04-26 12:25:01.753013] I [client.c:1883:client_rpc_notify] > 0-distribute-client-1: disconnected > > It's a case of RPC_CLNT_DISCONNECT according to the code but that alone > doesn't tell me much. What does the '2-distribute-client-1' actually map to? > > 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 -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://gluster.org/pipermail/gluster-users/attachments/20110426/9d2db560/attachment.htm>
