All the basic Hadoop services should be running when you start the VM. Port 8020 is for the hadoop-hdfs-namenode service, so my guess is that service has failed and just needs to be restarted.   You can check the status of a service with service <service-name> status and you can restart a service with service <service-name> restart So 'service hadoop-hdfs-namenode restart' may be all you need. Also check the hadoop-hdfs-datanode service as it may also need to be restarted.   The services should have been running, so if they're not it means something went wrong. If you're curious or if you continue to have a problem, have a look at the NameNode logs in /var/log/hadoop-hdfs for anything that looks like a fatal error and post it back here.   ... View more

The original error has nothing to do with connecting to Hue. It was an error interactions between Impala and the other daemons it needs to complete the query. Just use the link in the email or on the guidance page to connect to Hue. The public IP should work just fine. If it doesn't, you are experiencing a separate issue and would need to provide more information.     ... View more

Thanks for letting us know - glad you got it working! Is there are an article or blog post with more background on the bug you chould share? ... View more

I've had another VMWare Fusion user confirm that the latest (5.4.0-0) release works well for them, and they actually informed me that those lines we recently added to the .vmx file have been in use for a long time in Cloudera's courses without incident, so I don't think it's worth messing with those settings after all.   My only other suggestion would be to see if there is any kind of error message you can get from Fusion about why the VM is failing to start. It would see from the following article that you can enable some diagnostic information collection - perhaps the resulting files will contain a more useful error message?   http://kb.vmware.com/selfservice/search.do?cmd=displayKC&docType=kc&docTypeID=DT_KB_1_1&externalId=1003894 ... View more

I'm going to look into this, but while I do, here's something you can try if you'd like. These lines were added to the .vmx configuration file recently, and that's the only recent change that I can think of that might affect Fusion specifically. You could try removing them from the file and tryin again. (They're only added as a convenience to hide some annoying reminders and prompts).   tools.remindinstall="FALSE" tools.upgrade.policy="manual" Let me know if that does or doesn't work for you if you can try it out, otherwise I'll post back as soon as I can with more information. ... View more