Red Hat Bugzilla – Bug 103160
autofs doesn't see ldap based file systems after reboot
Last modified: 2007-04-18 12:57:10 EDT
From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030708 Description of problem: We use LDAP based tree lookup for autofs in our organization. If the (LDAP and NFS) server is rebooted, it won't find its own ldap based mounts. Reason: The autofs daemon is started at S28. LDAP is started at S39. So when the autofs does LDAP lookup to find all the trees, it gets no result because the LDAP server is not yet up. Version-Release number of selected component (if applicable): autofs-3.1.7-36 How reproducible: Always Steps to Reproduce: 1. Configure a server to be NFS and LDAP server 2. Configure autofs to use LDAP for NFS lookup 3. Reboot Actual Results: % /sbin/service autofs status Configured Mount Points: ------------------------ /usr/sbin/automount /home ldap ldap.hutweide.de:nisMapName=auto.home,dc=hutweide,dc=de hard,intr,lock,v3,rsize=8192,wsize=8192 Active Mount Points: -------------------- % Expected Results: % /sbin/service autofs status Configured Mount Points: ------------------------ /usr/sbin/automount /home ldap ldap.hutweide.de:nisMapName=auto.home,dc=hutweide,dc=de hard,intr,lock,v3,rsize=8192,wsize=8192 Active Mount Points: -------------------- /usr/sbin/automount /home ldap ldap.hutweide.de:nisMapName=auto.home,dc=hutweide,dc=de hard,intr,lock,v3,rsize=8192,wsize=8192 % Additional info: Simply shifting the start levels of autofs from S28 K72 to S40 K60 solves the problem.
I'm not sure whether it's preferrable to shift autofs later in the boot sequence, or make ldap come up earlier. I'd rather not move later in the boot, as I'm not sure if that hinders other services. Nalin, are there any issues moving ldap sooner in the boot? Does it depend on other services?
*** Bug 120509 has been marked as a duplicate of this bug. ***
Red Hat apologizes that these issues have not been resolved yet. We do want to make sure that no important bugs slip through the cracks. Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. They are maintained by the Fedora Legacy project (http://www.fedoralegacy.org/) for security updates only. If this is a security issue, please reassign to the 'Fedora Legacy' product in bugzilla. Please note that Legacy security update support for these products will stop on December 31st, 2006. If this is not a security issue, please check if this issue is still present in a current Fedora Core release. If so, please change the product and version to match, and check the box indicating that the requested information has been provided. If you are currently still running Red Hat Linux 7.3 or 9, please note that Fedora Legacy security update support for these products will stop on December 31st, 2006. You are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Any bug still open against Red Hat Linux 7.3 or 9 at the end of 2006 will be closed 'CANTFIX'. Again, if this bug still exists in a current release, or is a security issue, please change the product as necessary. We thank you for your help, and apologize again that we haven't handled these issues to this point.
Red Hat Linux 7.3 and Red Hat Linux 9 are no longer supported by Red Hat, Inc. f you are currently still running Red Hat Linux 7.3 or 9, you are strongly advised to upgrade to a current Fedora Core release or Red Hat Enterprise Linux or comparable. Some information on which option may be right for you is available at http://www.redhat.com/rhel/migrate/redhatlinux/. Closing as CANTFIX.