[Bacula-bugs] [bacula 0000065]: wrong ordner of jobs in bacula.log

[<no...@bu...>]

The following bug has been CLOSED
======================================================================
http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000065
======================================================================
Reported By:                buk
Assigned To:                
======================================================================
Project:                    bacula
Bug ID:                     65
Category:                   Director
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     closed
======================================================================
Date Submitted:             14-07-2004 00:02 PDT
Last Modified:              15-07-2004 12:12 PDT
======================================================================
Summary:                    wrong ordner of jobs in bacula.log
Description: 
When jobs with errors occur, the order of their logfile entries is wrong as
you can see in the appended log.
======================================================================

----------------------------------------------------------------------
 kern - 14-07-2004 01:37 PDT 
----------------------------------------------------------------------
You didn't specify why you think the order is wrong, or which items are
wrong -- sorry, I don't see it.

The log file is written to as the events happen as is the case with the
system log file. I see nothing unusual in your log file. If you thing
something is wrong, you will have to be much more specific, and remember a
log file contains items in the order they occur -- it is not the same as a
Job report where all the records for a single job are grouped together.

----------------------------------------------------------------------
 buk - 14-07-2004 02:03 PDT 
----------------------------------------------------------------------
When you look in the appended file you will find these entries:

1.)
Start time:             13-Jul-2004 21:00
End time:               13-Jul-2004 21:02
Termination:            *** Backup Error ***

2.)
Start time:             13-Jul-2004 22:02 <- one hour reschedule, ok
End time:               13-Jul-2004 21:02
Termination:            *** Backup Error ***

3.)
Start time:             13-Jul-2004 23:04
End time:               13-Jul-2004 21:02
Termination:            Backup OK

4.)
Start time:             13-Jul-2004 21:02 <- right after 1.) job
terminated
End time:               13-Jul-2004 21:04

5.)
Start time:             13-Jul-2004 22:04 <- one hour reschedule, ok
End time:               13-Jul-2004 21:04

6.)
Start time:             14-Jul-2004 01:06 <- ran after 3.) job ended, ok
End time:               13-Jul-2004 21:04

*snip*

I think this isn't the correct order, cause that's not order those
entries
where triggered by running jobs.

Correct order: 1, 4, 2, 5, 3, 6

Minor problem, which might be misleading if you don't take a closer look
to it.

edited on: 14-07-04 02:03

----------------------------------------------------------------------
 kern - 15-07-2004 12:12 PDT 
----------------------------------------------------------------------
I'm not sure exactly what is going on here, but I suspect that it is simply
that the job end time was not being properly updated. It would be very hard
for those items to get out of order as they are written sequentially to the
log at the end of the file.

In version 1.35.1, I have done the following things:
1. Print a message to the Job report when the job is rescheduled with the
time/date and the reschedule interval.
2. Always update the job end time. For some reason, it was not always
being updated, which caused rescheduled jobs to have the incorrect end
time/date causing a lot of confusion as you noted.

I am closing this bug because I believe the above will resolve the
confusion.

Bug History
Date Modified  Username       Field                    Change              
======================================================================
14-07-04 00:02 buk            New Bug                                      
14-07-04 00:02 buk            File Added: bacula.log                       
14-07-04 01:37 kern           Bugnote Added: 0000123                       
14-07-04 01:37 kern           Resolution               open => not a bug   
14-07-04 01:37 kern           Status                   new => closed       
14-07-04 02:02 buk            Bugnote Added: 0000126                       
14-07-04 02:02 buk            Resolution               not a bug => reopened
14-07-04 02:02 buk            Status                   closed => feedback  
14-07-04 02:03 buk            Bugnote Edited: 0000126                      
15-07-04 12:12 kern           Bugnote Added: 0000128                       
15-07-04 12:12 kern           Resolution               reopened => fixed   
15-07-04 12:12 kern           Status                   feedback => closed  
======================================================================