Question #3370: Job scheduler - Rudder - Issue Tracker

Custom queries

Bugs triage
CS - by Assignee
CS - by priority
CS - to review
My TR
Need technical review
Open bugs (all)
Open bugs (UI - UX)
Open UX defects (all)
Opened by users

Actions

Copy link

Question #3370

closed

Job scheduler

Added by Dennis Cabooter over 12 years ago. Updated about 10 years ago.

Status:

Resolved

Priority:

N/A

Assignee:

Category:

Techniques

Target version:

Regression:

Description

The Job Scheduler technique doesn't seem to have the possibility to run a job every five minutes. Is it possible, and if so, what is the best practice to do this?

Kind regards

History
Notes
Property changes

Actions

Copy link

Updated by Nicolas CHARLES over 12 years ago

Hi Dennis,

The Job Scheduler technique exists to execute a command only once a day. There are currently no way to execute a command every five minutes, but maybe the technique in developpement here http://www.rudder-project.org/redmine/issues/3214 would help you.

Actions

Copy link

Updated by Nicolas CHARLES over 12 years ago

What kind of job would you like to run ? Would you need as well them to be run in a specific time interval ?

Actions

Copy link

Updated by Dennis Cabooter over 12 years ago

We execute scripts every five minutes to feed our monitoring system. I could solve it by deploying /etc/crontab as a file, but it would be nice to schedule this within Rudder.

Actions

Copy link

Updated by Nicolas CHARLES over 12 years ago

Assignee set to Jonathan CLARKE

Ho, so I think we'd need a specific technique for that. What do you think Jon ?

Actions

Copy link

Updated by Nicolas CHARLES over 12 years ago

Project changed from Rudder to 24

Actions

Copy link

Updated by Nicolas PERRON over 12 years ago

Nicolas CHARLES wrote:

Ho, so I think we'd need a specific technique for that. What do you think Jon ?

There is already a Technique to manage crontab: Technique Cron daemon configuration.

Actions

Copy link

Updated by Jonathan CLARKE over 12 years ago

Category set to Techniques
Status changed from New to Discussion
Assignee changed from Jonathan CLARKE to Dennis Cabooter

As I understand it, this would be a typical use case for #3214: run a command on every CFEngine run.

Alternatively, as Nicolas Perron suggested above, you could use the crontab Technique to add a crontab for this on the machines.

Dennis, what do you reckon about these two approaches?

Actions

Copy link

Updated by Dennis Cabooter over 12 years ago

Sorry, I wasn't aware of the crontab technique. Maybe it's not in the right place? Also, why is there a job scheduler and a crontab technique, while they could be merged?

Actions

Copy link

Updated by Nicolas CHARLES about 12 years ago

Dennis Cabooter wrote:

Sorry, I wasn't aware of the crontab technique. Maybe it's not in the right place? Also, why is there a job scheduler and a crontab technique, while they could be merged?

There is a big difference between both approach :

the crontab technique edits the crontab, and the cron is responsible for running the command; so Rudder doesn't know anything about it
the jobScheduler technique runs the command, and can extract return code from it, to have reports on the execution of the command.

So they don't have the same purpose...
I guess #3214 is the one you'll need

Actions

Copy link

#10