Created attachment 1196971 [details] strace of "rpc-idmapd -f -vvv" showing libresolv isn't accesssed Description of problem: On a fresh Fedora 24 install, rpc.idmapd fails to start due to a symbol lookup error, whether started as nfs-idmapd.service or manually as "rpc.idmapd -f -vvv". Version-Release number of selected component (if applicable): Fresh Fedora 24 install, kernel 4.6.7 (-300.fc24.x86_64), nfs-utils 1.3.4 (-1.rc2.fc24), rpcbind 0.2.3 (-11.rc1.fc24), and glibc-2.23.1 (-10.fc24.x86_64). How reproducible: 100% reproducible Steps to Reproduce: 1. Fresh install using Fedora 24 net installer, selecting minimal install 2. # yum install nfs-utils 3. # systemctl enable nfs-server 4. # systemctl reboot 5. # systemctl status nfs-idmapd Actual results: Sep 01 19:09:00 fedora rpc.idmapd[682]: /usr/sbin/rpc.idmapd: symbol lookup error: /lib64/libnfsidmap.so.0: undefined symbol: __dn_expand Expected results: For nfs-idmapd.service to start Additional info: Some short searching looks like __dn_expand is part of libresolv. "strace rpc-idmapd -f -vvv" doesn't show "/usr/lib64/libresolv.so.2" is ever accessed, even though it exists. See attached strace.
By the way, on up to date Arch Linux, kernel 4.7.2 (-1 Arch), nfs-utils 1.3.4 (-1 Arch), rpcbind 0.2.3 (-3 Arch), glibc 2.24 (-2 Arch), rpc-idmapd starts just fine. Arch doesn't do anything to fix this bug, follows Fedora's packaging as upstream including nfs-utils_env.sh, nfs.sysconfig, and uses the same unmodified sourceforge source. Arch doesn't apply the 6 patches that Fedora does, so it could be a bug in one of those, like the new rc2 patch. Running dnf --showduplicates list nfs-utils, I see 1:1.3.3-8.rc5.fc24, so I downgraded to that. Problem still occurs.
Duplicate of bug 1372136?
Yes, it's a duplicate. I was looking in nfs-utils for duplicates, and that one is on libnfsidmap. Also, it's fixed. Earlier today: F25 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-285540258b F24 - https://bodhi.fedoraproject.org/updates/FEDORA-2016-625bd99661 *** This bug has been marked as a duplicate of bug 1372136 ***