Hi William,
So, where did you read the docs on the setup? Maybe the docs are
incomplete?
We are using Sun directory Server version 7, the configure on 389ds
copied from Sun Directory Server for the automount part.
Can you correctly do a "ldapsearch" or
"ldapwhoami" with -H
ldap://389ds.example.com?
YES. the ldapsearch can work propertly. Just the
automount part has some issue.
I will double check this today and reply. Thanks!
Sincerely,
--
DaV
On Fri, Aug 23, 2019, at 08:53, William Brown wrote:
>
>
> > On 23 Aug 2019, at 10:39, DaV <snowfrs(a)gmail.com> wrote:
> >
> > Hi all,
> > First of all, I don't know whether if this is a bug and I don't know
where to submit a bug.
>
> Let's do some investigation here first, but then I'd advise the RH
> bugzilla if we determine what the cause is.
>
> >
> > My 389ds info:
> > OS: CentOS Linux release 7.6.1810 (Core)
> > 389ds: 389-ds-base-1.3.8.4-15.el7.x86_64
> >
> > On 389ds server, I have configured like this
> >> # auto.master, service,
example.com
> >> dn: nismapname=auto.master,ou=service,dc=example,dc=com
> >> nisMapName: auto.master
> >> objectClass: nisMap
> >> objectClass: top
> >>
> >> # /home, auto.master, service,
example.com
> >> dn: cn=/home,nismapname=auto.master,ou=service,dc=example,dc=com
> >> nisMapName: home
> >> objectClass: nisObject
> >> objectClass: top
> >> cn: /home
> >> nisMapEntry: ldap
389ds.example.com
> >>
> >> # *, auto.home, service,
example.com
> >> dn: cn=*,nismapname=auto.home,ou=service,dc=example,dc=com
> >> nisMapName: home
> >> nisMapEntry: -fstype=nfs4,defaults,_netdev,acl sun:/home/&
> >> objectClass: nisObject
> >> objectClass: top
> >> cn: *:nismapname=auto.home,ou=service,dc=example,dc=com
> >>
> >
> > On client side
> > When I want to change directory under home (cd /home/username), I can't.
> > So I enable the autofs debug mode, and I see some message like this
> >
> >> Aug 22 15:55:36 centos automount[2424]: parse_server_string: lookup(ldap):
server "ldap://ds.example.com/", base dn
"nismapname=auto.home,ou=service,dc=example,dc=com"
> >
> > The prefix 389 has gone. The client says can't connect LDAP server because
in 389ds server I write ldap
389ds.example.com but I see
ds.example.com on client-side.
> >
> > I don't know whether this is a bug. Just write this to let you know.
Thanks!
>
So, where did you read the docs on the setup? Maybe the docs are
incomplete?
>
> What client tool are you using to read the mount? I seem to recall sssd
> has some stuff for it, or automount directly does. Seeing your
> automount "configs" would help here.
>
Can you correctly do a "ldapsearch" or
"ldapwhoami" with -H
ldap://389ds.example.com?
>
> Anyway, it seems like a url/uri parsing issue, so let's work out what
> part is failing :)
>
> >
> >
> > My solution is:
> > change the 389ds server-side using nisMapEntry: ldap
tc-389ds.example.com.
> >
> >
> >
> > Sincerely,
> > --
> > DaV
> >
> >
> >
> > _______________________________________________
> > 389-users mailing list -- 389-users(a)lists.fedoraproject.org
> > To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> > Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> > List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> > List Archives:
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
>
> —
> Sincerely,
>
> William Brown
>
> Senior Software Engineer, 389 Directory Server
> SUSE Labs
> _______________________________________________
> 389-users mailing list -- 389-users(a)lists.fedoraproject.org
> To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
> Fedora Code of Conduct:
>
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
> List Guidelines:
https://fedoraproject.org/wiki/Mailing_list_guidelines
> List Archives:
>
https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproje...
>