Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

LDAP sync error

LDAP sync error

New Contributor

11023-screenshot-from-2017-01-03-170720.png

Syncing all...ERROR: Exiting with exit code 1. REASON: Caught exception running LDAP sync. [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user ]; nested exception is javax.naming.AuthenticationException: [LDAP: error code 49 - INVALID_CREDENTIALS: Bind failed: ERR_229 Cannot authenticate user ]

14 REPLIES 14

Re: LDAP sync error

@Narasimma varman

1. Did the "sync-ldap" command ever worked successfully earlier ?

2. If YES then please make sure the ldap credentials and settings for OU are not alerted after that.

Try to use ldapsearch command using same user credentials to query ldap server to make sure ldap is working fine.

Re: LDAP sync error

New Contributor

NO, it won't work successfully earlier

Re: LDAP sync error

Rising Star
@Narasimma varman

It seems that your bind credentials in ambari.properties are wrong, can you send us the ambari.properties, and perform an ldapsearch with the same bind credentials as mentioned in ambari.properties file against your ldap server

Re: LDAP sync error

New Contributor

11031-ambari-sandbox-16.jpg

11032-ambari-sandbox-17.jpg

11033-ambari-sandbox-18.jpg

11034-ambari-sandbox-19.jpg

11035-ambari-sandbox-20.jpg

I attach my ambari.properties

Highlighted

Re: LDAP sync error

Rising Star

It seems you have attached wrong configs, these are ranger details, for ambari the properties are in file /etc/ambari-server/conf/ambari.properties

Re: LDAP sync error

New Contributor

Sorry by mistake I attach wrong think now I attach correct ambari.properties

Re: LDAP sync error

New Contributor

Now I am getting this issue

Syncing all...ERROR: Exiting with exit code 1. REASON: Caught exception running LDAP sync. 127.0.0.1:636; socket closed; nested exception is javax.naming.ServiceUnavailableException: 127.0.0.1:636; socket closed

Re: LDAP sync error

Rising Star

Is your LDAP server running on 636 port ?

# netstat -ntpl | grep 636

# netstat -ntpl | grep 389

Re: LDAP sync error

New Contributor

Yes, It is working

11030-screenshot-from-2017-01-03-174513.png

Don't have an account?
Coming from Hortonworks? Activate your account here