Bug 866006 - systemctl status nfs-idmap.service - failed
Summary: systemctl status nfs-idmap.service - failed
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Steve Dickson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-13 08:20 UTC by Flóki Pálsson
Modified: 2012-10-13 14:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-10-13 14:03:46 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Flóki Pálsson 2012-10-13 08:20:59 UTC
Description of problem:
systemctl status nfs-idmap.service - failed 

Version-Release number of selected component (if applicable):
nfs-utils-1.2.6-12.fc18.x86_64


How reproducible:
always 

Steps to Reproduce:
1.  # systemctl status nfs-idmap.service
2.
3.
  
Actual results:
nfs-idmap.service - NFSv4 ID-name mapping daemon
	  Loaded: loaded (/usr/lib/systemd/system/nfs-idmap.service; disabled)
	  Active: failed (Result: exit-code) since Fri, 12 Oct 2012 20:10:29 +0000; 12h ago
	  CGroup: name=systemd:/system/nfs-idmap.service

Oct 12 20:10:29 localhost systemd[1]: Starting NFSv4 ID-name mapping daemon...
Oct 12 20:10:29 localhost systemd[1]: Failed to start NFSv4 ID-name mapping daemon.

Expected results:
All services should start properly and systemctl reports no failed service
http://fedoraproject.org/wiki/QA:Testcase_Services_start

Additional info:
see bug 864670

Comment 1 Flóki Pálsson 2012-10-13 11:54:41 UTC
now ok
I reinstalled from Fedora-18-Beta-TC3-x86_64-Live-Desktop.iso
and yum update 
and reboot

# systemctl status nfs-idmap.service
nfs-idmap.service - NFSv4 ID-name mapping daemon
	  Loaded: loaded (/usr/lib/systemd/system/nfs-idmap.service; disabled)
	  Active: inactive (dead)
	  CGroup: name=systemd:/system/nfs-idmap.service

[root@localhost ~]#


Note You need to log in before you can comment on or make changes to this bug.