All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: rsmits-l <rsmits-l@tudelft.nl>, autofs@vger.kernel.org
Subject: Re: Problem with autofs and ldap
Date: Fri, 17 Oct 2014 16:51:40 +0800	[thread overview]
Message-ID: <5440D89C.6040001@themaw.net> (raw)
In-Reply-To: <543E6912.8050109@tudelft.nl>

On 15/10/14 20:31, rsmits-l wrote:
> Hello,
>
> I have a very weird issue that maybe someone sounds familiar. I have
> placed our automount entry's in our Active Directory / LDAP. Problem is
> that is it not stable. After a restart of autofs I sometimes only see
> half of our map entry's. Sometimes 75 %.

That's odd if the map is actually being read, yes.
At one time autofs didn't do paged ldap reads so AD would only send one 
page which meant not all the entries would be read for larger maps.

>
> When I do a autofs reload maybe 90 % of the time I see all entry's. I am
> having this issue on Redhat 6 and Suse 11. Strange thing is that the
> autofs logging (debug) shows always all the entry's but are not
> reflected in the filesystem structure.

I can't remember now what gets logged for the ldap map reads so how have 
you established the read gets all the entries (and what rel6 version of 
autofs are you using)?

>
> This is my config :
>
> /etc/sysconfig/autofs
> ----
> LDAP_URI="ldap://srvxxx.domain.net/"
> SEARCH_BASE="ou=LinuxAutoMount,ou=Resources,dc=domain,dc=net"
> LDAP_TIMEOUT="100"
> LDAP_NETWORK_TIMEOUT="100"
> MAP_HASH_TABLE_SIZE=2048

OK, so BROWSE_MODE isn't set so it = yes by default and you expect the 
mount point directories within what are probably indirect mounts to be 
created or removed, as the case may be, correct?

But they aren't all being created (or removed)?

>
> /etc/autofs_ldap_auth.conf
> ----
> <autofs_ldap_sasl_conf
>       usetls="no"
>       tlsrequired="no"
>       authrequired="yes"
>       authtype="GSSAPI"
>       clientprinc="nfs/client01.domain.net@DOMAIN.NET"
> />

Don't think this makes any difference since if auth was failing I don't 
think you would get any entries.

>
> /etc/nsswitch.conf
> ----
> automount:    files ldap

This might make a difference, depending on what file maps exist, but we 
would need a debug log and map examples to reproduce the problem.

What about logging a bug against rhel-6 and working on it there.

Ian

  reply	other threads:[~2014-10-17  8:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-15 12:31 Problem with autofs and ldap rsmits-l
2014-10-17  8:51 ` Ian Kent [this message]
2014-10-21 13:27   ` rsmits-l
2014-10-22  2:25     ` Ian Kent
2014-10-22  2:39     ` Ian Kent

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=5440D89C.6040001@themaw.net \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=rsmits-l@tudelft.nl \
    /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.