|
"netstat -tlnp" is a useful command to know. That shows what tcp
ports are listening and the pids and command names of those
processes. More specifically to gluster, "gluster volume status" will show what ports each brick is listening on. "@ports" from the IRC channel will trigger a factoid that says: glusterd's management port is 24007/tcp and 24008/tcp if you use rdma. Bricks (glusterfsd) use 24009 & up for <3.4 and 49152 & up for 3.4. (Deleted volumes do not reset this counter.) Additionally it will listen on 38465-38467/tcp for nfs, also 38468 for NLM since 3.3.0. NFS also depends on rpcbind/portmap on port 111 and 2049 since 3.4. The documentation states that: Brick ports will now listen from 49152 onwards (instead of 24009 onwards as with previous releases). The brick port assignment scheme is now compliant with IANA guidelines.https://forge.gluster.org/gluster-docs-project/pages/GlusterFS_34_Release_Notes#Brick+port+changes That is, however, the only place that it's correct. There does need to be a patch to the documentation . It still refers to port 24009. Whatever documentation you were looking at which mentioned 34865 would have been talking about nfs. On 5/5/2014 7:47 PM, Thing wrote:
|
_______________________________________________ Gluster-users mailing list Gluster-users@xxxxxxxxxxx http://supercolony.gluster.org/mailman/listinfo/gluster-users
