Hi, After a long long long way searching the web for answers to help me debug this Yarn not starting, i wondered if all this mess can't be a network configuration problem. The fact is i wasn't even able to find where the right starting logs where for Yarn. The only logs i got was the webui being unavailable. I so reinstalled the whole cluster, buts this time putting more services on slave Vms hoping another component to fail starting and giving me explicit logs. it worked. The explaination : Despite any kind of configuration you use in the VagrantFile, Vagrant will add to etc/hosts a line with the hostname you defined for the machine and the localhost adress, and obviously ,several components of the stack, at a step or another in the setup process, use the first IP feeded in the hosts file neither than the hostname. It explains why everything worked in single node and why their was so many mess in multi-node : some services or log where try-accessed throught 127.0.0.1 adress but where on other machines. The workaround is to provision an inline shell command like this : "sudo sed -i'' '/^127.0.0.1\\t#{hostname}\\t#{name}$/d' /etc/hosts" in the VagrantFile, then install and setup the Ambari server. trying to correct afterwards is like checking by hand every configuration file of the stack. This ticket can be closed.
... View more
