Just one thing that I'm trying to figure out: nfs-mountd.service already has:
[Unit] ... BindsTo=nfs-server.service Which means, it "requires" nfs-server.service AND it is stopped as soon nfs-server.service is stopped. Judging by this upstream commit: http://paste.ubuntu.com/23940610/ """ So while I think it is valid to use rpcbind.target for ordering (before/after) it shouldn't be used for dependencies (Wants/Requires). The rpcbind.target file included in systemd does not "Require" the actual service, so requiring rpcbind.target itself is pointless. """ This race condition might be happening because of the ".target" choice for rpcbind dependency - on nfs-server - instead of the "lack" of dependency in nfs-mountd. My only doubt is that developer preferred to depend on "rpcbind.socket" instead of "rpcbind.service". I'll go ahead and give it a try by testing ".socket", based on upstream commits, and ask for you to test it. Thank you Rafael -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1590799 Title: nfs-kernel-server does not start because of dependency failure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nfs-utils/+bug/1590799/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
