You are not logged in.
after a few hours of troubleshooting i finally found this thread: https://bbs.archlinux.org/viewtopic.php?id=152071
after you install the NFS Server you NEED to reboot. The server will refuse to work until you do.
i hope someone puts this message in the nfs-util package to save some headaches.
so, whenever systemd fails to start the nfs server and gives you some dependency errors, you probably forgot to restart.
Aug 13 21:10:23 systemd[1]: Dependency failed for NFSv4 ID-name mapping service.
Aug 13 21:10:23 systemd[1]: nfs-idmapd.service: Job nfs-idmapd.service/start failed with result 'dependency'.
Aug 13 21:10:23 systemd[1]: Dependency failed for NFSv4 Client Tracking Daemon.
Aug 13 21:10:23 systemd[1]: nfsdcld.service: Job nfsdcld.service/start failed with result 'dependency'.
Aug 13 21:10:23 systemd[1]: Dependency failed for NFSv4 Mount Daemon.
Aug 13 21:10:23 systemd[1]: Dependency failed for NFSv4 server and services.
Aug 13 21:10:23 systemd[1]: nfsv4-server.service: Job nfsv4-server.service/start failed with result 'dependency'.
Aug 13 21:10:23 systemd[1]: nfsv4-exportd.service: Job nfsv4-exportd.service/start failed with result 'dependency'.
Aug 13 21:10:23 systemd[1]: Dependency failed for NFS server and services.
Aug 13 21:10:23 systemd[1]: Dependency failed for NFS Mount Daemon.
Aug 13 21:10:23 systemd[1]: nfs-mountd.service: Job nfs-mountd.service/start failed with result 'dependency'.
Aug 13 21:10:23 systemd[1]: nfs-server.service: Job nfs-server.service/start failed with result 'dependency'.
Last edited by SunBlade (2024-08-13 20:11:33)
Live your life, you got only one.
Offline
Unlikely, more likely that your install actually coincided with a kernel update on that same boot, leading to the kernel being unable to load modules for the nfs driver.
This is a common occurence, which can be mitigated with https://archlinux.org/packages/?q=kernel-modules-hook in oder to keep old modules around when a newer kernel gets installed.
Last edited by V1del (2024-08-13 20:16:32)
Offline
although i am very diligent in rebooting after kernel updates, i can not promise i missed a kernel update while installing all those packages over the past few days.
but i vaguely remember the last time i installed an ubuntu server i had the same problem.
i am no expert on this, i can only guess:
i suspect, since nfs has been integrated into the kernel, there is some flag, driver or whatnot that enables/disables nfs capabilities of the kernel at boot time.
hmmm... maybe i should treat nfs like a kernel driver in the future.
Live your life, you got only one.
Offline
nfs has been part of the kernel since 1993 and nothing "enables/disables nfs capabilities of the kernel at boot time" that would go away w/ a simple reboot.
V1del's suggestion is the by far most likely cause, if in the future you want to know for sure what's breaking some service,
systemctl status nfs-idmapd.service
and similar
Offline