Re: A minor puzzle

Hi Phil,

Am 02.03.2026 um 16:58 schrieb Phil Stracchino:
> On 3/2/26 02:33, Arno Lehmann via Bacula-users wrote:
>> Hi Phil, all,
>>
>> Am 01.03.2026 um 18:02 schrieb Phil Stracchino:
>>> There *should* have been a set of incremental backups this morning
>>> starting at 04:30.
>>
>> No.
>>
>> 1st Monday meens "the Monday in the first week of the month".
>>
>> A week always starts with a Monday and ends with a Sunday in Bacula.
>>
>> First week this month only consisted of a Sunday.
> 
> Arno,
> I don't think this is correct, and it isn't answering the correct problem.

Well, I still think I'm right (but I know I'm biased) but of course 
you're absolutely right that I missed your point... sorry for that. 
Monday morning syndrome is the excuse I claim, although that implies I 
should have noticed it's no longer Sunday...

> Today is Monday March 2, the first Monday in March, the Monday of 
> technically the second week, and the monthly Full backups ran exactly as 
> they were scheduled to, exactly as they always have, month after month 
> without fail since about 2001.  There's no problem there.  The Monday 
> directives are working fine.
> 
> 
> The *problem* is that yesterday, *SUNDAY* March 1, the Incrementals that 
> *should* have run, that run *every* Tuesday through Sunday, didn't. 
> That's what I'm trying to find an explanation for.

Some possible causes are already ruled out. So we should consider a 
potential bug in Bacula. You could try to check if there are any jobs in 
the catalog in an unxpected state -- I'm thinking of 'C' for "created 
but not yet running":

In bconsole:
sql
select * from job where jobstatus = 'C';

In fact I'm thinking of a very particular issue that some colleagues are 
currently working on; not the best fit in your case as there seems to be 
no log output at all in your case, and the scenario I have in mind would 
usually log at least the "Start Backup JobId "-line, but that could be 
missed depending on logging and reporting settings, I guess.

I suppose you did not do any configuration changes in between the last 
jobs and the ones you're missing, right?

Also, how did you install your Bacula? From packages? If so, which ones, 
and if not, how did you build? (This is mostly for future references... 
I don't claim to have any good idea regarding build options or any fancy 
patches.)

Also, is there anything in 'status client' output that would imply any 
of the missing jobs actually started doing something?

If you want to understand what's going on, it might help to add new 
logging, using the comparatively new message type "Events" which afaik 
is not included in "All", but which should provide information about a 
job start from an early stage on.


Cheers,

Arno

> 
> 

-- 
Arno Lehmann

IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück



_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users