<div dir="ltr"><div class=""><img class="" id=":359" src="https://mail.google.com/mail/u/0/images/cleardot.gif" alt=""></div><div>Kaushal,<br><div class=""><div id=":357" class="" tabindex="0"><img class="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"></div>
</div><br>On Mon, Jul 29, 2013 at 11:59 PM, Kaushal M <<a href="mailto:kshlmster@gmail.com">kshlmster@gmail.com</a>> wrote:<br>> Some other process is listening on 49157 on ir2, but netstat and lsof<br>> don't provide any answers to what process it is.<br>
<br></div><div>I'm not confident that that is really happening. I tried hand executing the glusterfsd command with several other free ports and got exactly the same error messages. Is there another code path that causes it to fail to make the connection?<br>
</div><div><br>> Googling for more information I came across a possible answer to such<br>> processes. Apparently services which register with portmap usually are<br>> of this type.<br>> Can you do a 'rpcinfo -p' on ir2 and see if port 49157 is listed?<br>
<br></div><div>[root@ir2 bricks]# rpcinfo -p<br> program vers proto port service<br> 100000 4 tcp 111 portmapper<br> 100000 3 tcp 111 portmapper<br>
100000 2 tcp 111 portmapper<br> 100000 4 udp 111 portmapper<br> 100000 3 udp 111 portmapper<br> 100000 2 udp 111 portmapper<br> 100227 3 tcp 2049 nfs_acl<br> 100005 3 tcp 38465 mountd<br>
100005 1 tcp 38466 mountd<br> 100003 3 tcp 2049 nfs<br> 100021 4 tcp 38468 nlockmgr<br> 100021 1 udp 996 nlockmgr<br> 100021 1 tcp 999 nlockmgr<br> 100024 1 udp 37124 status<br>
100024 1 tcp 60047 status<br><br></div><div>I don't know if it is relevant but there is a defunct glusterfsd:<br>root 23744 208 0.0 0 0 ? Zsl Jul23 20015:32 [glusterfsd] <defunct><br>
<br></div>but lsof -p 23744 reports nothing at all.<div class=""><div id=":357" class="" tabindex="0"><img class="" src="https://mail.google.com/mail/u/0/images/cleardot.gif"><br></div><div id=":357" class="" tabindex="0">
Thanks,<br><br>Joel<br></div></div><div class="gmail_extra"><br><br></div></div>