[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
Re: autofs and OpenLDAP integration
Nalin Dahyabhai wrote:
>
> On Fri, Jul 20, 2001 at 06:25:30PM +0200, Jehan PROCACCIA wrote:
> > $/etc/init.d/autofs status
> > Configured Mount Points:
> > ------------------------
> > /usr/sbin/automount /mci ldap
> > openldap.int-evry.fr:ou=auto.mci,dc=int-evry,dc=fr
> >
> > Active Mount Points:
> > --------------------
> > /usr/sbin/automount /mci ldap
> > openldap.int-evry.fr:ou=auto.mci,dc=int-evry,dc=fr
> >
> > It seems to work better but now it is looking for a library that is not
> > present ?
> > automount[24668]: cannot open lookup module
> > openldap (/usr/lib/autofs//lookup_openldap.so: cannot open shared object
> > file: No such file or directory)
> >
> > where should it come from ?
>
> Whoa, that's freaky. It should be using /usr/lib/autofs/lookup_ldap.so
> for looking up entries using LDAP.
I think it's my fault, with my confusion on ldap key word and openldap
hostname
here's what I had
# This entry causes autofs to start up another automounter on /mci/mci.
dn: cn=mci,ou=auto.mci,dc=int-evry,dc=fr
objectClass: top
objectClass: automount
description: mci home directories
cn: mci
automountInformation: -fstype=autofs
openldap:ou=auto.mci.mci,dc=int-evry,dc=fr
I changed latest line with :
automountInformation: -fstype=autofs
ldap:ou=auto.mci.mci,dc=int-evry,dc=fr
Here's the ldap keyword is used and not the hostname of the ldap server
(Am I right ?) Any way I hadn't anymore the library problem now.
however doesn't mount the homedir either :-(
here's what logs says:
Jul 23 12:15:25 openldap automount[1651]: lookup(ldap): couldn't connect
to (null)
Jul 23 12:15:25 openldap automount[1650]: mount(autofs): sub automount
returned status 0x100
Again to avoid confusion I simplified the problem, now I tried to mount
the homedir /mci/em/doucet of user doucet (/mci/mci for procacci could
give confusion with the mci key followed by mci subdirectory ...)
Here's the ldif:
# This entry is more or less a place-holder for automount entries for
# directories which get mounted under /mci.
dn: ou=auto.mci,dc=int-evry,dc=fr
objectClass: top
objectClass: organizationalUnit
ou: auto.mci
# This entry causes autofs to start up another automounter on /mci/em.
dn: cn=em,ou=auto.mci,dc=int-evry,dc=fr
objectClass: top
objectClass: automount
description: em home directories
cn: em
automountInformation: -fstype=autofs
ldap:ou=auto.mci.em,dc=int-evry,dc=fr
# This entry is more or less a place-holder for automount entries for
# directories which get mounted under /mci/em.
dn: ou=auto.mci.em,dc=int-evry,dc=fr
objectClass: top
objectClass: organizationalUnit
ou: auto.mci.em
# This is a wildcard entry for any user whose home directory is under
# /mci/em (this includes doucet, too I guess).
dn: cn=/,ou=auto.mci.em,dc=int-evry,dc=fr
objectClass: top
objectClass: automount
description: generic home directory
cn: /
automountInformation: -rw,intr,soft,quota nfsserver:/user2000/em/&
And here is the result:
Red Hat Linux release 7.1 (Seawolf)
Kernel 2.4.3-12 on an i686
login: doucet
Password:
No directory /mci/em/doucet!
Logging in with home = "/".
Jul 23 12:15:25 openldap login(pam_unix)[1649]: session opened for user
doucet by (uid=0)
Jul 23 12:15:25 openldap automount[1606]: attempting to mount entry
/mci/em
Jul 23 12:15:25 openldap automount[1651]: starting automounter version
3.1.7, path = /mci/em, maptype = ldap, mapname =
ou=auto.mci.em,dc=int-evry,dc=fr
Jul 23 12:15:25 openldap automount[1651]: lookup(ldap): couldn't connect
to (null)
Jul 23 12:15:25 openldap automount[1650]: mount(autofs): sub automount
returned status 0x100
Jul 23 12:15:25 openldap automount[1650]: mount(autofs): failed to mount
ldap:ou=auto.mci.em,dc=int-evry,dc=fr on /mci/em
Jul 23 12:15:25 openldap -- doucet[1649]: LOGIN ON pts/6 BY doucet FROM
openldap
Jul 23 12:15:25 openldap automount[1606]: attempting to mount entry
/mci/em
Jul 23 12:15:25 openldap automount[1654]: starting automounter version
3.1.7, path = /mci/em, maptype = ldap, mapname =
ou=auto.mci.em,dc=int-evry,dc=fr
Jul 23 12:15:25 openldap automount[1654]: lookup(ldap): couldn't connect
to (null)
Jul 23 12:15:25 openldap automount[1653]: mount(autofs): sub automount
returned status 0x100
Jul 23 12:15:25 openldap automount[1653]: mount(autofs): failed to mount
ldap:ou=auto.mci.em,dc=int-evry,dc=fr on /mci/em
Jul 23 12:15:25 openldap login(pam_unix)[1649]: session closed for user
doucet
It's getting hard ! Is it working for you ?
Thanks again for your help .
>
> > Jul 20 13:30:14 openldap automount[24663]: mount(autofs): failed to
> > mount openldap:ou=auto.mci.mci,dc=int-evry,dc=fr on /mci/mci
> > Jul 20 13:30:14 openldap automount[24602]: attempting to mount entry
> > /mci/mci
> > Jul 20 13:30:14 openldap automount[24668]: starting automounter version
> > 3.1.7, path = /mci/mci, maptype = openldap, mapname =
> > ou=auto.mci.mci,dc=int-evry,dc=fr
> > Jul 20 13:30:14 openldap automount[24668]: cannot open lookup module
> > openldap (/usr/lib/autofs//lookup_openldap.so: cannot open shared object
> > file: No such file or directory)
>
> That's very strange. Autofs is somehow determining that the map type is
> "openldap" instead of "ldap", which is wrong. It then uses the map type
> to construct the path for the lookup module to use ("yp" maps are looked
> up using lookup_yp.so, "nisplus" maps using lookup_nisplus.so, and so on).
>
> Off-hand, a workaround would be to symlink lookup_openldap.so to
> lookup_ldap.so in /usr/lib/autofs, but I'm stumped as to where it's
> getting the wrong map type passed in, since the script is reporting the
> right configuration setup.
>
> Nalin
--
Jehan Procaccia
Institut National des Telecommunications| Email:
Jehan.Procaccia@int-evry.fr
MCI, Moyens Communs Informatiques | Tel : +33 (0) 160764436
9 rue Charles Fourier 91011 Evry France | Fax : +33 (0) 160764321