Member since
11-14-2017
5
Posts
1
Kudos Received
1
Solution
My Accepted Solutions
Title | Views | Posted |
---|---|---|
763 | 12-11-2017 10:24 PM |
04-14-2020
08:58 PM
Hi , The files you mentioned are not available on the node on which the atlas has been installed. Can you please suggest.
... View more
12-11-2017
10:24 PM
In fact, this is the combined effect of two issues: <1> The atlas.war file was not extracted properly during the Atlas installation. So, manually do so, as detailed here: https://community.hortonworks.com/questions/104751/index.html <2> The bug AMBARI-18368 caused a number of Atlas configuration files to be absent from their intended locations. The instructions to address this issue is here: https://issues.apache.org/jira/browse/AMBARI-18368 Now, Atlas is up, finally.
... View more
11-15-2017
06:41 PM
2 Kudos
@William Lu - yes, you would need to delete Atlas service and install it back after upgrade to HDP-2.6.0 Atlas was in Tech Preview mode in earlier versions of HDP like v2.3 and v2.4, so once you install new Atlas post upgrade - it will be a full blown GA'ed version that you will get. More about Atlas here Hope this helps! ------ Vivek
... View more
11-14-2017
06:08 AM
A few days ago, I happened to run into this issue myself. The root cause is, when installing Ranger, in the "External URL" property, the administrator entered "http://hostname.example.com:6080/", instead of the expected "http://hostname.example.com:6080" (WITHOUT the trailing slash character). Even though the Ranger installation would go through, Ranger's Usersync would log errors in /var/log/ranger/usersync/usersync.log due to this extraneous character. Also, any attempt to enable any of Ranger's plugins would fail, with the error message "Ambari admin username and password are blank", because Ranger is indeed missing many users, including the important one amb_ranger_admin. To fix this, just edit this property and remove any character after port 6080, and everything will start working.
... View more