<div dir="ltr">Funny things going on...<div><br></div><div>Let's start from the beginning: </div><div><br></div><div>I am not familiar with ubuntu's way of starting and stopping a service, but what you did on iptables was adding a line that, in theory, allows any connection to the server. </div>
<div><br></div><div>Just in case, really, REALLY disable iptables.</div><div><br></div><div>on a Red hat-based environment, you'd do something like:</div><div><br></div><div>service iptables stop</div><div>chkconfig iptables off</div>
<div><br></div><div>If you can do that, it can help.</div><div><br></div><div>Now, on the UBUNTU SERVER running gluster, try:</div><div><br></div><div>mkdir -p /mnt/glustervol0</div><div><br></div><div>mount -t nfs localhost:/gv0 /mnt/glustervol0</div>
<div><br></div><div>This should work.</div><div><br></div><div>Next, still on your ubuntu server, do:</div><div><br></div><div>df -h </div><div>(just to make sure you volume is there)</div><div><br></div><div>Let's do this first, to see if gluster and the server are behaving the way they should.</div>
<div><br></div><div>KR, </div><div><br></div><div>Carlos</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Tue, Mar 11, 2014 at 8:29 AM, Daniel Baker <span dir="ltr"><<a href="mailto:info@collisiondetection.biz" target="_blank">info@collisiondetection.biz</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear Carlos<br>
<br>
I opened up the glusterfs server firewall to accept all connections<br>
from my computer :<br>
<br>
iptables -I INPUT -p all -s 192.168.100.209 -j ACCEPT<br>
<br>
And on my computer to accept all connections from the glusterfs server.<br>
<br>
When I try showmount -e localhost<br>
<br>
Export list for localhost:<br>
/gv0 *<br>
<br>
<br>
When I try the same command from my computer I get:<br>
<br>
<br>
showmount -e 192.168.100.170<br>
Export list for <a href="http://192.168.100.170" target="_blank">192.168.100.170</a>:<br>
/gv0 *<br>
<br>
<br>
When I try from my computer :<br>
<div class=""><br>
sudo mount -t nfs 192.168.100.170:/gv0 /mnt/export<br>
<br>
</div>mount.nfs: mount point /mnt/export does not exist<br>
<br>
And when I try from my computer:<br>
<div class=""><br>
sudo mount -t glusterfs 192.168.100.170:/gv0 /mnt/export<br>
</div><div class="">Usage: mount.glusterfs <volumeserver>:<volumeid/volumeport> -o<br>
<options> <mountpoint><br>
Options:<br>
man 8 mount.glusterfs<br>
<br>
To display the version number of the mount helper:<br>
mount.glusterfs --version<br>
<br>
<br>
</div>So it looks like the volume is there but it doesn’t see the mount point ?<br>
<br>
Then I changed tac. I found this tutorial :<br>
<a href="http://www.howtoforge.com/high-availability-storage-with-glusterfs-3.2.x-on-debian-wheezy-automatic-file-replication-mirror-across-two-storage-servers" target="_blank">http://www.howtoforge.com/high-availability-storage-with-glusterfs-3.2.x-on-debian-wheezy-automatic-file-replication-mirror-across-two-storage-servers</a><br>
<br>
<br>
I issued this command on my client computer:<br>
<br>
mkdir /mnt/glusterfs<br>
<br>
mount.glusterfs <a href="http://192.168.100.170/gv0" target="_blank">192.168.100.170/gv0</a> /mnt/glusterfs<br>
<br>
<br>
This time I did not receive any messages about how to use the gluster<br>
commads. So it looked ok.<br>
<br>
However when I issue :<br>
<br>
mount<br>
<br>
I get this :<br>
<br>
/dev/sda2 451G 421G 7.2G 99% /<br>
udev 3.8G 4.0K 3.8G 1% /dev<br>
tmpfs 1.6G 1008K 1.6G 1% /run<br>
none 5.0M 0 5.0M 0% /run/lock<br>
none 3.8G 748K 3.8G 1% /run/shm<br>
cgroup 3.8G 0 3.8G 0% /sys/fs/cgroup<br>
/dev/sda1 93M 2.1M 91M 3% /boot/efi<br>
/home/kam270/.Private 451G 421G 7.2G 99% /home/kam270<br>
<br>
No mount point to server.<br>
<br>
Maybe I need to try adding hostnames in my /etc/hosts ?<br>
<br>
<br>
Thanks,<br>
<div><div class="h5"><br>
Dan<br>
<br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 4<br>
> Date: Fri, 7 Mar 2014 17:56:08 +0100<br>
> From: Carlos Capriotti <<a href="mailto:capriotti.carlos@gmail.com">capriotti.carlos@gmail.com</a>><br>
> To: Daniel Baker <<a href="mailto:info@collisiondetection.biz">info@collisiondetection.biz</a>><br>
> Cc: gluster-users <<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>><br>
> Subject: Re: [Gluster-users] Testing Gluster 3.2.4 in VMware<br>
> Message-ID:<br>
> <CAMShz32JK=B+O+cL3Ej-hxSsQ1s06U0JOiP9GgSkdjfq1=<a href="mailto:0s-Q@mail.gmail.com">0s-Q@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> Hello, Daniel.<br>
> I am also testing gluster on vmware; in my application, it will be a<br>
> secondary datastore for VM images.<br>
><br>
> So far, I've hit a couple of brick walls, like, for instance, VMware not<br>
> reading volumes created as striped, or striped + replicated. It simply sits<br>
> there, trying, four hours, without errors on either sides.<br>
><br>
> But your current configuration WILL work.<br>
><br>
> As a suggestion, to begin with your troubleshooting, try disabling firewall<br>
> and SElinux. nothing to do with your current problem, BUT will matter in<br>
> the near future. After you are sure all works, go back an re-enable/ fine<br>
> tune them.<br>
><br>
> Now to your problem...<br>
><br>
> Your first syntax seem to be a bit off,unless it is a typo;<br>
><br>
> sudo mount.glusterfs 192.168.100.170:gv0 /mnt/export<br>
><br>
> you see, there is a slash missing after. It should read<br>
><br>
> sudo mount.glusterfs 192.168.100.170:/gv0 /mnt/export<br>
><br>
> For the second case, you did not post the error message, so I can only<br>
> suggest you try copying/pasting this:<br>
><br>
> sudo mount -t glusterfs 192.168.100.170:/gv0 /mnt/export<br>
><br>
> Now, here is another trick: try mounting wit nfs:<br>
><br>
> First, make sure your NFS share is really being shared:<br>
><br>
> # showmount -e 192.168.100.170<br>
><br>
> Alternatively, if you are on one of the gluster servers, just for testing,<br>
> you may try:<br>
><br>
> # showmount -e localhost<br>
><br>
> Make sure your gluster volume is REALLY called gv0.<br>
><br>
> Now you can try mounting with:<br>
><br>
> sudo mount -t nfs 192.168.100.170:/gv0 /mnt/export<br>
><br>
> Again, if you are on one of the servers, try<br>
><br>
> sudo mount -t nfs localhost:/gv0 /mnt/export<br>
><br>
> You might want to "sudo su" to run everything all commands as root, without<br>
> the hassle of sudoing everything.<br>
><br>
> Give it a try. If nfs works, go for it anyway; It is your only option for<br>
> VMware/esxi anyway.<br>
><br>
> There are a few more advanced steps on esxi and on gluster, but let's get<br>
> it to work first, right ?<br>
><br>
> Cheers,<br>
><br>
> On Fri, Mar 7, 2014 at 9:15 AM, Daniel Baker <<a href="mailto:info@collisiondetection.biz">info@collisiondetection.biz</a>>wrote:<br>
><br>
>><br>
>> Hi,<br>
>><br>
>> I have followed your tutorial to set up glusterfs 3.4.2 in vmware.<br>
>><br>
>> <a href="http://www.gluster.org/community/documentation/index.php/Getting_started_configure" target="_blank">http://www.gluster.org/community/documentation/index.php/Getting_started_configure</a><br>
>><br>
>> My gluster volume info is the same as this:<br>
>><br>
>><br>
>> Volume Name: gv0<br>
>> Type: Replicate<br>
>> Volume ID: 8bc3e96b-a1b6-457d-8f7a-a91d1d4dc019<br>
>> Status: Created<br>
>> Number of Bricks: 1 x 2 = 2<br>
>> Transport-type: tcp<br>
>> Bricks:<br>
>> Brick1: node01.yourdomain.net:/export/sdb1/brick<br>
>> Brick2: node02.yourdomain.net:/export/sdb1/brick<br>
>><br>
>> In order to test replication I have installed the glusterfs-client on my<br>
>> ubuntu 12.04 laptop.<br>
>><br>
>> I issue this command:<br>
>><br>
>> sudo mount.glusterfs 192.168.100.170:gv0 /mnt/export<br>
>><br>
>> but I receive this error :<br>
>><br>
>> Usage: mount.glusterfs <volumeserver>:<volumeid/volumeport> -o<br>
>> <options> <mountpoint><br>
>> Options:<br>
>> man 8 mount.glusterfs<br>
>><br>
>> To display the version number of the mount helper:<br>
>> mount.glusterfs --version<br>
>><br>
>><br>
>><br>
>> I have also tried this variant :<br>
>><br>
>> # mount -t glusterfs HOSTNAME-OR-IPADDRESS:/VOLNAME MOUNTDIR<br>
>><br>
>><br>
>><br>
>> So how do I mount the volumes and test the replication. Your getting<br>
>> started tutorial doesn't detail that ?<br>
>><br>
>> Thanks for your help<br>
>><br>
>> Dan<br>
>><br>
>> _______________________________________________<br>
>> Gluster-users mailing list<br>
>> <a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
>> <a href="http://supercolony.gluster.org/mailman/listinfo/gluster-users" target="_blank">http://supercolony.gluster.org/mailman/listinfo/gluster-users</a><br>
>><br>
> -------------- next part --------------<br>
> An HTML attachment was scrubbed...<br>
> URL: <<a href="http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140307/1143f397/attachment-0001.html" target="_blank">http://supercolony.gluster.org/pipermail/gluster-users/attachments/20140307/1143f397/attachment-0001.html</a>><br>
><br>
> ------------------------------<br>
><br>
> Message: 5<br>
</div></div>> Date: Fri, 7 Mar 2014 19:05:24 +0000<br>
> From: Justin Clift <<a href="mailto:justin@gluster.org">justin@gluster.org</a>><br>
> To: <a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>, <<a href="mailto:gluster-devel@nongnu.org">gluster-devel@nongnu.org</a>><br>
> Subject: Re: [Gluster-users] [Gluster-devel] Is there demand for<br>
> geo-replication on RHEL/CentOS/SL 5.x?<br>
> Message-ID: <<a href="mailto:9D72E0A0-589F-48A4-B978-8B8508B56372@gluster.org">9D72E0A0-589F-48A4-B978-8B8508B56372@gluster.org</a>><br>
> Content-Type: text/plain; charset=us-ascii<br>
><br>
> On 04/03/2014, at 1:35 PM, Justin Clift wrote:<br>
>> Hi all,<br>
>><br>
>> Is anyone interested in having geo-replication work on RHEL/CentOS/SL 5.x?<br>
><br>
><br>
> Seems pretty clear there's no demand for geo-replication on EL5,<br>
> so we'll disable the rpm building of it.<br>
><br>
> Patch to do the disabling is up for review:<br>
><br>
> <a href="http://review.gluster.org/#/c/7210/" target="_blank">http://review.gluster.org/#/c/7210/</a><br>
><br>
> If anyone's got the time to do code review of it, please do (it's<br>
> a simple one). :)<br>
><br>
> Regards and best wishes,<br>
><br>
> Justin Clift<br>
><br>
> --<br>
> Open Source and Standards @ Red Hat<br>
><br>
> <a href="http://twitter.com/realjustinclift" target="_blank">twitter.com/realjustinclift</a><br>
><br>
><br>
><br>
> ------------------------------<br>
><br>
> Message: 6<br>
> Date: Fri, 7 Mar 2014 11:47:06 -0800<br>
> From: Justin Dossey <<a href="mailto:jbd@podomatic.com">jbd@podomatic.com</a>><br>
> To: gluster-users <<a href="mailto:gluster-users@gluster.org">gluster-users@gluster.org</a>><br>
> Subject: [Gluster-users] DNS resolution of gluster servers from<br>
> client?<br>
> Message-ID:<br>
> <<a href="mailto:CAPMPShziV96SvSb-tpAoExFR67qANvqDU4D1uavs9t33EYrULg@mail.gmail.com">CAPMPShziV96SvSb-tpAoExFR67qANvqDU4D1uavs9t33EYrULg@mail.gmail.com</a>><br>
> Content-Type: text/plain; charset="iso-8859-1"<br>
><br>
> While testing rolling upgrades from 3.3 to 3.4, I ran into the "Transport<br>
> Endpoint is not connected" issue on my test client (running 3.3) after<br>
> rebooting two of my four test GlusterFS 3.4 servers<br>
> (distributed-replicated-2).<br>
><br>
> Unmounting and remounting the volume was the only way I could get the error<br>
> to go away<br>
><br>
> As the nodes in question were actually up at the time I got the error, and<br>
> waiting did not help, I checked the client logs and found this:<br>
><br>
> [2014-03-04 23:19:26.124162] E [dht-common.c:1374:dht_lookup] 0-TEST1-dht:<br>
> Failed to get hashed subvol for /<br>
> [2014-03-04 23:19:26.124434] E [dht-common.c:1374:dht_lookup] 0-TEST1-dht:<br>
> Failed to get hashed subvol for /<br>
> [2014-03-04 23:19:27.626845] I [afr-common.c:3843:afr_local_init]<br>
> 0-TEST1-replicate-0: no subvolumes up<br>
> [2014-03-04 23:19:27.626928] W [fuse-bridge.c:2525:fuse_statfs_cbk]<br>
> 0-glusterfs-fuse: 77: ERR => -1 (Transport endpoint is not connected)<br>
> [2014-03-04 23:19:27.857455] E [common-utils.c:125:gf_resolve_ip6]<br>
> 0-resolver: getaddrinfo failed (No address associated with hostname)<br>
> [2014-03-04 23:19:27.857507] E<br>
> [name.c:243:af_inet_client_get_remote_sockaddr] 0-TEST1-client-0: DNS<br>
> resolution failed on host glustertest1<br>
> [2014-03-04 23:19:28.047913] E [common-utils.c:125:gf_resolve_ip6]<br>
> 0-resolver: getaddrinfo failed (No address associated with hostname)<br>
> [2014-03-04 23:19:28.047963] E<br>
> [name.c:243:af_inet_client_get_remote_sockaddr] 0-TEST1-client-1: DNS<br>
> resolution failed on host glustertest2<br>
><br>
> These log messages are interesting because although the servers in question<br>
> (glustertest{1,2,3,4} are not in DNS, they *are* in the /etc/hosts files on<br>
> all of the hosts in question.<br>
><br>
> Is it a bug that the client requires that all the GlusterFS servers be in<br>
> DNS?<br>
><br>
><br>
</blockquote></div><br></div>