On 11/02/2014, at 8:41 PM, John G. Heim wrote: > On 02/11/14 13:31, Justin Clift wrote: >> On 10/02/2014, at 4:18 PM, John G. Heim wrote: >>> On 02/10/14 07:23, Justin Clift wrote: >>>> On Thu, 06 Feb 2014 14:52:44 -0600 >>>> "John G. Heim" <jheim@xxxxxxxxxxxxx> wrote: >>>>> Maybe this is a dumb question but do I have to set up an nfs server on >>>>> one of the server peers in my gluster volume in order to connect to the >>>>> volume with nfs? >>>> >>>> In theory, NFS is supposed to be enabled/running by default. >>> >>> On all the servers? I have 51 servers in my cluster. I just ran a port scan and none of them have port 2049 open. >>> >>>> If you run "gluster volume status", what does it show? >>> >>> Do you mean 'gluster volume info'? That command says "nfs.disable: off" I'm running 3.2.7, the version in debian stable (wheezy). >> >> Heh, nah I'm definitely meaning "status" not info. He's the output from > > That gives me an error message "Unrecognized word". > > Difference between 3.2 and 3.5? Looks like it was introduced in 3.3. Sorry about that, that was unhelpful of me. :/ As a thought, does the version of netstat on Debian Wheezy support "-nltp" as an option when run as root? If so, that will show all listening ports and their process pid/name. From a Gluster 6.4 (now) vm just created: $ sudo gluster volume status Status of volume: playground Gluster process Port Online Pid ------------------------------------------------------------------------------ Brick centos65:/export/brick/brick1 49152 Y 6630 NFS Server on localhost 2049 Y 6641 There are no active volume tasks $ sudo netstat -nltp | grep gluster tcp 0 0 0.0.0.0:49152 0.0.0.0:* LISTEN 6630/glusterfsd tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN 6641/glusterfs tcp 0 0 0.0.0.0:38465 0.0.0.0:* LISTEN 6641/glusterfs tcp 0 0 0.0.0.0:38466 0.0.0.0:* LISTEN 6641/glusterfs tcp 0 0 0.0.0.0:38469 0.0.0.0:* LISTEN 6641/glusterfs tcp 0 0 0.0.0.0:24007 0.0.0.0:* LISTEN 6551/glusterd (lsof can show this info too, I'm just not as familiar with it) On the second line of netstat results, we can see glusterfs is binding to port 2049 on this server. Try it on one of your boxes. It will help figure out if something is actually listening on the NFS port, but not showing up in a port scan for some reason (iptables, etc). If glusterfs is NOT binding to port 2049, it might be crashing on startup too. For me with Gluster 3.5 dev, the crashing NFS server is leaving a bunch of core.xxxx files around (one per crash). eg: /core.1323 /core.1523 /core.1952 Running "file" on any of them shows its a core file from glusterfs trying to start (and failing). If you have that happening too, this helps narrow things down. ;) Let us know how it goes? + Justin -- Open Source and Standards @ Red Hat twitter.com/realjustinclift _______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
