You can find application specific logs out in your hadoop cluster. We're looking for the Application Master log first, which will tell us on what nodes your job is attempting to execute on. If you have access to your ResourceManager's UI you can click the application id and view this log. If you have aggregation enabled, you can view container logs by issuing the command
yarn logs -applicationId <your application id>
If not, you need to view logs from wherever your logging directory is configured to, in my system that happens to be /var/log/hadoop-yarn/container/<application id>/ ... etc. And the file we're looking for is called gl_AppMaster.stdout.
This file will tell you where the containers for Dato Distributed attempted to run. Finding the logs from those containers will give us more insight as to why your job isn't running.
You can also use
yarn application -status <your application id>
To get a report of the status of your application according to the YARN Resource Manager. If the application never enters the "running" state, you may have a problem with resource allocation.