[Gluster-users] glusterfsd won't restart on one brick

[Joel Young]

Kaushal,

On Mon, Jul 29, 2013 at 11:59 PM, Kaushal M <kshlmster at gmail.com> wrote:
> Some other process is listening on 49157 on ir2, but netstat and lsof
> don't provide any answers to what process it is.

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?

> Googling for more information I came across a possible answer to such
> processes. Apparently services which register with portmap usually are
> of this type.
> Can you do a 'rpcinfo -p' on ir2 and see if port 49157 is listed?

[root at ir2 bricks]# rpcinfo -p
   program vers proto   port  service
    100000    4   tcp    111  portmapper
    100000    3   tcp    111  portmapper
    100000    2   tcp    111  portmapper
    100000    4   udp    111  portmapper
    100000    3   udp    111  portmapper
    100000    2   udp    111  portmapper
    100227    3   tcp   2049  nfs_acl
    100005    3   tcp  38465  mountd
    100005    1   tcp  38466  mountd
    100003    3   tcp   2049  nfs
    100021    4   tcp  38468  nlockmgr
    100021    1   udp    996  nlockmgr
    100021    1   tcp    999  nlockmgr
    100024    1   udp  37124  status
    100024    1   tcp  60047  status

I don't know if it is relevant but there is a defunct glusterfsd:
root     23744  208  0.0      0     0 ?        Zsl  Jul23 20015:32
[glusterfsd] <defunct>

but lsof -p 23744 reports nothing at all.

Thanks,

Joel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://supercolony.gluster.org/pipermail/gluster-users/attachments/20130730/2d683812/attachment.html>