Hello,

On 3/13/2006 11:49 PM, Tim Howland wrote:

Hey guys- I'm trying to get bacula up and running.

I've been working through the initial tutorial example, so it isn't an issue with a tape drive or autochanger. I can label the new volume, but when I try to actually run the backup, it looks like the storage daemon crashes out.

Try compiling with -O0 (that is Oh-zero) as this is a known issue with x64 architecture and Bacula... seems to be a code generating bug in gcc. AFAIR there is something mentioned in the manual, too.

Arno

This is the error that's reported:

13-Mar 17:21 ridcully-dir: Client1.2006-03-13_17.19.04 Fatal error:
    Storage daemon didn't accept Device "FileStorage" because:

 JobId:                  3
 Job:                    Client1.2006-03-13_17.19.04
 Backup Level:           Full (upgraded from Incremental)
Client: "ridcully-fd" x86_64-unknown-linux-gnu,redhat,(Stentz)
 FileSet:                "Full Set" 2006-03-13 17:06:18
 Pool:                   "Default"
 Storage:                "File"
 Scheduled time:         13-Mar-2006 17:19:02
 Start time:             13-Mar-2006 17:19:06
 End time:               13-Mar-2006 17:21:47
 Priority:               10
 FD Files Written:       0
 SD Files Written:       0
 FD Bytes Written:       0
 SD Bytes Written:       0
 Rate:                   0.0 KB/s
 Software Compression:   None
 Volume name(s):
 Volume Session Id:      1
 Volume Session Time:    1142288302
 Last Volume Bytes:      0
 Non-fatal FD errors:    0
 SD Errors:              0
 FD termination status:
 SD termination status:
 Termination:            *** Backup Error ***



The GDB output suggests it's a segfault:

(gdb) run -s -f -c /etc/bacula/bacula-sd.conf
Starting program: /sbin/bacula-sd -s -f -c /etc/bacula/bacula-sd.conf
[Thread debugging using libthread_db enabled]
[New Thread 46912498478560 (LWP 18490)]
Detaching after fork from child process 18491.
[New Thread 1084229984 (LWP 18492)]
[Thread 1084229984 (LWP 18492) exited]
[New Thread 1094719840 (LWP 18493)]
[New Thread 1084229984 (LWP 18505)]
[Thread 1084229984 (LWP 18505) exited]
[New Thread 1084229984 (LWP 18508)]
[Thread 1084229984 (LWP 18508) exited]
[New Thread 1084229984 (LWP 18516)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 1084229984 (LWP 18516)]
fnmatch (pattern=0x20 <Address 0x20 out of bounds>, string=0x564478 "FileStorage", flags=0) at fnmatch.c:35
35        while ((c = *p++) != '\0')
Current language:  auto; currently c++

I compiled my own version of bacula (1.38.5), against mysql v. 5.0.18. Is this an artifact of running AMD_64? Should I try to track down binaries for x86_32?


Here's my config.out:

Configuration on Mon Mar 13 17:01:10 EST 2006:

 Host:                       x86_64-unknown-linux-gnu -- redhat (Stentz)
 Bacula version:             1.38.5 (18 January 2006)
 Source code location:       .
 Install binaries:           /sbin
 Install config files:       /etc/bacula
 Scripts directory:          /etc/bacula
 Working directory:          /var/bacula/working
 PID directory:              /var/run
 Subsys directory:           /var/run/subsys
 Man directory:              /usr/share/man
 Data directory:             /usr/share
 C Compiler:                 gcc 4.0.1
 C++ Compiler:               /usr/bin/g++ 4.0.1
 Compiler flags:              -g -O2 -Wall
 Linker flags:
 Libraries:                  -lpthread
 Statically Linked Tools:    no
 Statically Linked FD:       no
 Statically Linked SD:       no
 Statically Linked DIR:      no
 Statically Linked CONS:     no
 Database type:              MySQL
 Database lib:               -L/usr/local/mysql//lib -lmysqlclient_r -lz

 Job Output Email:           [EMAIL PROTECTED]
 Traceback Email:            [EMAIL PROTECTED]
 SMTP Host Address:          localhost

 Director Port:              9101
 File daemon Port:           9102
 Storage daemon Port:        9103

 Director User:
 Director Group:
 Storage Daemon User:
 Storage DaemonGroup:
 File Daemon User:
 File Daemon Group:

 SQL binaries Directory      /usr/local/mysql//bin

 Large file support:         yes
 Bacula conio support:       yes -ltermcap
 readline support:           no
 TCP Wrappers support:       no
 TLS support:                no
 ZLIB support:               yes
 enable-smartalloc:          yes
 enable-gnome:               no
 enable-wx-console:          no
 enable-tray-monitor:
 client-only:                no
 build-dird:                 yes
 build-stored:               yes
 ACL support:                yes
 Python support:             no

It compiled without errors.

I haven't messed with the configuration files at all. I found a few scattered issues with amd_64 on the mailing list archives, but nothing looked like this problem. Any insight or assistance is appreciated!

Thanks,

Tim

--
Tim Howland
Watchdog Systems, LLC
(978) 225-8494
http://wdogsystems.com



--
IT-Service Lehmann                    [EMAIL PROTECTED]
Arno Lehmann                  http://www.its-lehmann.de


-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to