@Kibrom Gebrehiwot Re-install should be the last resort because these are real conditions you will meet so start to diagnose and get the sandbox up and running would be a great feat ! How is you network configuration for the Sandbox? Do backup your /etc/hosts and create a new hosts with the below entry 127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4 ::1 localhost localhost.localdomain localhost6 localhost6.localdomain6 10.0.225.60 Sandbox.hortonworks.com Sandbox Set your network to DHCP and restart the sandbox ... View more

Did you follow these steps during your setup Postgres for Ambari steps ... View more

@Kibrom Gebrehiwot These are some of the steps you should try before reinstalling your server! Disable firewall / iptables on the host Run all the below command like root Execute the below command on the server to disable the firewall, type the following command as the root user to disable firewall for IPv6: [root@hiroshima01 ~]# service ip6tables stop [root@hiroshima01 ~]# chkconfig ip6tables off [root@hiroshima01 ~]# service iptables status IPv4 [root@hiroshima01 etc] # service iptables save [root@hiroshima01 etc] # service iptables stop [root@hiroshima01 etc] # chkconfig iptables off Disable Transparent Huge Pages (THP) Disable it on the host otherwise the Ambari install will fail [root@hiroshima01 ~]# echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled [root@hiroshima01 ~]# echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag To disable or make these changes persistent across reboots I add this to the bottom of my vi /etc/rc.local #disable THP at boot time if test -f /sys/kernel/mm/redhat_transparent_hugepage/enabled; then echo never > /sys/kernel/mm/redhat_transparent_hugepage/enabled fi if test -f /sys/kernel/mm/redhat_transparent_hugepage/defrag; then echo never > /sys/kernel/mm/redhat_transparent_hugepage/defrag fi To validate THP is disabled, I run the below three commands, or any variant you choose from here . [root@hiroshima01 ~]# cat /sys/kernel/mm/redhat_transparent_hugepage/defrag #output should be always madvise [never] [root@hiroshima01 ~]# cat /sys/kernel/mm/redhat_transparent_hugepage/enabled # output should be always madvise [never] Disable SELinux SELinux must be disabled for Ambari to function. To temporarily disable SELinux, run the following command on each host in your cluster: [root@hiroshima01 ~]# setenforce 0 Permanently disabling SELinux so that on system reboot it does not restart edit the SELinux config and set SELINUX to disabled. on each host: root@hiroshima01 ]# vi /etc/selinux/config Add the below lines # This file controls the state of SELinux on the system. # SELINUX= can take one of these three values: # enforcing - SELinux security policy is enforced. # permissive - SELinux prints warnings instead of enforcing. # disabled - SELinux is fully disabled. SELINUX=disabled # SELINUXTYPE= type of policy in use. Possible values are: # targeted - Only targeted network daemons are protected. # strict - Full SELinux protection. SELINUXTYPE=targeted Configure the NTPD services You must setup the NTPD server on CentOS to successfully implement Ambari follow the below steps to install and start the NTPD server. As the root user. To install ntpdate [root@hiroshima01 ~]# yum install ntp ntpdate Turn on the service: [root@hiroshima01 ~]# chkconfig ntpd on Synchronize the system clock with 0.pool.ntp.org server [root@hiroshima01 bin]# ntpdate pool.ntp.org 2 Jan 21:42:49 ntpdate[5101]: 31.3.135.236 rate limit response from server. 2 Jan 21:43:56 ntpdate[5101]: step time server 212.51.144.44 offset 67.520940 sec Check the NTPD services configure it start at system boot [root@hiroshima01 bin]# chkconfig --list ntpd ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off Start the NTP server. The following will continuously adjust system time from upstream NTP server. No need to run ntpdate: [root@hiroshima01 ~]# /etc/init.d/ntpd start or [root@hiroshima01 ~]# service ntpd start ... View more

Seems you have a DB connectivity problem ,can you copy and paste a complete output of the Ambari failed to start log ? The connection was closed when Java tried to read from it. This can be caused by: The PostgreSQL server being restarted The PostgreSQL backend you were connected to being terminated The PostgreSQL backend you were connected to crashing Dodgy network connection Badly behaved stateful firewalls Idle connections timing out of the NAT connection tables of NAT firewall/routers ... and probably more. Check the PostgreSQL server logs to see if there's anything informative there; also consider doing some network tracing with a tool like Wireshark. ... View more

OOoops GRANT SELECT ON TABLE logs TO USER bigotes WITH GRANT OPTION; ... View more

This should solve the "Permission denied:Principal[name=hive, type=USER] does not have following privileges for operation GRANT_PRIVILEGE [[SELECT with grant, INSERT with grant, UPDATE with grant, DELETE with grant] on Object[type=TABLE_OR_VIEW, name=default.logs]" ... View more

@Roberto Sancho check out my syntax GRANT SELECT ON TABLE logs TO bigotes WITH GRANT OPTION; ... View more

@Roberto Sancho Predag's response grants all privileges which is NOT what is advisable I would think limiting the grant OPTION for only select is a more secure approach ... View more

I think you need to run the below statement for the user bigotes this will allow him to grant the privileges to others. > su - hive > hive hive > GRANT SELECT ON TABLE logs TO bigotes WITH GRANT OPTION; ... View more

@Kibrom Gebrehiwot Grab Artem Ervits answer ... View more