- Subscribe to RSS Feed
- Mark Question as New
- Mark Question as Read
- Float this Question for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Ranger AD usersync : ERROR UserGroupSync [UnixUserSyncThread] Connection refused
- Labels:
-
Apache Ranger
Created ‎07-13-2017 11:45 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi, I am trying to do Ranger AD usersync (HDP version: 2.4.3 and Ambari version: 2.2.2.0) . When I try to do it manually from Ambari UI or pass the configuration through the blueprint, I get following error:
ERROR UserGroupSync [UnixUserSyncThread] - Failed to initialize UserGroup source/sink. Will retry after 3600000 milliseconds. Error details: com.sun.jersey.api.client.ClientHandlerException: java.net.ConnectException: Connection refused (Connection refused)
Not sure, where the problem is. Ping and telnet to the AD server is also successful.
Also, LDAP cert was loaded into a trustStore using following command:
keytool -import -trustcacerts -alias myldap1 -file mycertfile.pem -keystore /etc/pki/java/cacerts
Any solution please?
Attaching usersync.log file.usersync.txt
Created ‎07-14-2017 07:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From the posted usersync logs, it looks like the communication between ranger admin and ranger usersync is failing. Do you have https enabled for ranger admin? If so, please add the ranger admin cert to usersync trust store.
Usersync contacts ranger admin (database) to update the users and groups that are sync'd from AD.
Created ‎07-14-2017 06:34 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
can you please post the configuration that you gave in ranger usersync config ?
did you specify ldap/ldaps protocol and correct port while configuring usersync
Created ‎07-14-2017 07:13 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@Deepak Sharma Thanks for your reply. Following are my usersync configs:
Sync Source: LDAP/AD
LDAP/AD URL: ldaps://<server>:636
Authentication method: ACTIVE_DIRECTORY
Username Attribute: cn
User Object Class: user
User Search Filter: cn=*
User Search Scope: sub
User Group Name Attribute: memberof
Group Member Attribute: member
Group Name Attribute: cn
Group Object Class: group
Group Search Filter: cn=*
Also, these configs worked with a different Ranger that I had configured before wit the same LDAP cert file. But now I don't understand what the issue is.
Created ‎07-14-2017 07:33 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi @Pooja Kamle
Can you check and post the permissions on these two files:
/usr/hdp/current/ranger-usersync/conf/ugsync.jceks /usr/hdp/current/ranger-usersync/conf/.ugsync.jceks.crc
Also check the permissions of these two files on the other ranger that is working and verify if they are the same.
Created ‎07-14-2017 07:36 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
From the posted usersync logs, it looks like the communication between ranger admin and ranger usersync is failing. Do you have https enabled for ranger admin? If so, please add the ranger admin cert to usersync trust store.
Usersync contacts ranger admin (database) to update the users and groups that are sync'd from AD.
Created ‎07-17-2017 02:09 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I found the issue. My Ranger admin and ranger database reside on different nodes. I was giving the database host instead of Ranger admin host in "policymgr_external_url" property. Correcting it solved the issue. Thanks for your reply.
