|
From: Arno L. <al...@it...> - 2026-03-02 22:32:28
|
Hi Phil,
Am 02.03.2026 um 23:09 schrieb Phil Stracchino:
...
> Locally compiled on each host from the Gentoo ebuild.
Interesting, as I suppose this is a rather rarely used platform, so
probably one where fany settings or dependcies could introduce
unexpected behaviour. The only problem being that I still think the
scheduler would hardly be something where such things are relevant :-)
>
>> Also, is there anything in 'status client' output that would imply any
>> of the missing jobs actually started doing something?
>
> Nope.
At least not unexpected, but thanks for confirming!
>> 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.
>
> So I'd change:
>
> Messages {
> Name = Director
> append = "/var/log/bacula.log" = all, !skipped
>
> to 'all, events, !skipped'?
>
> And then just wait for it to happen again, I suppose... and remember to
> follow up if and when it does.
For simplicity it might actually help to introduce a separate append or
syslog line exclusively for events.
Syslog when you have some sort of automated log processing / checking in
place where, for exapmple, you could correlate job start events with job
end ones thus notice where starts without ends occur.
Plain text log file if you don't want your readable Bacula logs
cluttered with events information which are less suitable for human
digestion.
"Skipped" is about individual files that were skipped due to explicit
confguration iirc -- I never really needed/wanted/relied upon this. On
the other hand, I have a bunch of carefully crafted exclude options that
would lead to massive logs of boring contents *for me*... so, if you
never missed that information, I'd suggest you leave that part as it is.
Cheers,
Arno
>
>
--
Arno Lehmann
IT-Service Lehmann
Sandstr. 6, 49080 Osnabrück
|