@Juan Gonzalez If this answers your query then please mark this HCC thread as answered by clicking on "Accept" link on the correct answer, That way it will help other HCC users to quickly find the answers. ... View more

@Juan Gonzalez Regarding your query: I see that there is low memory,and i will have with run services in ambari. So solutions are put more memory or use azure HDP 2.5 because my friend say me that is more optimized and i will not have problems! >>> You will need atleast 8 GB RAM to run the HDP Sandbox The Stuck Ambari Desktop is due to the memory lack. Azure can be another best option however with 8GB memory your current Sandbox also should run fine. The Note from the Sandbox Minimum requirement section: https://hortonworks.com/tutorial/sandbox-deployment-and-install-guide/section/1/#prerequisites A computer with at least 8 GB of RAM to spare. Note: Make sure to allocate at least 8 GB (8192 MB) of RAM for the sandbox. . ... View more

@Juan Gonzalez May be the "/var/run/hbase/hbase-hbase-master.pid" file does not exist thats why the mentioned kill command failed. You can find some more java processes that you can kill for testing. The once you have enough free memory then you can start those services/components from Ambari UI. # ps -ef | grep java . Using the above command you can find the PIDs and then kill few of them. ... View more

@Juan Gonzalez To free up some resources we can try to kill some of the components and then once we are able to login to Ambari UI then based on the requirement we can start & stop the required services. Like: # free -m # kill -9 `cat /var/run/hive/hive-server.pid` # kill -9 `cat /var/run/hbase/hbase-hbase-master.pid` # kill -9 `cat /var/run/hbase/hbase-hbase-regionserver.pid` Then restart the ambari-server after checking the free memory. # free -m # ambari-server restart . ... View more

@Juan Gonzalez Based on the API output we can see that the amabri server is running fine and responding to the rest calls. So the Dashboard not loading issue might be related to the browser caching or from browser side. So as suggested earlier can you please try using "Incognito Mode" (Private Mode) of browser to avoid any browser caching issue. Also regarding the Alerts , The alerts are mostly normal and usually shows the really situation based on the type of alert. (rarely they are fake/false). When we invoke the "/api/v1/clusters/Sandbox" API then it will show all the alert destinations as a normal behavior. We can look at the individual alert to know why they are being triggered and if there is some attention required. However in Sandbox where too many services are running ... hence due to resource limitation we usually see many alerts and hence in order to suppress alerts we can put the servives in Maintenance mode. Example. Ambari UI --> Mapreduce --> Service Actions --> Turn ON Maintenance Mode. . https://docs.hortonworks.com/HDPDocuments/Ambari-2.2.2.0/bk_Ambari_Users_Guide/content/_setting_maintenance_mode.html ... View more

@Juan Gonzalez I just noticed that your Sandbox version is bit old "sandbox 2.2.4.2" so it might not have the 4200 (Web Terminal functionality). In that case you will have to try killing those processes using terminal: # ssh root@localhost -p 2222 Enter Password: hadoop . ... View more

@Krupal Jagtap Login to Ambari UI and the navigate to Amabri Dashboard left panel Ambari Metrics --> "Service Actions" (Drop down menu) --> Stop Ambari Metrics --> "Service Actions" (Drop down menu) --> Delete Service . ... View more

@Krupal Jagtap We will have to look at the complete "ambari-server.log" to understand what might be the issue. However looks like it might be due to Database Inconsistency. Take a fresh Amabri DB dump (as a backup). Is it possible to just stop the "Ambari Metrics" service itself and then Delete the whole "Ambari Metrics Service" from ambari UI and then reinstall it to quickly attempt to find the fix. (If you do not have much AMS data then deleting this service and installing it might be a better option) ... View more

@Juan Gonzalez This might happen mostly due to memory constraints. I will suggest , stopping / killing some of the components running on the Sandbox (kill -9 $HIVE_SERVER2_PID) or some other service components like HBase and then restart the ambari server again to see if it works. You can access the browser console to access the terminal http://localhost:4200 or use the SSH (ssh -p 2222 root@localhost). Once you are able to access the ambari UI then you can either put those unwanted components in Maintenance Mode or increase the RAM. Also please try using "Incognito Mode" of browser to avoid any browser caching issue. If you notice any WARNING / ERROR in "/var/log/ambari-server/ambari-server.log" then please share. ... View more