Univention Bugzilla – Bug 55008
NFS does not start when directory is missing
Last modified: 2022-07-19 13:34:44 CEST
A (school) customer tested the upgrade from UCS 4 to UCS 5 and found that NFS was not willing to start: Jul 14 10:44:35 testVM systemd[1]: Starting NFS server and services... Jul 14 10:44:35 testVM exportfs[7422]: exportfs: Failed to stat /home/testVM/mitarbeiter/<username>: No such file or directory Jul 14 10:44:35 testVM systemd[1]: nfs-server.service: Control process exited, code=exited status=1 Jul 14 10:44:35 testVM systemd[1]: Failed to start NFS server and services. Jul 14 10:44:35 testVM systemd[1]: nfs-server.service: Unit entered failed state. Jul 14 10:44:35 testVM systemd[1]: nfs-server.service: Failed with result 'exit-code'. Warning: nfs-server.service changed on disk. Run 'systemctl daemon-reload' to reload units. The creation of the missing folder /home/testVM/mitarbeiter/<username> resolve the problem, but it looks like the code is not evaluating the var username. The customer mentioned that the problem seems to be there already in UCS 4 so I opened the bug against UCS4 but in UCS 5 it seems to be present also.
What kind of nfs export is defined on the system? To me it looks like an expected behavior that the service does not start (i.e. fails early), if a directory should be exported, but it does not exist.
(In reply to Dirk Schnick from comment #0) > The customer mentioned that the problem seems to be there already in UCS 4 > so I opened the bug against UCS4 but in UCS 5 it seems to be present also. So what does it have to do with the upgrade to UCS 5? I change the bug title from "NFS does not start after update from UCS4 to UCS5".