Red Hat Bugzilla – Bug 156819
autofs complains about objectclass but works using ldap
Last modified: 2007-11-30 17:11:05 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Description of problem:
Using what appears to be a RH/Fedora standard ldap automount map, every mount attempt gives a similar error to the following:
May 4 09:00:26 gold automount: lookup(ldap): got answer, but no first entry for (&(objectclass=nisObject)(cn=pgienger))
Regardless of the error, the mount is successful and things go happily on their way. The relevant LDIF information is below for this particular entry. It doesn't make much sense that a fully working system should error so consistantly.
I don't believe there are any other relevant system configuration changes to the client or the server. The latest server was a fresh install/patched stock FC3 machine and exhibits the behavior as soon as it is configured as an LDAP client and autofs is restarted.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. configure LDAP client
2. (re)start autofs
3. change to an automounted directory
Actual Results: Directory was mounted, error logged
Expected Results: Directory mounted, no errors on client side except maybe a notification of the directory being mounted.
This is caused because of the support for extra ldap schemas. Those errors can
be safely ignored and should only be present when logging debug messages in FC-5.
Could you specify the extra schemas that caused problem? Thanks.
Initially autofs would only look for objectClass=nisObject, the autofs in FC-3
adds support for objectClass=nisObject & objectClass=automount. Because autofs
checks for both types of maps it prints an error when it looks for maps in the
schema that the site is not using, but it will still succeed if it finds maps in
the other schema.
new packages should suppress this warning.
Could you specify the packages? I am using RHEL 3 & 4, and will be very happy to
see the problem be fixed on those OS versions too.
This bug has been fixed in autofs-4.1.3-158 and later.