[Bacula-bugs] [bacula 0000997]: The scheduler doesn't seem to handle DST transitions

[<bac...@li...>]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.bacula.org/view.php?id=997 
====================================================================== 
Reported By:                terom
Assigned To:                
====================================================================== 
Project:                    bacula
Issue ID:                   997
Category:                   scheduling
Reproducibility:            have not tried
Severity:                   major
Priority:                   normal
Status:                     feedback
====================================================================== 
Date Submitted:             10-28-2007 09:18 EDT
Last Modified:              10-31-2007 12:35 EDT
====================================================================== 
Summary:                    The scheduler doesn't seem to handle DST transitions
Description: 
We have our backups scheduled to run at 03:00 every day, which happens to
be our system's daylight saving time transition time. The system's
localtime goes 02:59, 03:00, 03:59, 03:00, 03:59, 04:00, 05:00, and this
seems to cause bacula to run some jobs three times, and another job doesn't
get run at all.

====================================================================== 

---------------------------------------------------------------------- 
 terom - 10-28-07 10:43  
---------------------------------------------------------------------- 
The Mail job not running was caused by a bug in my configuration
(NightlyBackup3 wouldn't run at all on the 4th sunday of a month), not the
DST transition. 

---------------------------------------------------------------------- 
 kern - 10-31-07 12:15  
---------------------------------------------------------------------- 
I'm sorry, I have no idea what you are talking about when you say "The
system's localtime goes 02:59, 03:00, 03:59, 03:00, 03:59, 04:00, 05:00,".

Most system make an abrupt jump from one time to another when changing
from DST to non-DST but not 6 jumps as you seem to indicate. Either you are
not clearly explaining the situation or you have a very badly broken
system.

Please describe what is happening and show *only* those jobs that ran
multiple times or where not run. 

---------------------------------------------------------------------- 
 terom - 10-31-07 12:35  
---------------------------------------------------------------------- 
I'll try and express what I meant with the localtime more clearly:
... 02:59, 03:00 ... 03:59, 03:00 ... 03:59, 04:00 ...

Point being, the time interval 03:00 ... 03:59 occurs twice. Somehow, this
causes jobs scheduled to run at 03:00 to run three times:

Job Name           JobIDs

RanssiFullNightly (753, 754, 759)
ShellFullNightly  (755, 756, 760)
BaculaSettings    (757, 758, 761)

The fix for this issue on my part would be to have the jobs run at a time
not in the interval (03:00 ... 03:59), but I found it somewhat weird that
the jobs ran three times. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
10-28-07 09:18  terom          New Issue                                    
10-28-07 10:43  terom          Note Added: 0002906                          
10-31-07 12:15  kern           Note Added: 0002909                          
10-31-07 12:15  kern           Status                   new => feedback     
10-31-07 12:35  terom          Note Added: 0002910                          
======================================================================