On Saturday 15 September 2007 21:09, Marc Schiffbauer wrote:
> * Kern Sibbald schrieb am 15.09.07 um 20:33 Uhr:
> > On Saturday 15 September 2007 16:44, Dan Langille wrote:
> > > FYI, SD is crashing on 2.2.4 for this chap. See other email for
> > > backtrace.
> >
> > Some wild speculation with little info, starting with the less probable:
> >
> > 1. There is some hardware or driver problem with his tape drive. The
> > particular tape may also be bad or blank (it may need an eof written).
>
> The hardware setup has been 100% stable for several years now. About
> 1 year with bacula. 100% stable with bacula 2.0.3. 100% crashes with
> bacula 2.2.3 and 2.2.4.
>
> The tape has been labeled with bacula 2.0.3 and the 2.2.4 SD can
> mount it and reads the correct label. The crash occurs when doing a
> relabel or when running a job.
>
> > 2. His build is bad.
>
> I am using always the same procedure for the build under debian
>
> > 3. A binary built on one OS/architecture was moved to another different
> > OS/architecture.
>
> Built on debian sarge i386, used on the same.
>
> > What is clear is that Bacula died due to a buffer overrun -- something I
> > have never seen in the SD, so this is a very unusual case.
> >
> > Since there is no info on what system he is running, or his Bacula
> > .configure, or the other crashes, I cannot make any more comments.
>
> Debian sarge. (My own packages that I announced on the list as well)
>
> configure:
> cp /usr/share/misc/config.guess /usr/share/misc/config.sub \
> /tmp/buildd/bacula-2.2.4/debian/tmp-build-sqlite/autoconf/
> cd /tmp/buildd/bacula-2.2.4/debian/tmp-build-sqlite && \
> bash ./configure --config-cache \
> --host=i386-linux --build=i386-linux \
> --prefix=/usr \
> --sysconfdir=/etc/bacula
> --with-scriptdir=/etc/bacula/scripts \
> --sharedstatedir=/var/lib/bacula \
> --localstatedir=/var/lib/bacula \
> --with-pid-dir=/var/run/bacula --with-smtp-host=localhost \
> --with-working-dir=/var/lib/bacula \
> --with-subsys-dir=/var/lock \
> --mandir=\${prefix}/share/man \
> --infodir=\${prefix}/share/info \
> --enable-smartalloc --with-python --with-tcp-wrappers
> --with-libiconv-prefix=/usr/include --with-readline=yes
> --with-libintl-prefix=/usr/include --with-x --with-readline=yes
> --with-openssl --with-sqlite --without-mysql --without-postgresql
> --without-sqlite3 --enable-bwx-console
>
>
> Configuration on Sat Sep 15 12:10:05 UTC 2007:
>
> Host: i386-pc-linux-gnu -- debian 3.1
> Bacula version: 2.2.4 (14 September 2007)
> Source code location: .
> Install binaries: /usr/sbin
> Install config files: /etc/bacula
> Scripts directory: /etc/bacula/scripts
> Working directory: /var/lib/bacula
> PID directory: /var/run/bacula
> Subsys directory: /var/lock
> Man directory: ${prefix}/share/man
> Data directory: ${prefix}/share
> C Compiler: i386-linux-gcc 3.3.5
> C++ Compiler: /usr/bin/i386-linux-g++ 3.3.5
> Compiler flags: -g -O2 -Wall
> Linker flags:
> Libraries: -lpthread -ldl
> Statically Linked Tools: no
> Statically Linked FD: no
> Statically Linked SD: no
> Statically Linked DIR: no
> Statically Linked CONS: no
> Database type: SQLite
> Database lib: -L/usr/lib -lsqlite
> Database name: bacula
> Database user: bacula
>
> 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/bin
>
> Large file support: yes
> Bacula conio support: yes -ltermcap
> readline support: no
> TCP Wrappers support: yes -lwrap
> TLS support: yes
> Encryption support: yes
> ZLIB support: yes
> enable-smartalloc: yes
> bat support: no
> enable-gnome: no
> enable-bwx-console: yes wxWidgets 2.4
> enable-tray-monitor:
> client-only: no
> build-dird: yes
> build-stored: yes
> ACL support: yes
> Python support: yes -L/usr/lib/python2.3/config -lpython2.3
> -lutil -lrt Batch insert enabled: yes
>
>
> What can I do/try/test now?
- Run the debugger on it, and make it crash in some different way, maybe that
will tell us something.
- Make the smartalloc routine dump the *full* information it has on the buffer
that was overrun.
- Run the SD with valgrind, maybe it will point out what is overrunning the
buffer.
- Figure out why it is the only SD crashing (at least that is what I deduce
from "one of my SD ... crashes ..." (paraphrased).
- Back up to 2.0.3, rebuild it and see if it crashes too in the same way.
>
> Thanks
> -Marc
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-devel
