RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 994989 - when service nfs start fail, should output useful error info to user.
Summary: when service nfs start fail, should output useful error info to user.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: nfs-utils
Version: 7.0
Hardware: Unspecified
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Steve Dickson
QA Contact: Red Hat Kernel QE team
URL:
Whiteboard:
Depends On:
Blocks: 1002484
TreeView+ depends on / blocked
 
Reported: 2013-08-08 11:03 UTC by JianHong Yin
Modified: 2013-08-29 11:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1002484 (view as bug list)
Environment:
Last Closed: 2013-08-29 09:59:13 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description JianHong Yin 2013-08-08 11:03:28 UTC 
Description of problem:
when service nfs start  fail, should output useful error info to user.
more than "Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details."

Version-Release number of selected component (if applicable):
RedHatEnterpriseWorkstation 7.0
Linux dhcp12-125.nay.redhat.com 3.10.0-0.rc7.64.el7.x86_64 #1 SMP Tue Jun 25 10:00:04 EDT 2013 x86_64 x86_64 x86_64 GNU/Linux
nfs-utils-1.2.8-2.0.el7.x86_64

How reproducible:
100%

Steps to Reproduce:
1.  echo 'RPCNFSDARGS="--no-tcp"' >/etc/sysconfig/nfs
    service nfs start
2.
3.

Actual results:
Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.

Expected results:
---->
Job for nfs-server.service failed. See 'systemctl status nfs-server.service' and 'journalctl -xn' for details.
+rpc.nfsd: version 4 requires the TCP protocol
<----
Additional info:
  police: Stop, Your application does not meet the requirements
          Specific reason please ask my colleagues 'journalctl' in next room
  people: ??? Why you do not tell me???
Comment 5 JianHong Yin 2013-08-29 10:01:59 UTC 
I means that  it should give user the reason directly in the stderr. 
-like in RHEL6 and RHEL5
Comment 6 Steve Dickson 2013-08-29 10:13:38 UTC 
(In reply to Yin.JianHong from comment #5)
> I means that  it should give user the reason directly in the stderr. 
> -like in RHEL6 and RHEL5
nfs-utils has no way of controlling that so you should open
up the bug against systemd.
Comment 7 JianHong Yin 2013-08-29 10:30:39 UTC 
(In reply to Steve Dickson from comment #6)
> (In reply to Yin.JianHong from comment #5)
> > I means that  it should give user the reason directly in the stderr. 
> > -like in RHEL6 and RHEL5
> nfs-utils has no way of controlling that so you should open
> up the bug against systemd.

Hi steve, thanks your explanation.
But from the customer perspective, we do not know the background complete,
why must use the systemd?? now  it  cause many issues ...
Comment 8 Steve Dickson 2013-08-29 11:07:41 UTC 
(In reply to Yin.JianHong from comment #7)
> (In reply to Steve Dickson from comment #6)
> > (In reply to Yin.JianHong from comment #5)
> > > I means that  it should give user the reason directly in the stderr. 
> > > -like in RHEL6 and RHEL5
> > nfs-utils has no way of controlling that so you should open
> > up the bug against systemd.
> 
> Hi steve, thanks your explanation.
> But from the customer perspective, we do not know the background complete,
> why must use the systemd?? now  it  cause many issues ...

Back in the Fedora 17 time frame there was a big push to speed
up boot/reboot speeds. So it was decided to have system services 
start asynchronous instead of synchronous like the old system 5
scripts were. So old /bin/init process was replaced by systemd.

Unfortunately the systemd people did not care or think it was
necessary to be backwards compatible with the old scripts.

So yes, systemd has caused a lot of problems but its also solved
a few...
Note You need to log in before you can comment on or make changes to this bug.