Re: [Gluster-devel] brick stops responding

2014-01-21 Thread Emmanuel Dreyfus
Hi Any idea of where to look for something to fix here? Emmanuel Dreyfus wrote: > Emmanuel Dreyfus wrote: > > > Now the statedump command completes, but since I restarted the daemons > > in the meantime, the bug is not there anymore. I will restart my tests. > > It came rather quickly from a

Re: [Gluster-devel] brick stops responding

2014-01-20 Thread Emmanuel Dreyfus
On Mon, Jan 20, 2014 at 01:51:10AM -0800, Harshavardhana wrote: > Yeah agreed. Regardless of RPMs - i think these directories's should > be created in "make install". Here is it for master and release-3.5: http://review.gluster.org/6733 http://review.gluster.org/6734 -- Emmanuel Dreyfus m...@net

Re: [Gluster-devel] brick stops responding

2014-01-20 Thread Harshavardhana
> > Yes, this is reasonable. The RPMs contain this directory, but it would > be nicer to have it created during 'make install'. Yeah agreed. Regardless of RPMs - i think these directories's should be created in "make install". -- Religious confuse piety with mere ritual, the virtuous confuse re

Re: [Gluster-devel] brick stops responding

2014-01-20 Thread Niels de Vos
On Sun, Jan 19, 2014 at 05:08:22AM +0100, Emmanuel Dreyfus wrote: > Emmanuel Dreyfus wrote: > > > # gluster volume statedump gfs35b1 all > > volume statedump: failed: Commit failed on debacle. Please check log file > for details. > > I found why. The log message is meaningless, it fails because

Re: [Gluster-devel] brick stops responding

2014-01-18 Thread Emmanuel Dreyfus
Emmanuel Dreyfus wrote: > Now the statedump command completes, but since I restarted the daemons > in the meantime, the bug is not there anymore. I will restart my tests. It came rather quickly from another brick. I assume the condition comes after some time, and it was ready to happen here. [2

Re: [Gluster-devel] brick stops responding

2014-01-18 Thread Emmanuel Dreyfus
Emmanuel Dreyfus wrote: > # gluster volume statedump gfs35b1 all > volume statedump: failed: Commit failed on debacle. Please check log file for details. I found why. The log message is meaningless, it fails because /var/run/gluster does not exist. Would the fix below be reasonable? Now the st

Re: [Gluster-devel] brick stops responding

2014-01-16 Thread Emmanuel Dreyfus
Pranith Kumar Karampuri wrote: > Could you provide statedumps of the bricks and mounts please. # gluster volume statedump gfs35b1 all volume statedump: failed: Commit failed on debacle. Please check log file for details. glusterd log on server debacle: [2014-01-17 04:55:17.855158] E [gluster

Re: [Gluster-devel] brick stops responding

2014-01-16 Thread Pranith Kumar Karampuri
Could you provide statedumps of the bricks and mounts please. Just curious what does the test do? Pranith - Original Message - > From: "Emmanuel Dreyfus" > To: gluster-devel@nongnu.org > Sent: Thursday, January 16, 2014 8:11:36 PM > Subject: [Gluster-devel]

[Gluster-devel] brick stops responding

2014-01-16 Thread Emmanuel Dreyfus
Hi With 3.5beta1, at some point I have a brick that stops responding, and reconection never happens. Client log: [2014-01-16 12:57:47.896907] C [client-handshake.c:127:rpc_client_ping_timer_expired] 0-gfs35b1-client-0: server 192.0.2.99:49152 has not responded in the last 42 seconds, disconn