initialization of autofs is erratic (no nis maps available)
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| autofs5 (Ubuntu) |
Opinion
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: autofs5
I am using autofs to mount nfs home dirs. My autofs configuration uses NIS maps, and the auto.master looks like:
+auto.master
However, the NIS maps are not available after reboot. I have several scenarios.
Case 1
---------
NIS is most working.
Work around:
1) I have to start nis ( /etc/init.d/nis start) because strangely it has not been started.
2) I restart atufos (stop autofs, start autofs)
Case 2
--------
statd is not working.
Work around:
1) Start statd manually (/etc/init.d/statd start)
2) I restart atufos (stop autofs, start autofs)
It seems that it is related to the way the initialization daemon starts the services. It has a big impact on the system, since users cannot login after NIS and autofs is working, and manual intervention as root has to be performed.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: autofs5 5.0.4-3.1ubuntu5
ProcVersionSign
Uname: Linux 2.6.32-24-generic x86_64
Architecture: amd64
Date: Wed Aug 18 17:09:36 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
LANG=es_ES.UTF-8
SHELL=/bin/bash
SourcePackage: autofs5
| Enrique (enrique-garcia) wrote | #1 |
| Serge Hallyn (serge-hallyn) wrote | #2 |
| Changed in autofs5 (Ubuntu): | |
| status: | New → Incomplete |
| importance: | Undecided → Medium |
| tags: | added: upstart |
| Changed in autofs5 (Ubuntu): | |
| importance: | Medium → Wishlist |
| status: | Incomplete → Opinion |
| Enrique (enrique-garcia) wrote | #3 |
Thanks for taking the time to report this bug and helping to make Ubuntu
better. Please clarify - are you saying that upon rebooting the system, you
randomly get either statd or nis not starting? While other times both start
fine and then autofs starts fine? If so, do you have any idea why nis and
statd are failing to start?
Or, are you saying it is simply a timing issue, and autofs is sometimes started
before nis and statd start?
Note that since your autofs configuration depends upon nis and statd, I think
it would be good to modify your /etc/init/autofs to wait until both nis and
statd are available.