Red Hat Bugzilla – Bug 118657
autofs can't handle ldap information for nfs mountpoints
Last modified: 2007-11-30 17:07:12 EST
Description of problem:
when using ldap for distributung nfs mounts, autofs 4.1.0-2
will not be able to resolve the correct mount points and
therefore automountd can't handle these mount points.
here's my log from /var/log/mesages and my ldap
==> /var/log/slapd.log <==
Mar 18 16:44:09 theseus slapd: daemon: conn=103 fd=14
connection from IP=192.168.15.11:40753 (IP=0.0.0.0:389) acc
Mar 18 16:44:09 theseus slapd: conn=103 op=0 BIND dn=""
Mar 18 16:44:09 theseus slapd: conn=103 op=0 RESULT tag=97
==> /var/log/messages <==
Mar 18 16:44:09 theseus automount: using timeout 300 seconds;
freq 75 secs
Mar 18 16:44:09 theseus automount: lookup(ldap): query failed
Mar 18 16:44:10 theseus automount: lookup(ldap): query failed
Mar 18 16:44:10 theseus automount: failed to load map, exiting
Mar 18 16:44:10 theseus automount: failed to remove dir
`^W^E^Hâ^V]Ã^P: No such file or directory
as you can see in slapd.log there's >>> BIND dn="" <<< which normally
should be resolved/mapped to >>>
that's why automount can't load the maps tells "No such file or
directory" referring to a file/dirname that seems to be real ugly
Version-Release number of selected component (if applicable): 4.1.0-2
1) install ldap server
2) create automount map entries within ldap server
3) try using these entries with installed autofs 4.1.0-2
deinstall autofs 4.1.0-2 and install autofs-3.1.7-36 (is used the
rpm from redhat 9.0) and everything works fine...
autofs-3.1.7-41 is the version of autofs that ships with RHEL 3. We
do not support the two version of autofs you list in the bug report
under RHEL 3.
Having said that, at least one of the problems you mentioned is fixed
in autofs-4.1.1. Namely, the garbage in the log file was due to an
errant use of a freed pointer.