On Tue, Sep 13, 2016 at 1:29 PM, Willem Jan Withagen <wjw@xxxxxxxxxxx> wrote: > On 13-9-2016 21:52, Gregory Farnum wrote: >> Is osd.0 actually running? If so it *should* have a socket, unless >> you've disabled them somehow. Check the logs and see if there are >> failures when it gets set up, I guess? >> >> Anyway, something has indeed gone terribly wrong here. I know at one >> point you had some messenger patches you were using to try and get >> stuff going on BSD; if you still have some there I think you need to >> consider them suspect. Otherwise, uh...the network stack is behaving >> very differently than Linux's? > > So what is the expected result of an osd down/up? > > Before it is connected to ports like: > 127.0.0.1:{6800,,6801,6802}/{nonce=pid-like} > after the osd has gone down/up the sockets work be: > 127.0.0.1:{6800,,6801,6802}/{(nonce=pid-like)+1000000} > > or are the ports also incremented? IIRC, it should usually be the same ports and different nonce. But the port is *allowed* to change; that happens sometimes if there was an unclean shutdown and the port is still considered in-use by the OS for instance. -- 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