failed scheduling jobs with cron 1 * * * *

Comments

5 comments

  • Konsta Danyliuk

    Hello Anson.

    This cron pattern should work fine. May I ask you to check the Information Tab of the Inspector (View -> Inspector) for this ImportJob and let me know is mentioned under the Scheduled section?

    Here is an example from my lab for the ImporJob scheduled with the crop pattern 1 * * * *.

    0
    Comment actions Permalink
  • Anson Chan

    Hello Konsta - many thanks for your reply.

    please find the picture. As you can see the last processed is 2 hrs, 19 mins ago.

    I am really unsure why the schedule job won't run. Will you please help me?

    Thanks, Anson

    0
    Comment actions Permalink
  • Konsta Danyliuk

    Hello Anson.
    In my lab, I've scheduled an ImportJob and a Workbook using the crop pattern 1 * * * *. Both artifacts are being successfully triggered last 2 hours.

    For further troubleshooting, I would recommend configuring debug logging for job triggering event as described in the KB article Debugging Job Scheduler and Trigger Problems. As soon as you add the mentioned property to conf/log4j-production.properties file and restart Datameer, appropriate messages for every attempt to trigger scheduled job appear in logs/conductor.log file, together with the error, if any.

    I would also recommend to create a few test artifacts and schedule them with different cron patterns, e.g. every 10-15-20 mins, to better understand the scope of the issue, I'm curious whether this affects any scheduled job or only a certain one(s).

    By the way, what Datamer version do you use?

     

     

    0
    Comment actions Permalink
  • Anson Chan

    Hello Konsta,

    please find our version used below. Although I have Admin Access into Datameer but I do not have access to the AWS enviornment.

    I have attempted to try a few scheduled import jobs which all have not been triggered.

    0
    Comment actions Permalink
  • Konsta Danyliuk

    Hello Anson.

    In case none of the scheduled jobs are being triggered, you definitely should enable the suggested debug logging option to understand what is going on. Do you think you could ask your Datameer admins to do this?

    0
    Comment actions Permalink

Please sign in to leave a comment.