Bug 752747

Summary: NFS service not starting
Product: [Fedora] Fedora Reporter: Erik Terwan <erik.terwan>
Component: nfs-utilsAssignee: Steve Dickson <steved>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: bfields, jlayton, steved
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 07:14:01 EST Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description Erik Terwan 2011-11-10 05:15:36 EST
When starting NFS on my freshly network-installed Fedora 16, I get the following error message from systemd:

# systemctl start nfs.service

Failed to issue method call: Unit nfs.service failed to load: No such file or directory. See system logs and 'systemctl status nfs.service' for details.

Well, the "details" are:

# systemctl status nfs.service
nfs.service
          Loaded: error (Reason: No such file or directory)
          Active: inactive (dead)

There's nothing in the system logs either.
Comment 1 Erik Terwan 2011-11-10 06:13:59 EST
Right, filed this bug report too soon. The message: "Failed to issue method call: Unit nfs.service failed to load: No such file or directory. See system logs and 'systemctl status nfs.service' for details" seems to be systemd's way of telling that a service does not exist (there are better ways, I presume).

So there is no nfs.service. In Fedora 16 it is called nfs-server.service.

# systemctl start nfs-server.service

did start nfs.