On Mon, 2014-02-10 at 10:28 +0800, Ed Greshko wrote:
> On 02/10/14 09:55, 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?
> >
> 
> nfs service working just fine here on F20.
> 
> After you reboot, what is the output of
> 
> systemctl status nfs.service
> 
> FWIW, there may be a "bug" when using the name nfs.service (which is a 
> symlink) when enabling an enabled service.

A very good question.  I should have followed it earlier.
For more see below.

On Tue, 11 Feb 2014 06:14:05 +0800, Ed Greshko wrote:
> On 02/11/14 05:54, Jonathan Ryshpan wrote:
> > What's going on?  How can I fix it
> 
> One other thing....
> 
> You say you're using a laptop.  Possibly you are also using DHCP to
> get your IP addresses....
> 
> In that case you should also make sure that....
> 
> NetworkManager-wait-online.service is enabled.

As often happens, Ed has got to the root of the problem.  The last line
of the transcript is the important one.:

# systemctl status nfs.service
nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
   Active: failed (Result: exit-code) since Tue 2014-02-11 13:36:33 PST; 1min 
27s ago
  Process: 1316 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=1/FAILURE)
  Process: 1313 
ExecStartPre=/usr/libexec/nfs-utils/scripts/nfs-server.preconfig (code=exited, 
status=0/SUCCESS)

Feb 11 13:36:33 localhost.localdomain exportfs[1316]: exportfs: Failed to 
resolve amito
Feb 11 13:36:33 localhost.localdomain exportfs[1316]: exportfs: Failed to 
resolve amito
Feb 11 13:36:33 localhost.localdomain exportfs[1316]: exportfs: Failed to 
resolve amito
Feb 11 13:36:33 localhost.localdomain exportfs[1316]: exportfs: Failed to 
resolve amito
Feb 11 13:36:33 localhost.localdomain systemd[1]: nfs-server.service: control 
process exited, code=exited status=1
Feb 11 13:36:33 localhost.localdomain systemd[1]: Failed to start NFS Server.
Feb 11 13:36:33 localhost.localdomain systemd[1]: Unit nfs-server.service 
entered failed state.

# systemctl start nfs-server.service

# systemctl status nfs-server.service
nfs-server.service - NFS Server
   Loaded: loaded (/usr/lib/systemd/system/nfs-server.service; enabled)
   Active: active (exited) since Tue 2014-02-11 13:46:00 PST; 17s ago
  Process: 1525 
ExecStartPost=/usr/libexec/nfs-utils/scripts/nfs-server.postconfig 
(code=exited, status=0/SUCCESS)
  Process: 1510 ExecStart=/usr/sbin/rpc.nfsd $RPCNFSDARGS $RPCNFSDCOUNT 
(code=exited, status=0/SUCCESS)
  Process: 1507 ExecStartPre=/usr/sbin/exportfs -r (code=exited, 
status=0/SUCCESS)
  Process: 1504 
ExecStartPre=/usr/libexec/nfs-utils/scripts/nfs-server.preconfig (code=exited, 
status=0/SUCCESS)
 Main PID: 1510 (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/nfs-server.service

Feb 11 13:46:00 localhost.localdomain systemd[1]: Starting NFS Server...
Feb 11 13:46:00 localhost.localdomain systemd[1]: Started NFS Server.

# systemctl enable NetworkManager-wait-online.service   #<Fixes the problem; 
nfs starts at boot time.>


-- 
users mailing list
users@lists.fedoraproject.org
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

Reply via email to