Your message dated Mon, 9 Oct 2006 11:08:33 -0500
with message-id <[EMAIL PROTECTED]>
and subject line Not a bug
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: bacula-director-mysql
Version: 1.38.11-5
Severity: important
Starting Bacula Director: 17-Sep 01:39 bacula-dir: Fatal Error because:
Bacula interrupted by signal 11: Segmentation violation
Kaboom! bacula-dir, bacula-dir got signal 11. Attempting traceback.
Kaboom! exepath=/usr/sbin/
Calling: /usr/sbin/btraceback /usr/sbin/bacula-dir 5645
/usr/sbin/btraceback: line 18: /usr/sbin/bsmtp: No such file or
directory
Traceback complete, attempting cleanup ...
/etc/init.d/bacula-director: line 53: 5645 Segmentation fault
start-stop-daemon --start --quiet --pidfile $PIDFILE --exec $DAEMON --
$ARGS
failed.
SEGFAULT IS LABEL FOR GOOD SOFTWARE: NO ERROR HANDLING, NO LOG, NO
TRACE, NO HINT ON THE SOURCE OF PROBLEM. MS SCHOOL.
I have found: in this case the reason was my broken config. But this is
nonsense: do not handling config error. If this way operate main
software it is not Linux.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17-2-686
Locale: LANG=C, LC_CTYPE=ru_RU.KOI8-R (charmap=KOI8-R)
Versions of packages bacula-director-mysql depends on:
ii bacula-director-common 1.38.11-5 Network backup, recovery and verif
ii dbconfig-common 1.8.21 common framework for packaging dat
ii debconf [debconf-2.0] 1.5.4 Debian configuration management sy
ii libc6 2.3.6.ds1-4 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-13 GCC support library
ii libmysqlclient15off 5.0.24a-3 mysql database client library
ii libssl0.9.8 0.9.8b-3 SSL shared libraries
ii libstdc++6 4.1.1-13 The GNU Standard C++ Library v3
ii libwrap0 7.6.dbs-11 Wietse Venema's TCP wrappers libra
ii mysql-client-5.0 [mysql-clie 5.0.24a-3 mysql database client binaries
ii python2.3 2.3.5-15 An interactive high-level object-o
ii zlib1g 1:1.2.3-13 compression library - runtime
Versions of packages bacula-director-mysql recommends:
ii mysql-server-5.0 [mysql-serve 5.0.24a-3 mysql database server binaries
-- debconf information:
bacula-director-mysql/mysql/admin-user: root
bacula-director-mysql/purge: false
bacula-director-mysql/import-oldsettings:
bacula-director-mysql/remove-error: abort
bacula-director-mysql/remove_catalog_on_purge: false
* bacula-director-mysql/dbconfig-install: false
bacula-director-mysql/db/app-user: bacula
bacula-director-mysql/upgrade-backup: true
bacula-director-mysql/install-error: abort
bacula-director-mysql/db/dbname: bacula
bacula-director-mysql/remote/host:
bacula-director-mysql/upgrade-error: abort
bacula-director-mysql/remote/port:
bacula-director-mysql/passwords-do-not-match:
bacula-director-mysql/db_host: localhost
bacula-director-mysql/dbconfig-upgrade:
bacula-director-mysql/remote/newhost:
bacula-director-mysql/performing_upgrade: true
bacula-director-mysql/database-type: mysql
bacula-director-mysql/create_tables: true
bacula-director-mysql/mysql/method: unix socket
bacula-director-mysql/internal/reconfiguring: false
bacula-director-mysql/mysql_root_username: root
bacula-director-mysql/dbconfig-reinstall: false
bacula-director-mysql/dbconfig-remove:
bacula-director-mysql/db_user: bacula
--- End Message ---
--- Begin Message ---
----- Forwarded message from Kern Sibbald <[EMAIL PROTECTED]> -----
From: Kern Sibbald <[EMAIL PROTECTED]>
Date: Mon, 9 Oct 2006 17:57:00 +0200
Reply-To: Kern Sibbald <[EMAIL PROTECTED]>, [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Bug#387838: bacula-director-mysql: segfault
The Bacula manual recommends that you test your conf files with ./bacula-xx
-t ...
This will clearly indicate what is wrong and where (in 99.9% of the cases).
If you run Bacula as a daemon, due to the flexibility in Bacula error message
handling, it is very hard to get the user's attention, so Bacula attempts to
produce a traceback, which for some reason in your case seems to be
configured incorrectly. This also would have indicated what the problem is.
Finally, yes Bacula does use SEGFAULT to generate tracebacks when it aborts,
because it is the only portable way of doing so (the Unix abort() is not
portable).
This is not a bug and should be closed.
----- End forwarded message -----
--- End Message ---
