On 23-1-2017 22:01, Ming Lin wrote: > On Mon, Jan 23, 2017 at 12:38 PM, Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote: >> On 23-1-2017 20:08, Ming Lin wrote: >>> On Mon, Jan 23, 2017 at 6:28 AM, Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote: >>> >>>> >>>> Other nice tools to help you here to see where the socket has gone: >>>> sockstat >>>> lsof >>>> >>>> They can tell you if the socket is somewhere else opened. >>>> And what the state is. >>>> >>>> Or they can tell you what other port(s) the monitor has opened. >>> >>> # netstat -putnl |grep 7000 >>> <no output> >> >>> # netstat -putna |grep 7000 >>> tcp 0 0 192.168.0.1:7000 192.168.122.131:53240 >>> ESTABLISHED 21980/ceph-mon >> >> Is process 21980 listening on any other ports? the normal range would be >> 6800-7300 (as defined in config_opts.h) > > No, that's the only one with ESTABLISHED state. > > # netstat -putna |grep 21980 > tcp 0 0 192.168.0.1:7000 192.168.122.131:53240 > ESTABLISHED 21980/ceph-mon > >> And it would start on 6789, so quite a few rebinds have occurred. >> unless have configured it differently. > > I configured with 7000 for test purpose. > > [mon] > mon initial members = a > > [mon.a] > mon addr = 192.168.0.1:7000 > Then the process is really broken somewhere, and you will have to refer to either logfiles and or gdb-debugging. --WjW -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
