oozie job fails with very little information

[Supreeth]

Hi Team:

Setup a brand new oozie server and most of the usecases succeed. However
when I add a data check node into the coordinator on the likes of

   <datasets>

    <dataset name="raw-logs" frequency="${coord:minutes(1)}"
initial-instance="${initialInstance}" timezone="UTC">

<uri-template>${nameNode}/${inputBaseDir}/${YEAR}${MONTH}${DAY}${HOUR}{MINUTE}</uri-template>

  </dataset>

    <dataset name="aggregated-logs" frequency="${coord:minutes(1)}"
initial-instance="${initialInstance}" timezone="U\
TC">


<uri-template>/output-data/aggregator/aggregatedLogs/${YEAR}/${MONTH}/${DAY}/${HOUR}{MINUTE}</uri-template>

    </dataset>

  </datasets>

  <input-events>

    <data-in name="input" dataset="raw-logs">

      <instance>2014-06-27T11:19Z</instance>

    </data-in>

  </input-events>

  <output-events>

        <data-out name="output" dataset="aggregated-logs">

          <instance>2014-06-27T11:19Z</instance>

        </data-out>

  </output-events>

The COORD app fails with status set to "FAILED". Not much in the logs on
the Oozie UI or in the oozie.log.dir.

Any help to debug this further, how I can get more logging enabled which
can provide info on why the coord is getting marked as "failed"?

Build info:
Oozie client build version: 4.0.0.2.1.2.1-471

oozie-log4j file:

log4j.logger.openjpa=ALL, openjpa
log4j.logger.oozieops=ALL, oozieops
log4j.logger.oozieinstrumentation=ALL, oozieinstrumentation
log4j.logger.oozieaudit=ALL, oozieaudit
log4j.logger.org.apache.oozie=ALL, oozie
log4j.logger.org.apache.hadoop=ALL, oozie

Thanks,
Supreeth