Project

General

Profile

Actions
Copy link

Bug #2940

closed

(ex PT/ Technique)JobScheduler: The command defined in the directive seems to never be executed during some interval of time

Added by Nicolas PERRON over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
2
Assignee:
Nicolas PERRON
Category:
Techniques
Target version:
2.3.9
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I've try to use jobScheduler Technique in order to execute some commands during the night but it never happens. The parameters used are:

The only report we have with these parameters is:

Oct  4 00:56:43 debian-5-32 rudder[27405]:  R: @@jobScheduler@@log_info@@47f44489-b4d0-499a-8ddd-cf73c3fe286a@@35241818-4a3d-414e-802d-37836072fba7@@11@@Job@@/root/testjobScheduler2.sh@@2012-10-04 00:56:27+02:00##0876521e-3c81-4775-85c7-5dd7f9d5d3da@#The command will be run at a random time after 1:00 on this node (/root/testjobScheduler2.sh)

The Technique is from the latest version (last commit: 356098feb4c8605b46a9ab189dc9c6cf665f2977).

Nevertheless, the commands are executed if we use other intervals of time like: 13h to 14h.

Files

jobSchedulerNotWorking.png (21.2 KB) jobSchedulerNotWorking.png Nicolas PERRON, 2012-10-04 14:34
Actions
Copy link

Also available in: Atom PDF