Hi @Vinicius Higa Murakami, unfortunately it wasn't that easy... the next time, I started my environment, I had these strange errors again. But - after quite some desperate hours of trial and error - I got the point. Whenever I started a brand new image, everything was fine. I didn't have any errors. When I started the shutted down image the next day, it was ruined. It occurs to me, that a solid termination of the HDP processes in ambari and a service ambari-agent stop with a service ambari-server stop would be a nicer approach and that helped. When terminating the process in a correct manner, the restart will happen without any errors. When just shutting down the AWS instance, it breaks. That's it, plain and simple. Well... the good point is: I learned a lot 😉 Thanks for your help! Chris ... View more

Hi @Vinicius Higa Murakami, I was abcent a view days due to some business trip. I just started my AWS instance to check your sticky bit tip but the HDP started without any errors...? I didn't do anything with it in the past days so I have no idea what's going on. Could it be that these errors occur because of network issues during "rush hours" in AWS? I'll have an eye on it at the weekend... Thanks! Chris ... View more

Maybe that helps: No process listening on port 8042 though... ... View more

Hi @Vinicius Higa Murakami, when starting the nodemanager via ambari, I get a process listening on 8042 for one second: [root@resourcemanager ~]# while [ true ]; do sleep 1; netstat -tupln | grep 8042; done tcp 0 0 :::8042 :::* LISTEN 20422/java Also, please find attached two grep-results of the log-file while restarting via ambari. tail -f /var/log/hadoop-yarn/yarn/yarn-yarn-nodemanager-resourcemanager.log | grep -i 'error\|warn\|fatal\|severe' > /tmp/nodemanager1.log Thank you so much for your support! Chris ... View more