On 2/19/19 4:59 AM, Vanush "Misha" Paturyan wrote: > On Mon, 18 Feb 2019 at 19:26, Phil Stracchino <ph...@caerllewys.net > <mailto:ph...@caerllewys.net>> wrote: >> I tried strace, but it seems not to follow bacula-dir through >> daemonization. Possibly my invocation is wrong. > > On Linux, use `strace -o strace.log -ff` to trace child processes as > they are forked, > and save output from them into `strace.log.$pid` files (makes it easier > to analyze > those traces)
Thanks, I'll try that. It's been a while since I last had to use it and I'm a bit rusty. >> I did also just notice in Bacula's jobs-run list that it thinks dbcheck >> terminated with a fatal error. This is not apparent from >> bacula-dir.log. I'm running a manual dbcheck now to see whether it >> sheds any light. > > Are you sure your server is not running out of memory and OOM killer not > zapping > your bacula invocations? (this should leave traces in /var/log/syslog or > /var/log/messages > or should be visible with journalctl command, depends on your distribution). There's no OOM events in the logs, as there very well should not be considering the server has 24GB RAM and only about 6GB of it is in active use. -- Phil Stracchino Babylon Communications ph...@caerllewys.net p...@co.ordinate.org Landline: +1.603.293.8485 Mobile: +1.603.998.6958 _______________________________________________ Bacula-devel mailing list Bacula-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-devel
