Before reporting a bug, please be sure it is a bug and not a request for support or a feature request (see the menu bar at the left of this page). Bugs are resolved by volunteer Bacula developers (and the community at large). If you have a high priority for your bug or need professional help, please see the Professional Services page of this website.Bacula now has a Mantis bug reporting system implemented by Dan Langille and hosted on his computer. It is web based, easy to use, and we recommend you give it a try. However, before visiting our bugs database, please carefully read the following: To view the bug reports, you can login as user anonymous and password anonymous. The advantage of actually being subscribed is that you will be notified by email of any serious bugs and their resolution. To submit bug reports, you must create an account. You must also use a browser running a US ASCII code page or UTF-8. Some users running Win32 IE with Windows Eastern European code pages have experienced problems interfacing with the system.

Most Bacula problems are questions of support, so if you are not sure if a problem you are having is a bug, see the support page on this site for links to the email lists. However, once you have determined that a problem is a bug, you must either submit a bug report to the bugs database or send an email to the bacula-devel list, otherwise it is possible that the developers will never know about your bug and thus it will not get fixed. You should expect some things to be slightly different in our Bugs handling than many other Open Source projects. Most importantly, we unfortunately cannot give support via the bugs database, also we close bugs very quickly to avoid being overwhelmed. Please don’t take this personally. Officially we support the current major Bacula version as well as the prior major version. This means that if you are using a very old Bacula version (as a lot of people seem to do) we may not look into your problem in detail, but rather, we will ask you to upgrade. Again, please do not take this personally. We do this to be able to have the time to work on current bugs and program new features.

There is a portion of the bugs database that allows you to enter Feature Requests as well as a section that allows
you to enter documentation problems and/or suggestion.

If you want to add a note to the bug report after it is closed, you can do so by reopening the bug, adding a bug note, then closing the bug report again, or for really simple matters, you can send an email to the bacula-devel email list. If a developer closes a bug report and after everything considered, you are convinced there really *is* a bug and you have new information, you can always reopen the bug report.

Information Needed in a Bug Report

For us to respond to a bug report, we normally need the following as the minimum information, which you should enter into the appropriate fields of the bug reporting system:

  • Your operating system
  • The version of Bacula you are using
  • A clear and concise description of the problem
  • If you say “it crashes”, “it doesn’t work” or something similar, you should include some output from Bacula that shows this

If you are having tape problems, please include:

  • The kind of tape drive you have
  • Have you run the btape “test” command?

The first two of these items can be fulfilled by sending us a copy of your config.out file, which is in the main Bacula source directory after you have done your ./configure.In addition, we will sometimes need a copy of your Bacula configuration files (especially bacula-dir.conf).  If you think it is a configuration problem, please don’t hesitate to send the appropriate bacula-xx.conf file if necessary.

Please read the little Bug-Report-HowTo as well.

You can submit a bug or review the list of open or closed bugs by going to: