All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jim Summers <jsummers@bachman.cs.ou.edu>
To: Rich West <Rich.West@wesmo.com>
Cc: autofs@linux.kernel.org
Subject: Re: autofs5 + ldap + ldap replication
Date: Tue, 07 Aug 2007 11:52:33 -0500	[thread overview]
Message-ID: <46B8A351.1010901@cs.ou.edu> (raw)
In-Reply-To: <46B88EA1.3060707@wesmo.com>

Rich West wrote:
> Jim Summers wrote:
>> Rich West wrote:
>>   
>>>> Ian Kent wrote:
>>>>       
>>>>> On Tue, 2007-07-24 at 11:48 +0800, Ian Kent wrote:
>>>>>   
>>>>>         
>>> After some tinkering I did finally figure things out.  It had to do with 
>>> the automountInformation field.
>>>
>>> In the LDAP database, I had:
>>> automountInformation: ldap:ldap.mydomain.com:ou=auto.home,dc=mydomain,dc=com
>>>
>>> I found (on an obscure posting elsewhere) that I could get it to work 
>>> via this entry:
>>> automountInformation: ldap:ou=auto.home,dc=mydomain,dc=com
>>>
>>> Basically, I eliminated the LDAP server from the entry.  I'm going to 
>>> hazard a guess, but, since autofs sees that it is an ldap entry, it just 
>>> uses the system's bindings in order to resolve the ou...  Anyhow, it 
>>> works like a champ on FC5, FC6, and FC7.
>>>     
>> Hi Rich,
>>
>> Where are you setting the ldap server?  I have my ldap config in 
>> /etc/ldap.conf.  when  i start autofs with the following map in /etc/auto.master:
>>
>> /home   ldap:ou=auto.home,dc=it,dc=ou,dc=edu
>>
>> i see the following in my debug file:
>>
>> Aug  7 08:58:35 leech automount[11991]: master_do_mount: mounting /home
>> Aug  7 08:58:35 leech automount[11991]: lookup_nss_read_map: reading map ldap 
>> ou=auto.home,dc=it,dc=ou,dc=edu
>> Aug  7 08:58:35 leech automount[11991]: parse_server_string: lookup(ldap): 
>> Attempting to parse LDAP information from string 
>> "ou=auto.home,dc=it,dc=ou,dc=edu".
>> Aug  7 08:58:35 leech automount[11991]: parse_server_string: lookup(ldap): 
>> server "(default)", base dn "ou=auto.home,dc=it,dc=ou,dc=edu"
>>
>> .....
>>
>> Aug  7 09:24:34 leech automount[3283]: lookup_init: lookup(ldap): cannot 
>> connect to server
>>
>> not sure where to specify default server.  in this case, for replication, i 
>> guess a list of servers.  in ldap.conf i have:
>>
>> uri ldaps://serve0 ldaps://serve1
>>
>> so i am not sure that autofs will handle the ssl connections.
>>
>> this would be really useful to get working so that the mounts have some 
>> failover potential.
>>
>> ideas / suggestions?
>>
>> tia
>>
>>
>>   
> 
> I have it in both /etc/ldap.conf and /etc/openldap/ldap.conf, and the
> format is the same:
> uri <type>://host:port/
> For example:
> uri ldap://ldap1.mydomain.com:389/ ldap://ldap2.mydomain.com:389/
> 
> The only difference I have between the two files is that uri is
> capitalized in /etc/openldap/ldap.conf.  I am not sure if there is any
> case sensitivity here, but the default file had it capitalized and I
> just didn't take the chance. :)
> 
> Autofs (along with most of the clients) uses /etc/openldap/ldap.conf. 
> /etc/ldap.conf is primarily used by the nss_ldap/pam_ldap for user
> authentication.
> 
> The only thing I have not yet adjusted is the 'failover period' that you
> referred to.  I don't know what would be a good value for the amount of
> time to allow before failing over to the replica, and I don't yet know
> where that value in order to adjust it.  It's not an autofs
> configuration option from what I can tell...

That worked.  I have been symlinking the /etc/ to /etc/openldap.  I broke the 
link and then created a separate file in /etc/openldap and all is well now.  I 
have seen timelimit and idle_timelimit but neither seem appropriate for an 
adjustment to the bind timeout.  I'll post if i come across anything.

thanks again.

> 
> -Rich

-- 
Jim Summers
School of Computer Science-University of Oklahoma
-------------------------------------------------

  reply	other threads:[~2007-08-07 16:52 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-07  1:32 autofs5 + ldap + ldap replication Rich West
2007-08-07 14:33 ` Jim Summers
2007-08-07 15:24   ` Rich West
2007-08-07 16:52     ` Jim Summers [this message]
2007-08-08 11:33       ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2007-07-15  2:26 Rich West
2007-07-15  8:31 ` jehan procaccia
     [not found]   ` <469A39D5.8040304@wesmo.com>
2007-07-16 18:28     ` Rich West
2007-07-16 15:17 ` Ian Kent
2007-07-16 18:26   ` Rich West
2007-07-16 18:59     ` Jeff Moyer
2007-07-16 19:54       ` Rich West
2007-07-17  6:20         ` Ian Kent
2007-07-23 16:37           ` Rich West
2007-07-24  3:48             ` Ian Kent
2007-07-24  3:56               ` Ian Kent
2007-07-24 16:55                 ` Rich West

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=46B8A351.1010901@cs.ou.edu \
    --to=jsummers@bachman.cs.ou.edu \
    --cc=Rich.West@wesmo.com \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.