@uri ben-ari You are seeing the values containing the "%HOSTGROUP::host_group_4" instead of actual hostname, This is because you might have created the cluster using blueprint. Inside the blueprint these placeholders are usually used. . - Please check which tag version config are you checking? Is it INITIAL , TOPOLOGY_RESOLVED or any specific version like "version1503221811491297915" ? http://localhost:8080/api/v1/clusters/Sandbox/configurations?type=webhcat-site&tag=INITIAL http://localhost:8080/api/v1/clusters/Sandbox/configurations?type=webhcat-site&tag=TOPOLOGY_RESOLVED http://localhost:8080/api/v1/clusters/Sandbox/configurations?type=webhcat-site&tag=version1503221811491297915 - We can set any specific property value of any config type using "config.sh set" command. Syntax: /var/lib/ambari-server/resources/scripts/configs.sh set $AMBARI_HOST $CLUSTER_NAME webhcat-site $KEY $VALUE Example: If we want to change the "templeton.exec.timeout" property value then we can use "set" command as following: /var/lib/ambari-server/resources/scripts/configs.sh set localhost Sandbox webhcat-site "templeton.exec.timeout" "60001" . Reference: https://cwiki.apache.org/confluence/display/AMBARI/Modify+configurations ... View more

@uri ben-ari To list all the service status # curl -i --user admin:admin -i -H 'X-Requested-By: ambari' -X GET http://localhost:8080/api/v1/clusters/Sandbox/services?fields=ServiceInfo/state | grep -A 1 'service_name' . If you want to see only the services that are stopped (means in INSTALLED state) then you can try the following command: # curl -i --user admin:admin -i -H 'X-Requested-By: ambari' -X GET http://localhost:8080/api/v1/clusters/Sandbox/services?fields=ServiceInfo/state | grep -B 1 'INSTALLED' . Example Output: # curl -i --user admin:admin -i -H 'X-Requested-By: ambari' -X GET http://localhost:8080/api/v1/clusters/Sandbox/services?fields=ServiceInfo/state | grep -B 1 'INSTALLED' "service_name" : "AMBARI_INFRA", "state" : "INSTALLED" -- "service_name" : "AMBARI_METRICS", "state" : "INSTALLED" -- "service_name" : "ATLAS", "state" : "INSTALLED" -- "service_name" : "FALCON", "state" : "INSTALLED" -- "service_name" : "HBASE", "state" : "INSTALLED" -- "service_name" : "HDFS", "state" : "INSTALLED" -- "service_name" : "KAFKA", "state" : "INSTALLED" -- "service_name" : "KNOX", "state" : "INSTALLED" -- "service_name" : "LOGSEARCH", "state" : "INSTALLED" -- "service_name" : "PIG", "state" : "INSTALLED" -- "service_name" : "SLIDER", "state" : "INSTALLED" -- "service_name" : "SMARTSENSE", "state" : "INSTALLED" -- "service_name" : "SQOOP", "state" : "INSTALLED" -- "service_name" : "STORM", "state" : "INSTALLED" -- "service_name" : "TEZ", "state" : "INSTALLED" -- "service_name" : "ZOOKEEPER", "state" : "INSTALLED" . Here please replace the following: 1. "localhost" : with the Ambari FQDN 2. 8080 : with ambari port. 3. Sandbox : With cluster Name. . Reference: https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=41812517 ... View more

@Jacqualin jasmin As we see that your passwords are encrypted, Because you mght have the "security.passwords.encryption.enabled" property set to true inside your ambari.properties. # grep 'passwd' /etc/ambari-server/conf/ambari.properties server.jdbc.rca.user.passwd=${alias=ambari.db.password} server.jdbc.user.passwd=${alias=ambari.db.password} Assuming you remember your old ambari db pasword (by default it shoudl be "bigdata"), And you want to change the DB password to something new like "bigdata_new" # mysql -u ambari -p Enter password: bigdata mysql> use ambari; mysql> SET PASSWORD FOR 'ambari'@'localhost' = PASSWORD('bigdata_new'); mysql> SET PASSWORD FOR 'ambari'@'%' = PASSWORD('bigdata_new'); mysql> SET PASSWORD FOR 'ambari'@'standaloneambari1.example.com' = PASSWORD('bigdata_new'); mysql> FLUSH PRIVILEGES; REMEMBER: in the following statement you will need to enter your ambari DB hostname while resetting the DB password. Here standalone1.example.com is the FQDN (hostname -f) where my MySQL DB was running. mysql> SET PASSWORD FOR 'ambari'@'standaloneambari1.example.com' = PASSWORD('bigdata_new'); . Steps from ambari side: First of all please take a backup of ambari properties file # cp -f /etc/ambari-server/conf/ambari.properties /etc/ambari-server/conf/ambari.properties.ORIGINAL . Once the password is changed from the DB side then edit the "/etc/ambari-server/conf/ambari.properties" file and change the value of "server.jdbc.rca.user.passwd" and "server.jdbc.user.passwd" property as following: # grep 'passwd' /etc/ambari-server/conf/ambari.properties server.jdbc.rca.user.passwd=/etc/ambari-server/conf/password.dat server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat Create a file with name "/etc/ambari-server/conf/password.dat" and enter the new Ambari Database password there. Like: # echo "bigdata_new" > /etc/ambari-server/conf/password.dat # cat /etc/ambari-server/conf/password.dat bigdata_new Restart ambari server to see if it is starting fine with the newly retested ambari db password or not? # ambari-server restart . If everything is OK so far then do the following: If ambari server starts fine then we can now proceed with "Encrypting the password" again using "ambari-server setup-security" option [2] Encrypt passwords stored in ambari.properties file. # ambari-server setup-security Using python /usr/bin/python Security setup options... =========================================================================== Choose one of the following options: [1] Enable HTTPS for Ambari server. [2] Encrypt passwords stored in ambari.properties file. [3] Setup Ambari kerberos JAAS configuration. [4] Setup truststore. [5] Import certificate to truststore. =========================================================================== Enter choice, (1-5): 2 Password encryption is enabled. Do you want to reset Master Key? [y/n] (n): n Adjusting ambari-server permissions and ownership... Ambari Server 'setup-security' completed successfully. Once this is done we should see that the password is again encrypted. # grep 'passwd' /etc/ambari-server/conf/ambari.properties server.jdbc.rca.user.passwd=${alias=ambari.db.password} server.jdbc.user.passwd=${alias=ambari.db.password} . Now restart ambari server # ambari-server restart . ... View more

@Winnie Philip It looks like more of a Web Server issue where you installed the local repository. Can you please check if you are able to get the repomd.xml file using wget/curl from abari server host? # wget http://vlmazgrpmaster.fisdev.local/hdp/HDP/centos7/repodata/repomd.xml OR # curl http://vlmazgrpmaster.fisdev.local/hdp/HDP/centos7/repodata/repomd.xml . If above does not work and gives same 403 response. Then you will need to check your Proxy configuration Or Proxy username / password. Please check if there is any proxy server configured which requires proxy credentials? If yes then add the credentials something like following inside your "/etc/profile" OR inside "~/.bash_profile" file of all hosts with the correct proxy username / password and port. export http_proxy=http://USERNAME:PASSWORD@proxy.com:80 . Reference: https://www.cyberciti.biz/faq/linux-unix-set-proxy-environment-variable/ ... View more