Using dhcp-4.3.1/2 together with bind-9.10.1/2 Run 'dhclient em1', dhclient obtains an address, then goes to running in background and stops reacting. Once the address lifetime decreases to 0, it's removed from interface and machine is left without address. When I prevent it from daemonizing by using -d, i.e. 'dhclient -d em1', it works, but it's impossible to stop it (Ctrl+C) and I have to 'kill -9' it. Dhcpd seems to have the same problem. strace shows a lot of futex() calls, but I don't know if that's related.
http://fedoraproject.org/wiki/Changes/BIND_9.10 says that: Adaptive mutex locks are now used on systems which support them. If that's related, maybe we can try to disable them somehow.
The only work-around until we have a fix is to downgrade back to bind-9.9 https://koji.fedoraproject.org/koji/buildinfo?buildID=598877 https://koji.fedoraproject.org/koji/buildinfo?buildID=599854 I put the x86_64 rpms also to https://jpopelka.fedorapeople.org/dhcp/bz1193944/ in case the koji builds are deleted any time soon.
(In reply to Jiri Popelka from comment #1) > http://fedoraproject.org/wiki/Changes/BIND_9.10 > says that: > Adaptive mutex locks are now used on systems which support them. > > If that's related, maybe we can try to disable them somehow. Building bind neither with --with-locktype=standard nor --with-locktype=adaptive makes any change.
(In reply to Jiri Popelka from comment #2) > The only work-around until we have a fix is to downgrade back to bind-9.9 Or to start playing with internal dhcp client in NetworkManager: # echo "dhcp=internal" >> /etc/NetworkManager/NetworkManager.conf
*** This bug has been marked as a duplicate of bug 1184173 ***