Re: Bacula 15.0.2 - Windows Clients name-fd.trace File Grows Extremely Fast
Eric Bollengier via Bacula-users <[email protected]>
| Newsgroups | gmane.comp.bacula.user |
|---|---|
| Message-ID | <[email protected]> |
Hello, thanks for the report, I have uploaded a new version of the binary on bacula.org without the trace problem. It's called 15.0.2-3. The previous one is no longer on the main page. Best Regards, Eric On 9/21/24 00:15, Arno Lehmann wrote: > Hi Derek, > > Am 20.09.2024 um 20:37 schrieb Derek Bable: >> Hi All, >> >> I am having a strange issue regarding Bacula 15.0.2 on Windows Clients. >> Clients were installed using the Bacula 15.0.2 Binaries from bacula.org. >> >> We noticed that the C:\Program Files\Bacula\working\host-fd.trace file grows >> extremely fast every time a backup occurs. Here is an example of what events >> we see. These events seem like they are occurring with every directory >> specified to include in our fileset for each client: > ...> I’ve already tried disabling debug logging / tracing on the QB client >> above (opened bconsole on server and ran ‘setdebug level=0 trace=0 >> client=QB’), but I still continue to see thousands of these entries display in >> the trace log when a backup is run. > > If I recall correctly, we had something very similar with the enterprise edition > recently. The fix needed a rebuild. So for now, I would propose downgrading to > an older bacula-fd on Windows (unless you need new functions / fixes, of course) > and report this via the bug tracker. > > With a bit of luck, I'll recall this on Monday and see if I can reach out to > Eric :-) > > Cheers, > > Arno > _______________________________________________ Bacula-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bacula-users