On 07/30/2013 10:08 AM, Joel Young wrote: > On Mon, Jul 29, 2013 at 9:30 PM, Krishnan Parthasarathi > <kparthas at redhat.com <mailto:kparthas at redhat.com>> wrote: > > We need to find out what is the glusterfs process with pid 7798 and > understand > > what is causing glusterd, which is also a portmapping service for > bricks/clients, > > assign a port that is already bound. > > ps -ef | grep 7798 > root 7798 1 0 Jul29 ? 00:00:30 /usr/sbin/glusterfs -s > localhost --volfile-id gluster/nfs -p /var/lib/glusterd/nfs/run/nfs.pid > -l /var/log/glusterfs/nfs.log -S > /var/run/c363357361020603c58966244aa8b101.socket > Gluster NFS process should listen by default on 2049 with 3.4. Can you please check if port 2049 is in use? netstat -ntlp | grep 2049 can help. Thanks, Vijay
