Bug 118444 - ldap map lookup broken
ldap map lookup broken
Status: CLOSED RAWHIDE
Product: Fedora
Classification: Fedora
Component: autofs (Show other bugs)
rawhide
All Linux
medium Severity medium
: ---
: ---
Assigned To: Nalin Dahyabhai
Brock Organ
:
Depends On:
Blocks: FC2Blocker
  Show dependency treegraph
 
Reported: 2004-03-16 14:35 EST by Bill Nottingham
Modified: 2014-03-16 22:43 EDT (History)
3 users (show)

See Also:
Fixed In Version: 4.1.1-3
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-03-19 16:10:56 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)
autofs config file (273 bytes, text/plain)
2004-03-16 14:36 EST, Bill Nottingham
no flags Details

  None (edit)
Description Bill Nottingham 2004-03-16 14:35:22 EST
Given the attached auto.master, startup fails with:

lookup(ldap): query failed for (&(objectcalss=nisObject))
lookup(ldap): query failed for (&(objectclass=automount))
failed to load map, exiting
failed to remove dir ^PP: No such file or directory.

The failed to remove directory error looks pretty bogus too.
Comment 1 Bill Nottingham 2004-03-16 14:36:10 EST
Created attachment 98578 [details]
autofs config file
Comment 2 Jeffrey Moyer 2004-03-18 11:32:51 EST
The ldap path initialization code changed between versions 3 and 4.  I
ported forward the version 3 way of parsing the ldap server name and
base DN.  This fix will appear in fc2t2.

-Jeff
Comment 3 Bill Nottingham 2004-03-18 11:38:25 EST
Now, with a wildcard map, if I try to mount
/home/<some-user-whose-homedir-isn't-in-autofs>, it mounts the last
one in the entry.
Comment 4 Jeffrey Moyer 2004-03-18 11:50:51 EST
Bill, could you provide a little more information?  When you say you
try to mount, do you issue the mount command by hand?  Do you try to
cd to a directory that doesn't exist?  And when you say it mounts the
last one in the entry, what precisely do you mean?  Exact steps to
reproduce the problem would be helpful.

Thanks,
Jeff
Comment 5 Stephen Tweedie 2004-03-18 12:20:01 EST
I'm seeing exactly the same symptoms as Bill, using a NIS autofs map.
 "ls /home/foo" where foo is caught by the wildcard results in a
directory-not-found, and the logs show autofs was trying to mount the
last entry listed in "ypcat auto.home" (which happens to be
unreachable at present, hence the mount fails.)
Comment 6 Stephen Tweedie 2004-03-19 06:39:42 EST
Appears fixed in autofs-4.1.1-1, at least for my NIS case.
Comment 7 Jeffrey Moyer 2004-03-19 14:51:40 EST
autofs-4.1.1 fixed the wildcard issues.  It broke ldap, though.  I
fixed a bug dealing with too short timeouts, and all seems well.  I've
tested the nis case and the ldap case.  Both work for me in
autofs-4.1.1-3, which I built into fc2-HEAD.

-Jeff
Comment 8 Bill Nottingham 2004-03-19 16:10:56 EST
Works for me.

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