On 01/05/14 07:45, Colin King wrote: > I'm seeing this too, strace show it spinning on: > > select(8, [0 3 6 7], [], [6], NULL) = 1 (in [0]) > recvmsg(0, 0x7fffdb2aa6d0, 0) = -1 ENOTSOCK (Socket operation on non-socket) > accept(0, 0, NULL) = -1 ENOTSOCK (Socket operation on non-socket) > select(8, [0 3 6 7], [], [6], NULL) = 1 (in [0]) > recvmsg(0, 0x7fffdb2aa6d0, 0) = -1 ENOTSOCK (Socket operation on non-socket) > accept(0, 0, NULL) = -1 ENOTSOCK (Socket operation on non-socket) > > So we're getting ENOTSOCK on fd 0, which is /dev/null : >
It would be really useful to get an strace of dnsmasq from startup to when it's in this state, since I've no yet been able to reproduce this. Also the output of lsof | grep dnsmasq The bug looks superficially like an earlier one which was triggered by starting dnsmasq without stdout/stdin/stderr (ie fd 0,1,2). Sockets would be opened which used these fds, and subsequently the "connect std* to /dev/null" code would trash them. However that doesn't explain why both the UDP and TCP listening sockets seem to be zero here. Cheers, Simon. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1314697 Title: Upon upgrade, DNS resolution no longer works To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1314697/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
