Re: unlink of socket failed and no such object

[Pete Greenup <petegreenup [at] gmail.com>]

ok got it working... thanks. I had to get the right combination of the active directory settings in the nslcd.conf file and now i should be all set.

Appreciate the direction

On Tue, May 19, 2015 at 12:53 PM, Pete Greenup <petegreenup [at] gmail.com> wrote:

>Your nslcd.conf has two binddn options. If you LDAP server requires binding before searching you need to configure binddn and bindpw.

Right, these are set and look to be working as expected

>You also map the uid attribute to cn but your ldapsearch uses the uid attribute so you should probably disable that mapping.

Done

>Also be sure that the filter you configured in nslcd.conf all map to attributes found in the LDAP server.

Will look into this.

>Right before the "user not found" error nslcd should log which search it tried to perform (in debug mode). This should provide information on why the search failed.

Ok, good info. thanks

On Sat, May 16, 2015 at 3:42 AM, Arthur de Jong <arthur [at] arthurdejong.org> wrote:

On Thu, 2015-05-14 at 16:31 -0700, Pete Greenup wrote:
> nslcd: DEBUG: unlink() of /var/run/nslcd/socket failed (ignored): No
> such file or directory

This should only happen on start-up and can be safely ignored.

> nslcd: [3c9869] <authc="xuser"> DEBUG: "xuser": user not found: No
> such object

This means that nslcd is not able to find the user in LDAP. If you can
find the user with ldapsearch, it probably indicates a configuration
issue.

> I have tried un-commenting and commenting a few different fields in
> the active directory section of my nslcd.conf, but am thinking i might
> need to do something more specific?

Your nslcd.conf has two binddn options. If you LDAP server requires
binding before searching you need to configure binddn and bindpw.

You also map the uid attribute to cn but your ldapsearch uses the uid
attribute so you should probably disable that mapping. Also be sure that
the filter you configured in nslcd.conf all map to attributes found in
the LDAP server.

Right before the "user not found" error nslcd should log which search it
tried to perform (in debug mode). This should provide information on why
the search failed.

Kind regards,

--
-- arthur - arthur [at] arthurdejong.org - http://arthurdejong.org/ --

--
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe [at] lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/

-- 
To unsubscribe send an email to
nss-pam-ldapd-users-unsubscribe@lists.arthurdejong.org or see
http://lists.arthurdejong.org/nss-pam-ldapd-users/