All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Kent <raven@themaw.net>
To: Sohnaeo <trysomefun@gmail.com>
Cc: autofs@vger.kernel.org
Subject: Re: Autmount issue
Date: Wed, 27 May 2015 10:07:44 +0800	[thread overview]
Message-ID: <1432692464.2736.12.camel@pluto.fritz.box> (raw)
In-Reply-To: <CABJoi6zbw4wVni-kknMD=tVpFoqD32jc2PbbEP+CW2RU3zJ9tQ@mail.gmail.com>

On Tue, 2015-05-26 at 16:31 +1000, Sohnaeo wrote:
> Hello Ian,
> 
> Thank you very much for looking into this. Solaris clients didn't have
> any issue with the existing master map. In my environment, I do have
> 99% Solaris clients and I don't want to change master map for few
> Linux clients. below is the auto_master map on Sun Directory Server
> 
> dn: automountkey=ahmedf,automountMapName=auto_master,dc=drivess,dc=rtaa
> automountinformation: nfs-cluster:/san/users/cmes/ahmedf
> automountkey: ahmedf
> objectclass: top
> objectclass: automount

I don't see how that could work, it's not a master map entry, it's a map
entry.

The problem with this entry is it doesn't provide the information about
what indirect mount this key belongs to?

You'll need to give me more info about what's in ldap and what the
mounts look like after automount is started on Solaris.

Start autofs on an idle system, do nothing else, and post the contents
of /etc/mnttab (assuming that hasn't changed over the years since I
worked on Solaris systems). If there are obvious things you don't want
people to see in it then delete those lines but don't delete autofs
related lines.

If you want you could log a bug at bugzilla.redhat.com and have it made
private to so the information isn't available to people not included on
the cc list or allowed groups.

> 
> 
> I am clueless.
> 
> On Thu, May 21, 2015 at 4:41 PM, Ian Kent <raven@themaw.net> wrote:
> > On Thu, 2015-05-21 at 12:42 +1000, Sohnaeo wrote:
> >> Hello Guys,
> >>
> >> I am having an issue with the autofs/automount on Cent OS 7, below is the detail
> >>
> >> LDAP Server
> >>
> >>
> >> Solaris 10
> >> Sun Directory Server 6.2
> >>
> >>
> >> LDAP Client
> >>
> >>
> >> CentOS 7
> >>
> >> OpenLdap
> >>
> >>
> >> I issued the below command to enable LDAP authetication. LDAP users
> >> can successfully authenticated now on CentOs
> >>
> >>  authconfig --enableldap --enableldapauth --ldapserver=x.x.x.x
> >> --ldapbasedn=dc=drivess,dc=rtta --disablemkhomedir --update
> >>
> >> But somehow users home directories can't be mounted through autofs.
> >> Below is my autofs.conf file
> >>
> >>  autofs
> >> master_map_name = ldap://xxxxx/automountMapName=auto_master,dc=drivess,dc=rtaa
> >> mount_nfs_default_protocol = 3
> >> logging = debug
> >> ldap_uri = "ldap://x.x.x.x"
> >> search_base = "automountMapName=auto_master,dc=drivess,dc=rtaa"
> >> map_object_class = automountMap
> >> entry_object_class = automount
> >> map_attribute = automountMapName
> >> entry_attribute = automountKey
> >> value_attribute= automountInformation
> >> auth_conf_file = /etc/autofs_ldap_auth.conf
> >> map_type = ldap
> >>
> >> When I run the below command , it throws an error
> >>
> >> automount -m
> >> get_query_dn: lookup(ldap): found query dn
> >> automountMapName=auto_master,dc=drivess,dc=rtaa
> >> lookup_read_master: lookup(ldap): searching for
> >> "(objectclass=automount)" under
> >> "automountMapName=auto_master,dc=drivess,dc=rtaa"
> >> lookup_read_master: lookup(ldap): examining entries
> >> syntax error in map near  ahmedf nfs-cluster:
> >>
> >> Below is ldapsearch command result
> >>   ldapsearch -x -b 'automountMapName=auto_master,dc=drivess,dc=rtaa'
> >> "(objectClass=automountMap)"
> >>
> >> dn: automountMapName=auto_master,dc=drivess,dc=rtaa
> >> automountMapName: auto_master
> >> objectClass: top
> >> objectClass: automountMap
> >>
> >>  ldapsearch -x -b
> >> 'automountkey=ahmedf,automountMapName=auto_master,dc=drivess,dc=rtaa
> >> dn: automountkey=ahmedf,automountMapName=auto_master,dc=drivess,dc=rtaa
> >> automountInformation: nfs-cluster:/san/users/cmes/ahmedf
> >> automountKey: ahmedf
> >> objectClass: automount
> >> objectClass: top
> >>
> >> In short, automountInformation is nfs-cluster:/san/users/cmes/ahmedf
> >> but somehow autmount is complaining "syntax error in map near [ ahmedf
> >> nfs-cluster: ]"
> >
> > That's telling you that your master map is not right.
> >
> >>
> >>
> >> Any ideas?
> >
> > Have a look at the example in /usr/share/doc/autofs:
> > ldap-automount-rfc2307-bis-auto.master
> > ldap-automount-rfc2307-bis-auto.indirect
> > ldap-automount-rfc2307-bis-auto.direct
> >
> > For the indirect mount case above you need master map ldap entries that
> > contain an entry that specifies the indirect mount mount point and the
> > map where the entries for that mount point are stored.
> >
> > Ian
> >
> >
> >



  reply	other threads:[~2015-05-27  2:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21  2:42 Autmount issue Sohnaeo
2015-05-21  6:41 ` Ian Kent
2015-05-26  6:31   ` Sohnaeo
2015-05-27  2:07     ` Ian Kent [this message]
2015-05-27  3:55       ` Ian Kent
2015-05-27  7:38         ` Sohnaeo
2015-05-27 11:10           ` Ian Kent
2015-05-28  0:00             ` Sohnaeo
2015-05-28  1:46               ` Ian Kent
2015-05-28  2:19                 ` Ian Kent
2015-05-28  2:39                   ` Ian Kent
2015-05-28  3:28                     ` Sohnaeo

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=1432692464.2736.12.camel@pluto.fritz.box \
    --to=raven@themaw.net \
    --cc=autofs@vger.kernel.org \
    --cc=trysomefun@gmail.com \
    /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.