hi james! I dont understand, what you like to tell me? I cannot mention more as I did - the glusterfsd dies before I can configure anything: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2293 since version 3.1.x you have to use the "gluster" command to configure your cluster nodes and your volumes regards markus ------------------------------ Message: 8 Date: Thu, 20 Jan 2011 09:41:20 -0500 From: "Burnash, James"<jburnash at knight.com> Subject: Re: glusterfs 3.1.1 troubles on SLES11 SP1 To:"gluster-users at gluster.org" <gluster-users at gluster.org> Message-ID: <9AD565C4A8561349B7227B79DDB988736314F31992 at EXCHANGE3.global.knight.com> Content-Type: text/plain; charset="utf-8" ?Hi Markus. You don't mention anything that would put you in this scenario - but when I was testing a newer version of gluster on one set of boxes while running a different version in production, requests from production GlusterFS clients for production resources were received by the testing version of GlusterFS, and it appears that those resources not being available immediately caused the glusterd daemons to exit with no log information to that effect. I was using the 3.0.x versions at the time and have not tested this with the 3.1.x versions. This mystified and frustrated me for a while before I found it on my own. I did make a comment on this list about the "no error message" part several months ago. Hopefully this will be helpful to you and others. James Burnash, Unix Engineering
