This was determined to be caused by a new kernel setting (at the time). If net.core.xfrm_larval_drop is not set to 1, bind does not get the blocking behavior it expects on the socket and causes this situation. Setting net.core.xfrm_larval_drop=1 works around it.
** Changed in: bind (Ubuntu) Status: Incomplete => Invalid -- loss of masters causing bind to become unresponsive https://bugs.launchpad.net/bugs/177489 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs