This happens every time that portmap is stopped while something has a connection open to it. The problem can be reliably reproduced like this:
# nc localhost sunrpc & [1] 14894 # stop portmap [1] + done nc localhost sunrpc portmap stop/waiting # start portmap start: Job failed to start You can see from netstat that the server-side socket is sitting in TIME_WAIT, blocking portmap from starting: # netstat -a | grep sunrpc tcp 0 0 localhost:60269 localhost:sunrpc TIME_WAIT tcp 0 0 localhost:sunrpc localhost:33281 TIME_WAIT I would expect portmap to use SO_REUSEADDR to deal with this case, but apparently it only does this if the weird LOOPBACK_SETUNSET #define is enabled. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688550 Title: portmap/statd can not be restarted To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/portmap/+bug/688550/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs