Hi @Eric Yuan , i see error : Causedby: java.io.IOException:Unexpected HTTP response: code=504!=201, op=CREATE, message=GatewayTimeout please check if you have enabled any Http Proxy / Network proxy at your end? I am suspecting that the WebHDFS requests originated by the Hive View is actually passing through some Http Proxy configured on your cluster. You may need to either make the request bypass the proxy server or make the proxy work. So please check the following: 1. Check the "environment" setting to find out if there is any Http Proxy added? (look for 'proxy') # /var/lib/ambari-agent/ambari-sudo.sh su hdfs -l -s /bin/bash -c 'env' 2. See if you are able to make the WebHDFS call via terminal from ambari server host? And to see the output of the request is being passed via proxy? # curl -ivL -X GET "http://$ACTIVE_NAME_NODE:50070/webhdfs/v1/user/admin?op=GETHOMEDIRECTORY&user.name=admin" 3. You can also refer to the following doc to know how to enable Http Proxy settings inside Ambari Server (and you can also configure ambari JVM property to exclude your cluster nodes requests to NOT be passed via proxy) See: https://docs.hortonworks.com/HDPDocuments/Ambari-2.6.2.0/bk_ambari-administration/content/ch_setting_up_an_internet_proxy_server_for_ambari.html -Dhttp.nonProxyHosts=<pipe|separated|list|of|hosts> 4. Or you can also configure "no_proxy" at the "~/.bash_profile" OR "/etc/profile" level globally to make suere that your internal cluster requests are not passed vias Proxy. no_proxy=".example.com"export no_proxy . Please see if this helps you and please accept answer if it did. ... View more

Hi @Sampath Kumar , From the output of chage -l hdfs i see your password of hdfs local user is expired. can you try to change To resolve this issue, disable the expired password for the HDFS user, using the following command: chage -m 0 -M 99999 -I -1 -E -1 hdfs This command sets the following for the HDFS user: Minimum Password Age to 0 Maximum Password Age to 99999 Password Inactive to -1 Account Expiration Date to -1 You can further explore the command chage in google and set the password policy accordingly. and then try again with ambari. Please see if this helps you. please accept answer if it did. ... View more

Hi @Hieu Nguyen Trung , the exception you have shared seems to be from Apache bug : https://issues.apache.org/jira/browse/AMBARI-18285 Which is your base version from which you are upgrading ? Can you revisit the ambari.properties file in /etc/ambari-server/conf/ambari.properties also compare your ambari.properties with ambari.properties.rpmsave in /etc/ambari-server/conf/ this is my output when i grep for jdbc : [root@asn1 conf]# cat ambari.properties |grep -i jdbc custom.mysql.jdbc.name=mysql-connector-java.jar server.jdbc.connection-pool=internal server.jdbc.database=postgres server.jdbc.database_name=ambari server.jdbc.postgres.schema=ambari server.jdbc.user.name=ambari server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat Please accept this answer if this helped you. ... View more

Hi @Kei Miyauchi, This looks like a javascript bug to me. i have gone ahead and created a apache jira on the same : https://issues.apache.org/jira/browse/AMBARI-24885 the fix for this issue is in javascript and you can find it in the jira. Incase you want to implement the fix in your cluster. Steps 1) go to /usr/lib/ambari-server/web/javascripts 2)take backup of app.js cp app.js app_backup.js_backup 3) edit app.js , go to line 95478 ,edit the line if (App.router.currentState.name !== 'viewDetails') { to if (App.router.currentState.name !== 'viewDetails' && App.router.currentState.name !== 'shortViewDetails') { 4) and do a diff [root@anaikhdp1 javascripts]# diff app.js app_fix.js 95478c95478 < if (App.router.currentState.name !== 'viewDetails') { --- > if (App.router.currentState.name !== 'viewDetails' && App.router.currentState.name !== 'shortViewDetails') { 5) reload the webpage. incase you find any difficulty please copy back the backedup app.js and reload the page to revert back the changes. Please accept this anser if you find this helpfull which will help other users to get the fix. ... View more

Hi @kanna k , I guess you are doing wrong here as per https://supportmatrix.hortonworks.com/ Ambari-2.7 version only supports HDP-3.0 and HDF-3.2 that's the reason you are facing the issue here. Refer to : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-installation/content/determine_product_interop.html as ambari is not fully compatable with HDP version is failing. ... View more

Hi @Amin Meziani , IT seems you are installing in Ubuntu and facing the issue mentioned in here : https://community.hortonworks.com/content/supportkb/48912/how-to-install-the-hortonworks-gpg-key-on-ubuntu.html Can you please See if the solution works and revert. Please accept this answer if this solution worked for you. ... View more

Hi @Cibi Chakaravarthi, Go to Ambari UI>Atlas >Configs (Filter for property atlas.ssl.exclude.cipher.suites) Set as below and restart the service atlas.ssl.exclude.cipher.suites=.*NULL.*, .*RC4.*, .*MD5.*, .*DES.*, .*DSS.* I guess a '.' is missing before *NULL* is your problem. Please login and accept the answer if this helps you ... View more