On 02/11/14 06:20, Robert P. J. Day wrote: > On Tue, 11 Feb 2014, Ed Greshko wrote: > >> On 02/11/14 05:54, Jonathan Ryshpan wrote: >>> On Sun, 2014-02-09 at 17:55 -0800, Jonathan Ryshpan wrote: >>>> Setting up an nfs server on a laptop running Fedora-20, I get the >>>> following perplexing results: >>>> >>>> # systemctl start nfs.service >>>> # systemctl enable nfs.service >>>> Failed to issue method call: No such file or directory >>>> >>>> Sure enough, as promised, nfs works up to the next reboot, then it stops >>>> working. Is the system missing a module? Or what? >>> I had thought that enabling nfs-server.service to which nfs.server is >>> linked would enable nfs.server; but it doesn't seem to. Here's the >>> latest: >>> # ll /usr/lib/systemd/system/nfs.service >>> lrwxrwxrwx. 1 root root 18 Feb 1 >>> 18:54 /usr/lib/systemd/system/nfs.service -> nfs-server.service >>> # systemctl list-unit-files | grep nfs >>> proc-fs-nfsd.mount static >>> var-lib-nfs-rpc_pipefs.mount static >>> nfs-blkmap.service disabled >>> nfs-idmap.service disabled >>> nfs-lock.service enabled >>> nfs-mountd.service enabled >>> nfs-rquotad.service disabled >>> nfs-secure-server.service disabled >>> nfs-secure.service disabled >>> nfs-server.service enabled <==== >>> nfs.service disabled <==== >>> nfslock.service disabled >>> nfs.target enabled >>> And in fact nfs networking doesn't work till I invoke: >>> # systemctl start nfs.service >>> (Note that nfs.target is enabled.) >>> >>> What's going on? How can I fix it >>> >> In answer to "What is going on".... Yesterday I asked if you have the output of >> >> systemctl status nfs-server.service >> >> *before* you started it manually. > hmmmmm ... i can vouch that i'm getting the same thing on my f20 > system. manually starting and stopping seems to work fine, but the > "enable" operation generates what the OP reported. odd ... > > [root@localhost rpjday]# systemctl disable nfs > [root@localhost rpjday]# systemctl enable nfs > Failed to issue method call: No such file or directory > [root@localhost rpjday]# systemctl start nfs > [root@localhost rpjday]# showmount -e > Export list for localhost.localdomain: > ... snip correct output here ... > # > > so, yes, start and stop seem fine, but enable isn't working well. > All well and good..... And yes, the same is true here.... BUT, I need not manually start the NFS server after a reboot. I comes up just fine and a remote system can mount the exported file systems. Unlike what the OP and you seem to have in common. Sooooo...... What is the output of "systemctl status nfs-server.service" *after* a reboot and before you manually start it.... And second..... Do you have "NetworkManager-wait-online.service" enabled. If not, does enabling it make a difference? -- Getting tired of non-Fedora discussions and self-serving posts -- users mailing list users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
