Re: [Bacula-users] bconsole list nextvol triggers director assert?

[Ken J. <KJo...@ec...>]

Hi,

I have encountered a problem which I think may be a bug, and the page at
bugs.bacula.org says the first step in filing a bug report is a post to the
user's mailing list.

I'm running Bacula 2.2, from the 2.2.8-4~bpo40+1 Etch Backports packages on
Debian Etch.

As far as I can tell, a bconsole command of "list nextvol job=ServerBackup"
triggered these entries in the file /var/log/bacula/log (Debian):


14-Mar 13:04 linux2-dir Fatal Error at sql_get.c because: rwl_writelock
failure.  stat=22:  ERR=Invalid argument 

14-Mar 13:04 linux2-dir ERROR in mem_pool.c:163 Failed ASSERT: obuf 

14-Mar 13:04 linux2-dir Fatal Error because Bacula interrupted by signal 11:
Segmentation violation


ServerBackup was the name of a job scheduled to run the next morning.  As
far as I can tell, the Bacula Director exited after writing these error
messages to the log.

Not long prior to this, I had modified pool definitions in the director
configuration file, adding "Use Volume Once = Yes" to several pools used by
the ServerBackup job.  After changing the config file, I used the bconsole
"reload" command.

(I have since read that Use Volume Once is deprecated, and have replaced it
with Maximum Volume Jobs.)

Should this be reported as a bug?

Regards,

Ken Johnson