Minimum Logs to Attach to Issue

In order to display the complete joblog, from bconsole simply type:

@tee /tmp/joblog-XXXX
llist joblog jobid=XXXX
@tee

  • Where XXXX is the jobid of the job in error.

  • You can now open a support case and simply attach or copy/paste the content of the file /tmp/joblog-XXXX.

  • If you use a plugin, there are possibly complementary logs in a dedicated /opt/bacula/working subdirectory.

  • If you experience a crash of a Bacula service (Director/File Daemon/Storage Daemon), there are .lockdump and .traceback files located in /opt/bacula/working that are important for our development team to analyze to find the root cause of the issue. Please add them to the ticket.

  • These lockdump and traceback files are generated only if the typical platform debugger, typically gdb is installed and can attach to a crashing process. Both is not, by default, the case on a reasonably hardened system, so it may be necessary to install and configure some dependencies.

See also

Go back to:

Go to:

Go back to the Reporting Issues chapter.

Go back to the Best Practices chapter.

Go back to the main Bacula Enterprise Configuration page.