@moritz   I see in your "ambari.properties" there are no JDBC settings appeared because looks like you are mixing the custom driver setup arguments along with the JDBC DB setup arguments in a single setup commands. Thats the reason the JDBC settings are not getting persisted. Please try the following sequence of setup. Step-1). Setup the JDBC DB settings.  After this step you should see that your ambari.properties file has the JDBC entries in it.    # ambari-server setup --java-home /usr/lib/jvm/java-1.8.0-openjdk/jre --enable-lzo-under-gpl-license --database=postgres --databasehost=localhost --databaseport=5432 --databasename=ambari --databaseusername=ambari --postgresschema=ambari --databasepassword=ambari -s   Step-2). Now Setup the Custom Postgres JDBC Driver of your own choice using the following command. However, usually ambari ships a Postgres Driver here "/usr/lib/ambari-server/postgresql-*"   # ambari-server setup --jdbc-db=postgres --jdbc-driver=/usr/share/java/postgresql-jdbc.jar   Step-3). Now run the following command to verify the JDBC settings are reflected properly or not? Example:   # grep 'jdbc' /etc/ambari-server/conf/ambari.properties custom.postgres.jdbc.name=postgresql-jdbc.jar server.jdbc.connection-pool=internal server.jdbc.database=postgres server.jdbc.database_name=ambari server.jdbc.driver=org.postgresql.Driver server.jdbc.hostname=localhost server.jdbc.port=5432 server.jdbc.postgres.schema=ambari server.jdbc.rca.driver=org.postgresql.Driver server.jdbc.rca.url=jdbc:postgresql://localhost:5432/ambari server.jdbc.rca.user.name=ambari server.jdbc.rca.user.passwd=/etc/ambari-server/conf/password.dat server.jdbc.url=jdbc:postgresql://localhost:5432/ambari server.jdbc.user.name=ambari server.jdbc.user.passwd=/etc/ambari-server/conf/password.dat     . ... View more

@ranger  As we see "Authentication Failed" hence most possible cause may be the incorrect ranger admin credentials supplied to the curl command.   1. Are you sure that you are able to Login to Ranger UI using Web Browser with the same credentials Username: "rangeradmin" Password: "rangeradmin"?     http://$RANGER_HOSTNAME:6080     If not then please check what is the Username& Password you have entered here     Ambari UI --> Ranger --> Configs --> Advanced --> "Advanced ranger-env" --> "Ranger Admin username" AND "Ranger Admin user's password"     2. Please tail the "xa_portal.log" log and see if you are getting any of the following message when you are attempting to login to Ranger UI using the same credentials? Or while making the API call?     # tail -f /var/log/ranger/admin/xa_portal.log # grep 'Login Unsuccessful' /var/log/ranger/admin/xa_portal.log # grep 'Authentication with' /var/log/ranger/admin/xa_portal.log # grep 'Bad Credentials' /var/log/ranger/admin/xa_portal.log     .     ... View more

@Manoj690  We see the error as  ERROR : FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got exception: org.apache.hadoop.security.AccessControlException Permission denied: user=root, access=EXECUTE, inode="/warehouse/tablespace/managed/hive":hive:hadoop:drwx------ Here we see that 'user=root'  which means you might be running the query as "root" user.  Who does not have permission to write in the mentioned HDFS directory "/warehouse/tablespace/managed/hive" .   So better to run the same query as "hive" user and then check the results. ... View more

@tyadav  Every service provides a "metainfo.xml" file which is used by ambari to determine the <dependencies> between individual service/components. For example in case of HIVE service you can see a "metainfo.xml" file in the following location. /var/lib/ambari-server/resources/common-services/HIVE/0.12.0.2.0/metainfo.xml /var/lib/ambari-server/resources/stacks/HDP/3.0/services/HIVE/metainfo.xml   You can find the <dependencies> tab inside this file which talks about the component dependencies. For example you can see the "HIVE_SERVER" dependencies as following: <component> <name>HIVE_SERVER</name> <displayName>HiveServer2</displayName> <category>MASTER</category> <cardinality>1</cardinality> <versionAdvertised>true</versionAdvertised> <reassignAllowed>true</reassignAllowed> <clientsToUpdateConfigs></clientsToUpdateConfigs> <dependencies> <dependency> <name>ZOOKEEPER/ZOOKEEPER_SERVER</name> <scope>cluster</scope> <auto-deploy> <enabled>true</enabled> <co-locate>HIVE/HIVE_SERVER</co-locate> </auto-deploy> </dependency> <dependency> <name>YARN/YARN_CLIENT</name> <scope>host</scope> <auto-deploy> <enabled>true</enabled> </auto-deploy> </dependency> <dependency> <name>MAPREDUCE2/MAPREDUCE2_CLIENT</name> <scope>host</scope> <auto-deploy> <enabled>true</enabled> </auto-deploy> </dependency> </dependencies> . Similarly you can also find the dependencies using the following kind of Ambari API call: # curl -sk -u admin:admin -H "X-Requested-By: ambari" -X GET http://$AMBARI_HOST:8080/api/v1/stacks/HDP/versions/3.1/services/HIVE | grep -A5 'required_services' "required_services" : [ "ZOOKEEPER", "HDFS", "YARN", "TEZ" ], . . If your question is answered then, Please make sure to mark the answer as the accepted solution. If you find a reply useful, say thanks by clicking on the thumbs up button.   ... View more