Description of problem: The locking directory and warm start directory for rpcbind has moved to /run/rpcbind. That directory is usually created by systemd-tmpfiles-setup but that does not seem to happen with dracut-pre-udev: From https://bugzilla.redhat.com/show_bug.cgi?id=1401561#c66 Mar 7 09:41:25 localhost audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=kernel msg='unit=iscsid comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Mar 7 09:41:25 localhost kernel: RPC: Registered named UNIX socket transport module. Mar 7 09:41:25 localhost kernel: RPC: Registered udp transport module. Mar 7 09:41:25 localhost kernel: RPC: Registered tcp transport module. Mar 7 09:41:25 localhost kernel: RPC: Registered tcp NFSv4.1 backchannel transport module. Mar 7 09:41:25 localhost dracut-pre-udev: rpcbind: /run/rpcbind/rpcbind.lock: No such file or directory Version-Release number of selected component (if applicable): How reproducible: IDK... but looking at modules.d/95nfs/module-setup.sh it is definitly not doing the right thing, anymore.
It is expected that rpcbind will be started up via systemd do the dependency on systemd-tmpfiles-setup service
Please add "systemd-tmpfiles --creat /run/rpcbind" to the modules.d/95nfs/module-setup.sh before rpcbind is started.
Wouldn't it be possible to solve the problem without intervention by dracut-maint-list (since it seems that no one is listening there...)?
(In reply to Maurizio Paolini from comment #3) > Wouldn't it be possible to solve the problem without intervention by > dracut-maint-list (since it seems that no one is listening > there...)? They seem to be fairly dormant which is unfortunate
maybe a workaround: for a homebrewed kernel I set CONFIG_AF_RXRPC=y CONFIG_AF_RXRPC_IPV6=y CONFIG_AF_RXRPC_INJECT_LOSS=y CONFIG_AF_RXRPC_DEBUG=y
(In reply to Maurizio Paolini from comment #3) > Wouldn't it be possible to solve the problem without intervention by > dracut-maint-list (since it seems that no one is listening > there...)? I did add the following code to create create the direcory at the beginning of rpcbind... char *systemdtmp = "/usr/bin/systemd-tmpfiles --create rpcbind.conf" tryagain: /* Check that another rpcbind isn't already running. */ if ((rpcbindlockfd = (open(RPCBINDDLOCK, O_RDONLY|O_CREAT, 0444))) == -1) { if (once) { once = system(systemdtmp); /* set once to avoid a warning */ once = 0; goto tryagain; } err(1, "%s", RPCBINDDLOCK); } which should take of this problem... I'm not sure why its not working??
https://github.com/dracutdevs/dracut/commit/1856ae95c873a6fe855b3dccd0144f1a96b9e71c
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '25'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 25 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days