Try creating statdir once when opening lock file fails
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2017-66c84b1ba8
Please login to add feedback.
This update has been submitted for testing by steved.
This update has been pushed to testing.
Works
no regressions noted, I can't vagrant and boot problems
Works fine on x86_64.
This update has been submitted for stable by bodhi.
This update has been pushed to stable.
works as well in vagrant (sorry for the delayed testing ;)
With rpcbind-0.2.4-5.rc1.fc25.x86_64 after reboot ypbind was failing and showing these errors: May 15 10:56:35 ourserver systemd: Starting RPC Bind... May 15 10:56:35 ourserver rpcbind: rpcbind: pmap_prot.c:50: xdr_pmap: Assertion `regs != NULL' failed. May 15 10:56:35 ourserver systemd: Started RPC Bind. May 15 10:56:35 ourserver systemd: rpcbind.service: Main process exited, code=killed, status=6/ABRT May 15 10:56:35 ourserver systemd: rpcbind.service: Unit entered failed state. May 15 10:56:35 ourserver systemd: rpcbind.service: Failed with result 'signal'.
Oddly rpcbind status was showing ok just a failure on ypbind: -- Unit rpcbind.service has finished starting up. -- -- The start-up result is done. May 15 10:58:15 ourserver systemd[1]: rpcbind.service: Main process exited, code=killed, status=6/ABRT May 15 10:58:15 ourserver systemd[1]: rpcbind.service: Unit entered failed state. May 15 10:58:15 ourserver systemd[1]: rpcbind.service: Failed with result 'signal'. May 15 10:58:17 ourserver ypbind[2631]: Binding took 46 seconds May 15 10:58:17 ourserver ypbind[2633]: NIS server for domain divscimath is not responding. May 15 10:58:17 ourserver ypbind[2634]: Killing ypbind with PID 2290. May 15 10:58:17 ourserver ypbind[2290]: 2292: Signal (15) for quitting program arrived. May 15 10:58:17 ourserver systemd[1]: Starting RPC Bind... -- Subject: Unit rpcbind.service has begun start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rpcbind.service has begun starting up. May 15 10:58:17 ourserver ypbind[2635]: Try increase NISTIMEOUT in /etc/sysconfig/ypbind May 15 10:58:17 ourserver systemd[1]: ypbind.service: Control process exited, code=exited status=1 May 15 10:58:17 ourserver systemd[1]: Started RPC Bind. -- Subject: Unit rpcbind.service has finished start-up -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit rpcbind.service has finished starting up. -- -- The start-up result is done. May 15 10:58:18 ourserver systemd[1]: Failed to start NIS/YP (Network Information Service) Clients to NIS Domain Binder. -- Subject: Unit ypbind.service has failed -- Defined-By: systemd -- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel -- -- Unit ypbind.service has failed. -- -- The result is failed. May 15 10:58:18 ourserver systemd[1]: ypbind.service: Unit entered failed state. May 15 10:58:18 ourserver systemd[1]: ypbind.service: Failed with result 'exit-code'.
Downgraded to rpcbind-0.2.3-11.rc1.fc25.x86_64 and both ypbind and rpcbind start fine.