Bug 55931 - "service autofs start" starts daemon multiple times
"service autofs start" starts daemon multiple times
Status: CLOSED DUPLICATE of bug 65003
Product: Red Hat Linux
Classification: Retired
Component: autofs (Show other bugs)
9
All Linux
low Severity low
: ---
: ---
Assigned To: Nalin Dahyabhai
Brock Organ
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2001-11-08 19:56 EST by Michael Schwendt
Modified: 2006-02-21 13:48 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:48:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Michael Schwendt 2001-11-08 19:56:24 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012

Description of problem:
Running "service autofs start" multiple times starts the automount daemon
multiple times instead of exiting with a "[FAILED]" error.

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

How reproducible:
Always

Steps to Reproduce:
1. service autofs start
[  OK  ]
2. service autofs start
[  OK  ]
3. service autofs start
[  OK  ]
4. service autofs status ; pidof /usr/sbin/automount
See list of "Active Mount Points" and find three automount processes.



Actual Results:  Multiple /usr/sbin/automount processes.

Expected Results:  Running "service autofs start" more than once should
have given a "[FAILED]" error.

Additional info:

Might be related to bug #55715.
Comment 1 Jesse Keating 2002-04-19 01:54:44 EDT
pidof /usr/sbin/automount doesn't return any pids... do you have to have mounts
defined for automount to duplicate?
Comment 2 Michael Schwendt 2002-04-19 07:35:20 EDT
On Skipjack-beta2 with only /misc/cd enabled in /etc/auto.misc:

# service autofs start
Starting automount:                                        [  OK  ]
# service autofs start
Starting automount:                                        [  OK  ]
# service autofs start
Starting automount:                                        [  OK  ]
# service autofs start
Starting automount:                                        [  OK  ]

# service autofs status                          
Configured Mount Points:
------------------------
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc  

Active Mount Points:
--------------------
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc

# ps auxw | grep auto
root       637  0.0  0.2  1472  584 ?        S    11:19   0:00
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
root      1886  0.0  0.2  1472  584 pts/2    S    13:30   0:00
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
root      1949  0.0  0.2  1472  584 pts/2    S    13:30   0:00
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
root      2012  0.0  0.2  1472  584 pts/2    S    13:30   0:00
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc
root      2075  0.0  0.2  1472  584 pts/2    S    13:30   0:00
/usr/sbin/automount --timeout 60 /misc file /etc/auto.misc

#  pidof /usr/sbin/automount 
2075 2012 1949 1886 637
Comment 3 Jesse Keating 2002-04-22 17:39:54 EDT
So, is this an issue on Red Hat Linux 7.2 or on the SkipJack beta2 ?
Comment 4 Michael Schwendt 2002-04-22 18:10:35 EDT
It is reproducible on both Enigma and Skipjack. Two different machines.
Comment 5 Michael Schwendt 2002-06-18 06:27:40 EDT
Reproducible on Valhalla.

# service autofs start
Starting automount:                                        [  OK  ]
# service autofs start
Starting automount:                                        [  OK  ]
# service autofs start
Starting automount:                                        [  OK  ]
# service autofs start
Starting automount:                                        [  OK  ]

# pidof automount
12627 12600 12575 12512 12485 12458 12393 12366 12341 12278 12251 12224

# cat /proc/mounts | grep ^auto
automount(pid12224) /misc autofs rw 0 0
automount(pid12251) /home/ms/public_html/ct/mnt autofs rw 0 0
automount(pid12278) /home/ms/public_html/mount autofs rw 0 0
automount(pid12366) /home/ms/public_html/ct/mnt autofs rw 0 0
automount(pid12393) /home/ms/public_html/mount autofs rw 0 0
automount(pid12341) /misc autofs rw 0 0
automount(pid12458) /misc autofs rw 0 0
automount(pid12485) /home/ms/public_html/ct/mnt autofs rw 0 0
automount(pid12512) /home/ms/public_html/mount autofs rw 0 0
automount(pid12600) /home/ms/public_html/ct/mnt autofs rw 0 0
automount(pid12627) /home/ms/public_html/mount autofs rw 0 0
automount(pid12575) /misc autofs rw 0 0
Comment 6 Michael Schwendt 2003-01-25 13:36:04 EST
Original report was for Red Hat Linux 7.2 (Enigma). Reproducible on Psyche 8.0.93.
Comment 7 Michael Schwendt 2003-01-25 13:37:20 EST
Typo. Meant Phoebe (8.0.93).
Comment 8 Adam Spiers 2003-02-06 08:01:39 EST
Reproducible on Advanced Server 2.1.

A partial workaround appears to be the following sequence:

service autofs stop
killall -9 automount
service autofs start

And then everything appears to work again, despite /proc/mounts
and /etc/mtab being corrupted with multiple entries.

However, before applying the workaround, if anything tries to access
an automount, I get a load of processes in uninterruptible sleep
(D) which can render the machine fairly useless.  So please consider
raising the severity.  (This should be easy to fix anyway, right?)
Comment 9 Adam Spiers 2003-02-07 13:07:42 EST
Please see my attachment to bug 65003 which will
hopefully fix both bugs.
Comment 10 Jeff Moyer 2004-03-19 16:43:45 EST

*** This bug has been marked as a duplicate of 65003 ***
Comment 11 Red Hat Bugzilla 2006-02-21 13:48:14 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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