Bug 1043860 - Running autofs causes system to hang on reboot or shutdown
Summary: Running autofs causes system to hang on reboot or shutdown
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: autofs
Version: 19
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ian Kent
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-17 11:25 UTC by S Hutchinson
Modified: 2015-02-17 19:41 UTC (History)
1 user (show)

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


Attachments (Terms of Use)

Description S Hutchinson 2013-12-17 11:25:33 UTC
Description of problem:
A system running autofs will not reboot or shut down.

Version-Release number of selected component (if applicable):
autofs version 5.0.7-28

How reproducible:
If autofs is running then the system does not reboot or shut down.

If autofs is stopped successfully using 'systemctl stop autofs.service' the system reboots or shuts down.

Sometimes when stopping autofs the following appears:

Failed to issue method call: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. 
Warning: Unit file of autofs.service changed on disk, 'systemctl --system daemon-reload' recommended.

If this happens the system hangs and has to be power-cycled.

If there is only one entry in /etc/auto_master the problem does not occur. If there is more than one entry, then it does.

Steps to Reproduce:
1. Add two entries to /etc/auto.master
2. Start autofs.service
3. Reboot or shut down either from the GUI or from the command line.

Actual results:
System hangs. 

Expected results:
System should shut down or reboot.

Additional info:
This happens in Fedora 18 too.

Comment 1 Fedora End Of Life 2015-01-09 20:53:11 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 2 Fedora End Of Life 2015-02-17 19:41:07 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.