Hi, I discussed this with one of the developers. Here are 4 things that typically cause issues:
1) not enough RAM/CPU for the CDH Quickstart (we've already discussed this - it may be the actual problem here)
2) Hive crashed while the Quickstart was coming up (Clark had you explore this one - it could be related to 1)
3) Diskspace on the Quickstart is full (Since it is a new environment I doubt this one is it)
4) SASWorkspace shared directory is not setup/configured properly (I would double-check this)
The developer pointed me to a description of how to collect logs from the Quickstart configuration. Here are the instructions.
You can collect logging information from the CDH Quickstart (it will work with Hortonworks, too). Here's how:
Go to your SASvAppLedger: <ipaddress>/SASvAppLedger
Click on "Jobs"
Click on "Collect vApp Logs" button
Go to <ipaddress>/SASvAppLedger/resources
Find "logarchive"
There should be a "...tar.gz" filename and it is a link.
Click this filename
on the page that comes up, click "link"
This brings up a dialog box which allows you to save the log zip file
Take a look at the resulting files. You may be able to see what the problem is. If you find the problem please post the resolution here. Not knowing what the problem is has Clark and me flustered;)
... View more