Bug 1040368 - nfsd and mountd sometimes fail to start right after stop with 'Address already in use'
Summary: nfsd and mountd sometimes fail to start right after stop with 'Address alread...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: nfs-utils
Version: 19
Hardware: Unspecified
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: 2013-12-11 10:14 UTC by Yedidyah Bar David
Modified: 2015-02-17 19:36 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-02-17 19:36:21 UTC
Type: Bug


Attachments (Terms of Use)
part of /var/log/messages (31.12 KB, application/x-gzip)
2013-12-11 10:14 UTC, Yedidyah Bar David
no flags Details

Description Yedidyah Bar David 2013-12-11 10:14:08 UTC
Created attachment 835207 [details]
part of /var/log/messages

Description of problem:

engine-setup (from ovirt) stops and then starts nfs-service. This sometimes fails with this in /var/log/messages:
Dec 11 10:22:02 ovirte1 rpc.nfsd[6055]: rpc.nfsd: unable to bind inet TCP socket: errno 98 (Address already in use)
It seems as if 'stop' returns a bit too early and when start runs, the socket is still in use.

Version-Release number of selected component (if applicable):

nfs-utils-1.2.8-6.0.fc19.x86_64
kernel 3.11.10-200.fc19.x86_64
system updated with 'yum update'

How reproducible:

It might be related to enabling a service, which requires reloading systemd.

I ran the following loop:
while true; do /bin/systemctl enable httpd.service; service nfs-server stop; echo $?; service nfs-server start; echo $?; date; sleep 5; done
and it failed about 5% of the attempts or so.

Note that it might affect also rhel - we closed with no solution #848648 #1033964 which seem similar.

Steps to Reproduce:
1. Do some stuff ? (not sure what)
2. service nfs-server stop
3. service nfs-server start

Actual results:

Sometimes stop succeeds and start fails

Expected results:

start should always succeeed

Additional info:

The attached file is the output of:

egrep -i 'systemd.*reloading|nfs|mountd|exportfs' /var/log/messages | gzip > ~/nfslog.gz

Comment 1 Yedidyah Bar David 2013-12-11 10:23:04 UTC
(In reply to Yedidyah Bar David from comment #0)
> Note that it might affect also rhel - we closed with no solution #848648
> #1033964 which seem similar.

Sorry, that's BZ #848684 (and BZ #1033964).

Comment 4 Fedora End Of Life 2015-01-09 20:49:59 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Fedora End Of Life 2015-02-17 19:36:21 UTC
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


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