Gluster users - Mar 2012 - 3.2.5 client connectivity issues...

Hello gluster-users:

I have installed and configured a 2 brick replication setup and it 
appears to be a successful install. Writes on 1 brick are replicated on 
the other.

My current dilemma is my client will NOT stay connected.

I don't know what information to provide, so I will just give you the
install steps I have taken THIS TIME.

Recipe for this Ubuntu 12.04/32 host in Vbox:
Yes, I realize it's "beta". If using Ubuntu 11.x would be better,
I can
re-install this Vbox host using that.

cd /usr/src
apt-get install -y bison flex g++-4.4 make
wget 
http://download.gluster.com/pub/gluster/glusterfs/LATEST/glusterfs-3.2.5.tar.gz
tar zxf glusterfs-3.2.5.tar.gz && cd glusterfs-3.2.5
./configure && make && make install && ldconfig
vi /usr/local/etc/glusterfs/glusterfs.vol
volume cloud_c9
   type protocol/client
   option transport-type tcp
   option remote-host xx.xxx.xx.xxx
   option remote-subvolume brick
end-volume
mount -t glusterfs xxx.xx.xxx.xxx:cloud_c9 /mnt/cloud_c9 (or
mount -t glusterfs xxx.xx.xxx.xxx:cloud_c9 /mnt/cloud_c9 -o 
log-level=WARNING,log-file=/root/gclient.out)

mount shows it but when/if I df -h, it's gone and /root/gclient.out 
shows http://susepaste.org/97668544 (expires in 6 days).

No firewall rules in the way.
I can ping each and every host from each and every other host and the 
client. I added my IP using "gluster volume set cloud_c9 auth.allow 
xxx.xxx.xxx.xxx" successfully
fuse init (API version 7.17) is loaded.

My Questions are:
What should a "./configure --prefix=..." be to get the logs normalized
(into /var/log/glusterfs/) and the glusterfs to /etc/glusterfs/?'

./configure --prefix=/something --sysconfdir=/etc/something...?

On the bricks, it goes to /var/log/glusterfs...and /etc/glusterfs
but that's a CentOS host. IF the paths are just a Debian-derivative 
"thing" then I'll live with that.

I have to get the BOSS connected next week, or else, this project might 
get sidelined, or delayed, or worse!? (Not really worse)

We are a Cloud Hosting Provider of the AppLogic Grid Computing Software
and I'd really like to be able to provide some storage using glusterfs 
and I don't have the luxury of letting the clients "figure out"
their
connectivity issues.

It's not a marketable feature if the client(s) can't connect.

IT REALLY SHOULD NOT BE THIS DIFFICULT to get a client connected.
And some frequent convos on #gluster indicate that I am not the only 
person having difficulty with this task.

Are bounties allowed to be posted via this list? Because I am seriously
about fed up trying to MAKE this work.

Thank you all for your time.

-- 

JJ / Habitual on #gluster

On Sat, Mar 10, 2012 at 12:12:38AM -0500, JJ wrote:
> We are a Cloud Hosting Provider of the AppLogic Grid Computing Software
> and I'd really like to be able to provide some storage using
> glusterfs and I don't have the luxury of letting the clients
"figure
> out" their connectivity issues.
Then maybe it would be a good idea to test on a supported platform first.

I'm personally looking forward to 12.04 LTS being released, plus a few
months for the inevitable bugs to shake out, but it's definitely in the
"experimental" category right now.

Note also: all the official builds of glusterfs are 64-bit. From what I've
read, 3.2.x *ought* to work on 32-bit:
http://gluster.org/pipermail/gluster-users/2010-August/005175.html
but if your VM platform supports 64-bit images, I'd suggest using that
instead.

FWIW, I had no problem at all getting glusterfs 3.2.x to work on fresh
installs of ubuntu 11.10 64-bit server, connected via 10G ethernet.  I'm
testing on this because (a) the official packages are built for 11.10, and
(b) it's probably the nearest I can get to 12.04 whilst still being a widely
used and tested platform.
http://download.gluster.com/pub/gluster/glusterfs/LATEST/Ubuntu/

I have entries in /etc/hosts for all the nodes, pointing to their IPs on the
10G network (there are separate management interfaces too)

If you can get it to work like this first, it may then be easier to find out
what's happening with your source builds.  Some -dev package missing
perhaps?  OTOH, if it doesn't work from the official 64-bit packages, then
maybe there's some problem with your environment (e.g. DNS, iptables,
apparmor/selinux)

Regards,

Brian.