I'm testing bacula 2.2.4 and the bacula-sd daemon repeatedly exits with a 
segmentation fault. Bacula 1.38.11 works reliably on the same machine with the 
same hardware and configuration 
files.

Environment:
        Fedora Core 1
        Kernel 2.4.26
        gcc 3.3.2
        MySQL 5.0.22
        Dell PV 132T autochanger
        
Build configuration script:
        ./configure \
                 --prefix=/usr/local/bacula-2.2.4      \
                 --disable-nls \
                 --disable-ipv6        \
                 --enable-batch-insert \
                 [EMAIL PROTECTED]    \
                 [EMAIL PROTECTED]     \
                 --with-db-name=bacula2        \
                 --with-mysql  \
                 --mandir=/usr/local/bacula-2.2.4/man  \
                 --with-pid-dir=/usr/local/bacula-2.2.4/var/run        \
                 --with-subsys-dir=/usr/local/bacula-2.2.4/var/subsys  \
                 --with-dir-user=bacula        \
                 --with-dir-group=bacula       \
                 --with-sd-user=bacula \
                 --with-sd-group=bacula        \
                 --with-fd-user=root   \
                 --with-fd-group=root && make


I'm using the same configuration files for the director, sd, and fd that work 
with the 1.38.11 installation (after removing the "Accept Any Volume" 
directive, changing
the paths for 2.2.4, and adding the directive "RecyclePool = Scratch").

The software compiles without error. There were no errors from "btape test" or 
"btape autochanger".

The bacula-sd daemon crashes repeatedly whether or not the variable 
LD_ASSUME_KERNEL was set to "2.4.19" before compiling bacula.

The bacula-sd daemon is running as root (while I sort out an issue that's not
present in 1.38.11 with permissions on the tape device). The bacula-dir normally
runs as user "bacula". 

Even if I modify the bacula-dir options to run it as root, no traceback file is
generated. The message (received via email) from Bacula is:
        
        Using host libthread_db library "/lib/libthread_db.so.1".
        0x401728d1 in ?? ()
        /usr/local/bacula-2.2.4/etc/btraceback.gdb:1: Error in sourced command 
file:
        Cannot access memory at address 0x80a2e34

The fault seems to occur right after the SD begins despooling data. I've got 4 
log files from running the SD with debugging on (set to 200 or higher), and the 
error always happens after the first instance of despooling data. In each case, 
the log file shows "stored.c:582 In terminate_stored() sig=11".

I've attached an excerpt from the SD debugging output.


Thanks,

Mark


----
Mark Bergman                      [EMAIL PROTECTED]
System Administrator
Section of Biomedical Image Analysis             215-662-7310
Department of Radiology,           University of Pennsylvania

http://pgpkeys.pca.dfn.de:11371/pks/lookup?search=mark.bergman%40.uphs.upenn.edu

Attachment: bacula-2.2.4_SD_debugging
Description: bacula-2.2.4_SD_debugging

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to