From: Mantis B. T. <no...@bu...> - 2014-07-12 09:07:01
|
The following issue has been CLOSED ====================================================================== http://bugs.bacula.org/view.php?id=2074 ====================================================================== Reported By: roos Assigned To: ====================================================================== Project: Bacula Bug Reports Issue ID: 2074 Category: File Daemon Reproducibility: always Severity: minor Priority: low Status: closed Resolution: fixed Fixed in Version: 7.0.5 ====================================================================== Date Submitted: 2014-06-26 08:53 BST Last Modified: 2014-07-12 10:06 BST ====================================================================== Summary: fd prints error in mem_pool.c when configfile is missing Description: When bacula-fd.conf cannot be found, fd prints a mem_pool error instead of a meaningful error message (e.g. "<path>/bacula-fd.conf not found") Current error printed: bacula-fd: ABORTING due to ERROR in mem_pool.c:156 obuf is NULL Bacula interrupted by signal 4: Illegal instruction Kaboom! bacula-fd, bacula-fd got signal 4 - Illegal instruction at 26-Jun-2014 00:49:20. Attempting traceback. ====================================================================== ---------------------------------------------------------------------- (0006961) kern (administrator) - 2014-07-12 09:56 http://bugs.bacula.org/view.php?id=2074#c6961 ---------------------------------------------------------------------- Yes, it forgot to allocate memory when trying to display an error message. ---------------------------------------------------------------------- (0006965) kern (administrator) - 2014-07-12 10:06 http://bugs.bacula.org/view.php?id=2074#c6965 ---------------------------------------------------------------------- Thanks. I have now fixed this in version 7.0.5 to be released in the next couple of weeks. Bacula still stops running, but it now knows how to print its error message. Issue History Date Modified Username Field Change ====================================================================== 2014-06-26 08:53 roos New Issue 2014-07-12 09:56 kern Note Added: 0006961 2014-07-12 09:56 kern Status new => confirmed 2014-07-12 10:06 kern Note Added: 0006965 2014-07-12 10:06 kern Status confirmed => closed 2014-07-12 10:06 kern Resolution open => fixed 2014-07-12 10:06 kern Fixed in Version => 7.0.5 ====================================================================== |