Member since
09-01-2016
25
Posts
2
Kudos Received
0
Solutions
08-27-2018
03:35 AM
Even if I made "yum clean", there wasn't slider_3_0_1_1_5 package. I still don't understand wahy and from where this package should come. Downloaded and searched in rpm packages (not in hdf 3.0.1 and earlier and later), this slider_* doesn't exists.
... View more
05-04-2018
03:26 PM
1 Kudo
Hi, Unfortunately there were some changes on Azure regarding how the domain names are set through dhcp packets and sometimes the instances do not get the right domain in time then CB falls back a creates the example.com domain. If you are using our standard Azure images, then you'll get an update early next week which addresses this issue. If you have a custom image then I'm afraid you have to recreate it with the latest changes. Also the image update itself wont' fix the problem so you'll have to update to a newer version of CB (2.4.2 is not released yet, but will be soon).
... View more
07-06-2017
05:39 PM
Yeah. added into "Custom webhcat-site" under hive conf in ambari webhcat.proxyuser.HTTP.groups=* webhcat.proxyuser.HTTP.hosts=*
... View more
01-04-2017
08:09 AM
I found that there was problem in repo_version table, version column value should be "2.5.0.0-1245". I had only "2.5.0.0" Beacuse of that all services failed start or restart, with this error: ambari-python-wrap /usr/bin/conf-select set-conf-dir --package hadoop --stack-version 2.5.0.0 --conf-version 0' returned 1. 2.5.0.0 Incorrect stack version I still don't know how this situation happend. I updated version column to "2.5.0.0-1245" in database repo_version table
... View more
05-12-2019
05:54 PM
1 Kudo
This issue is usually seen when user wan't removed properly from Ranger db and some information is still available in user tables. For example in above situation it might be possible that 'user1' is not available in x_user table but its still part of other user tables such as x_portal_user, x_portal_user_role, x_user_module_perm, x_auth_sess etc. Perform below steps to resolve this issue. Verify whether problematic user is available in other tables MariaDB [ranger]> select * from x_user where user_name = 'user1';
MariaDB [ranger]> select id from x_portal_user where login_id = 'user1';
+----+
| id |
+----+
| 44 |
+----+
MariaDB [ranger]> delete from x_portal_user_role where id = 44;
MariaDB [ranger]> delete from x_user_module_perm where user_id = 44;
MariaDB [ranger]> delete from x_auth_sess where user_id = 44;
MariaDB [ranger]> delete from x_portal_user where id = 44; To get all such user's MariaDB [ranger]> select * from x_portal_user_role where id not in (select id from x_user);
MariaDB [ranger]> select * from x_user_module_perm where user_id not in (select id from x_user);
MariaDB [ranger]> select * from x_auth_sess where user_id not in (select id from x_user);
MariaDB [ranger]> select * from x_portal_user where id not in (select id from x_user); Remove users which are not part of x_user table but available in other tables MariaDB [ranger]> delete from x_portal_user_role where id not in (select id from x_user);
MariaDB [ranger]> delete from x_user_module_perm where user_id not in (select id from x_user);
MariaDB [ranger]> delete from x_auth_sess where user_id not in (select id from x_user);
MariaDB [ranger]> delete from x_portal_user where id not in (select id from x_user); Restart usersync process
... View more