Krishnan, On Mon, Jul 29, 2013 at 8:24 PM, Krishnan Parthasarathi <kparthas at redhat.com > wrote: > Could you check using netstat, what other process is listening on > the port, around the time of failure? [root at ir2 ~]# netstat -ntlp | grep 49157 tcp 0 0 0.0.0.0:49157 0.0.0.0:* LISTEN - Don't know how helpful that is. Here is the output of lsof -i: [root at ir2 ~]# lsof -i :49157 COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME glusterfs 7798 root 7u IPv4 4874907 0t0 TCP ir2.ncr.nps.edu: ftps-data->ir0.XX.edu:49157 (ESTABLISHED) glusterfs 7798 root 10u IPv4 4874910 0t0 TCP ir2.ncr.nps.edu:973-> ir1.XX.edu:49157 (ESTABLISHED) glusterfs 7804 root 7u IPv4 4874872 0t0 TCP ir2.ncr.nps.edu:1008 ->ir0.XX.edu:49157 (ESTABLISHED) glusterfs 7804 root 10u IPv4 4874875 0t0 TCP ir2.ncr.nps.edu:1007 ->ir1.XX.edu:49157 (ESTABLISHED) glusterfs 18954 root 10u IPv4 4948346 0t0 TCP ir2.ncr.nps.edu:959-> ir1.XX.edu:49157 (ESTABLISHED) glusterfs 18954 root 12u IPv4 4948343 0t0 TCP ir2.ncr.nps.edu:962-> ir0.XX.edu:49157 (ESTABLISHED) Thanks for your help! Joel -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130729/4eebf235/attachment.html>
