Job is queued but not executed

36 views
Skip to first unread message

SebKoe

unread,
May 10, 2019, 8:00:52 AM5/10/19
to chronos-scheduler
Hi everyone,

i am new to chronos and started to test it today.

I use CentOS 7 as OS.

Chronos Version running is 2.5.1-0.1.20171211074431
Mesos Version running is 1.8.0-2.0.1
Zookeeper Version running is 3.4.6-0.1.20141204175332

Installation was pretty simple. I used the rpm repo and only changed the chronos http_port and http_address Parameters to fit my needs.

I started all three processes and i am able to connect to the Chronos WebUI and add a new Job.

The Job added for testing was also pretty simple. Just a "/usr/bin/touch /tmp/test" with the Schdule "R0/2019-05-10T12:40:00/Z/PT24H".

I then did a "force run" to test my Job.

As soon as i do the "force run", the state changes to "queued". The state then does not change and the Job is not executed. When i restart Chronos, the state is "idle" again.

I had a look in the Logfiles i found, but did not notice anything special.

If you need more information, please let me know.

Thanks and best regards
Sebastian


Reply all
Reply to author
Forward
0 new messages