Project

General

Profile

Actions
Copy link

Bug #2480

closed

JobScheduler: I try to execute a script with JobScheduler but it never happens

Added by Nicolas PERRON over 12 years ago. Updated almost 10 years ago.

Status:
Rejected
Priority:
1 (highest)
Assignee:
Benoît PECCATTE
Category:
Techniques
Target version:
2.10.11
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

I have a script:

# ls -lh /root/
-rwxrw---- 1 root root  596 18 avril 12:57 myOwnScript.sh

And I want it to be executed between 12a.m and 01a.m, so A directive from JobScheduler has been created. A Rules has been made including the directive but the complience stuck with 0% in an Unknown state.

It seems that the job is never executed and the Technical Logs on the node only reports log_info:

The command will be run at a random time after 0:00 on this node (/root/myOwnScript.sh)

Actions
Copy link
 #1

Updated by Nicolas PERRON over 12 years ago

  • Description updated (diff)
Actions
Copy link
 #2

Updated by Nicolas PERRON over 12 years ago

This bug is confirmed and repeatable.
THe problem is that the Job can't be executed between 12 a.m and 01 a.m but it works between 10 p.m and 11 p.m .
No execution is made and no reports is sent which result in a "Unknown" state.

Actions
Copy link
 #3

Updated by Jonathan CLARKE over 12 years ago

This is because of #2183.

Actions
Copy link
 #4

Updated by Nicolas PERRON over 12 years ago

  • Target version changed from 2.3.7 to 2.3.8

Jonathan CLARKE wrote:

This is because of #2183.

Ok, so I postpone it to 2.3.8 too

Actions
Copy link
 #5

Updated by Jonathan CLARKE over 12 years ago

  • Project changed from Rudder to 24
  • Category deleted (Techniques)
Actions
Copy link
 #6

Updated by Nicolas PERRON over 12 years ago

  • Category set to Policy Templates

This bug concerns Policy templates

Actions
Copy link
 #7

Updated by Jonathan CLARKE over 12 years ago

  • Target version changed from 2.3.8 to 2.3.9
Actions
Copy link
 #8

Updated by Nicolas PERRON over 12 years ago

  • Assignee deleted (Nicolas PERRON)

This bug need the close #2183 but I'm not sure about what to do with it. I'm pretty sure it will not be made for the 2.4.0-beta5 or beta6.

Actions
Copy link
 #9

Updated by Jonathan CLARKE over 12 years ago

It is unclear whether this is indeed related to #2183 - Nicolas explained that he is unsure whether when he wrote "12:00 AM", he means "12:00" or "00:00". In the first case, this would be a duplicate of #2183, but in the second case it would be a different bug.

The first step here is to test whether this can be reproduced using "00:00".

Actions
Copy link
 #10

Updated by Nicolas PERRON about 12 years ago

  • Target version changed from 2.3.9 to 2.3.10
Actions
Copy link
 #11

Updated by Matthieu CERDA almost 12 years ago

  • Target version changed from 2.3.10 to 2.3.11
Actions
Copy link
 #12

Updated by Matthieu CERDA over 11 years ago

  • Target version changed from 2.3.11 to 2.3.12
Actions
Copy link
 #13

Updated by Matthieu CERDA over 11 years ago

  • Target version changed from 2.3.12 to 2.3.13
Actions
Copy link
 #14

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.3.13 to 84
Actions
Copy link
 #15

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 84 to 2.4.7
Actions
Copy link
 #16

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.7 to 2.4.8
Actions
Copy link
 #17

Updated by Nicolas PERRON over 11 years ago

  • Target version changed from 2.4.8 to 2.4.9
Actions
Copy link
 #18

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.9 to 2.4.10
Actions
Copy link
 #19

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.10 to 2.4.11
Actions
Copy link
 #20

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.11 to 2.4.12
Actions
Copy link
 #21

Updated by Nicolas PERRON about 11 years ago

  • Target version changed from 2.4.12 to 2.4.13

It will need to be tested again and more rigorously.

Actions
Copy link
 #22

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.4.13 to 2.6.11

Since version 2.4 is not maintained anymore, retageting this issue to 2.6

Actions
Copy link
 #23

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.11 to 2.6.12
Actions
Copy link
 #24

Updated by Vincent MEMBRÉ almost 11 years ago

  • Target version changed from 2.6.12 to 2.6.13
Actions
Copy link
 #25

Updated by Vincent MEMBRÉ over 10 years ago

  • Target version changed from 2.6.13 to 2.6.14
Actions
Copy link
 #26

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.14 to 2.6.16
Actions
Copy link
 #27

Updated by Jonathan CLARKE over 10 years ago

  • Target version changed from 2.6.16 to 2.6.17
Actions
Copy link
 #28

Updated by Nicolas PERRON over 10 years ago

  • Target version changed from 2.6.17 to 2.6.18
Actions
Copy link
 #29

Updated by Matthieu CERDA about 10 years ago

  • Target version changed from 2.6.18 to 2.6.19
Actions
Copy link
 #30

Updated by Vincent MEMBRÉ about 10 years ago

  • Target version changed from 2.6.19 to 2.6.20
Actions
Copy link
 #31

Updated by François ARMAND almost 10 years ago

  • Subject changed from (ex PT/ Technique)JobScheduler: I try to execute a script with JobScheduler but it never happens to JobScheduler: I try to execute a script with JobScheduler but it never happens
  • Description updated (diff)
  • Category changed from Policy Templates to Techniques
  • Assignee set to Benoît PECCATTE
  • Target version changed from 2.6.20 to 2.10.10

Benoit, could you look at that one ? If real and present in 2.10, the use case for jobscheduler is completly broken.

Actions
Copy link
 #32

Updated by Vincent MEMBRÉ almost 10 years ago

  • Target version changed from 2.10.10 to 2.10.11
Actions
Copy link
 #33

Updated by Benoît PECCATTE almost 10 years ago

  • Status changed from New to 8

The bug is still here in 2.10.

Actions
Copy link
 #34

Updated by Benoît PECCATTE almost 10 years ago

  • Status changed from 8 to Rejected

Can't reproduce on 2.10

Actions
Copy link
 #35

Updated by Benoît PECCATTE almost 10 years ago

  • Project changed from 24 to Rudder
  • Category changed from Techniques to Techniques
Actions
Copy link

Also available in: Atom PDF