Job For Nfs Server.service Canceled.

I have set up NFS accordingly to the Wiki until the point we start the server. When I type # sytemctl start nfs-server I get. A dependency job for nfs-server.service failed. See 'journalctl -xe' for details. And journalctl says. Mar 29 21:05:54 downbox systemd1: Mounting. Where I'm hanging up now is after 'sudo systemctl enable -now nfs-server rpcbind', I'm getting a 'Job for nfs-server.service canceled' error, instead of seeing it run. I've set up my IP address to be static, with a lease entered into my router, and changed my hostname to be 'something.local', replacing all previous hostnames in the correct file.

How To Set Up an NFS Mount on Ubuntu 16.04 Posted Aug 4, 2016 9.7k views Networking Ubuntu Ubuntu 16.04Question for:What does nfs-server.service code=exited status=22 mean? Anderson’s tutorial Log: SetUp NFS Mount Ubuntu 16.04This tutorial has gotten me further in getting one Ubuntu 16.04 to file share than the other 5 or so, good writing!Have searched and found no mention of status=22 here or at Ask.Ubuntu. file folders /status/22/ for another program. other nfs-server.service questions do not seem to apply to this situation. This is a home office LAN with 1 Ubuntu HP 220-110z tower and 1 Ubuntu HP Laptop and one Win 10 Laptop.

connecting with Win 10 is another matter. Remote superuser not wanted.I have been following M.

After the last updates the nfs-server stopped working:A dependency job for nfs-server.service failed. Maybe I should add below as possible reason:● systemd-boot-system-token.service - Store a System Token in an EFI VariableLoaded: loaded (/usr/lib/systemd/system/systemd-boot-system-token.service; static; vendor preset: disabled)Active: failed (Result: exit-code) since Mon 2019-12-02 13:55:21 WITA; 50min agoDocs: man:systemd-boot-system-token.service(8)Main PID: 455 (code=exited, status=1/FAILURE)Dec 02 13:55:21 b1 systemd1: Starting Store a System Token in an EFI Variable.Dec 02 13:55:21 b1 bootctl455: Couldn't find EFI system partition. It is recommended to mount it to /boot or /efi.Dec 02 13:55:21 b1 bootctl455: Alternatively, use -esp-path= to specify path to mount point.Dec 02 13:55:21 b1 systemd1: systemd-boot-system-token.service: Main process exited, code=exited, status=1/FAILUREDec 02 13:55:21 b1 systemd1: systemd-boot-system-token.service: Failed with result 'exit-code'.Dec 02 13:55:21 b1 systemd1: Failed to start Store a System Token in an EFI Variable. It seems the sc2 editor is currently broken for mac. The work-around isn't quite making sense to me as the rpcbind daemon you launched outside of systemd seems like it would prevent the rpcbind.socket from being created (this is what happens when I try and do this myself though I had rpcbind running in the foreground). The errors in your log that pop out to me are:Dec 01 21:22:03 b1 rpc.mountd2363: Cannot register service: RPC: Authentication error; why = Client credential too weakDec 01 21:22:03 b1 rpc.statd2354: unable to register (statd, 1, udp).Which make me wonder what the status of the rpcbind.service is before and after you try and start the nfs-server.service.