Your message dated Mon, 22 May 2006 11:56:27 -0500 with message-id <[EMAIL PROTECTED]> has caused the Debian Bug report #367424, regarding bacula-sd segfaults on start with autochanger defined to be marked as having been forwarded to the upstream software author(s) [EMAIL PROTECTED]
(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 ---Hello, I have recently received two bug reports at Debian from people having trouble with the storage daemon segfaulting when it starts up, with an autochanger defined. I have not been able to duplicate the problem myself, but there is some preliminary information below. Before diving in, I should first ask: is this the proper way you'd like me to forward these on, or should I instead submit a bug with the information? Anyway, the bug appears to occur when an Autochanger clause is present. One person reported the problem going away when that clause was removed. We run Bacula with that clause present without this problem, so there seems to be something here that is causing it in some cases but not all. Please note the preliminary debugging results at the very end of this message. Please preserve CCs when replying. Thanks, -- John ----- Forwarded message from Marcus Meyer <[EMAIL PROTECTED]> ----- From: Marcus Meyer <[EMAIL PROTECTED]> Date: Sat, 20 May 2006 00:01:42 +0200 Reply-To: Marcus Meyer <[EMAIL PROTECTED]>, [EMAIL PROTECTED] To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: Bug#367424: bacula-sd segfaults on start with autochanger defined Package: bacula Followup-For: Bug #367424 I have same problems here. When I start bacula-sd with /etc/init.d/bacula-sd start I've got an Error. server:/etc/bacula# /etc/init.d/bacula-sd start Starting Bacula Storage daemon: 15-Mai 22:04 bacula-sd: Fatal Error because: Bacula interrupted by signal 11: Segmentation violation Kaboom! bacula-sd, bacula-sd got signal 11. Attempting traceback. Kaboom! exepath=/usr/sbin/ Calling: /usr/sbin/btraceback /usr/sbin/bacula-sd 25680 Traceback complete, attempting cleanup ... The debugging message: (no debugging symbols found) Using host libthread_db library "/lib/tls/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1213823296 (LWP 25680)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7e601fe in __waitpid_nocancel () from /lib/tls/libpthread.so.0 /etc/bacula/scripts/btraceback.gdb:1: Error in sourced command file: No symbol table is loaded. Use the "file" command. Not much :-( This happens only when I configure the autochanger in the bacula-sd.conf file. Autochanger { Name = ADIC # Description = "ADIC VLS DLT400" Device = AUTO-DLT Changer Device = /dev/sg2 Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d" } Device { Name = AUTO-DLT # Description = "ADIC DLT4000" Media Type = DLT-auto Archive Device = /dev/nst0 AutomaticMount = yes; AlwaysOpen = yes; RemovableMedia = yes; RandomAccess = no; AutoChanger = yes; LabelMedia = no; Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'" Maximum Spool Size = 1895219200 Maximum Job Spool Size = 1695219200 Spool Directory = /var/spool/bacula } bacula-dir.conf : Storage { Name = ADIC Address = server SDPort = 9103 Password = "****************************" Device = ADIC Media Type = DLT-auto Autochanger = yes } When I use the following Dervice Section in bacula-sd.conf then I've got no error but the Changer doesn't work. Device { Name = ADIC # Description = "ADIC DLT4000" Media Type = DLT-auto Archive Device = /dev/nst0 AutomaticMount = yes; AlwaysOpen = yes; RemovableMedia = yes; RandomAccess = no; AutoChanger = yes; LabelMedia = no; Alert Command = "sh -c 'tapeinfo -f %c |grep TapeAlert|cat'" Changer Device = /dev/sg2 Changer Command = "/etc/bacula/scripts/mtx-changer %c %o %S %a %d" Maximum Spool Size = 1895219200 Maximum Job Spool Size = 1695219200 Spool Directory = /var/spool/bacula } I've open a bugreport at bacula.org but the problem is in the debian package. http://bugs.bacula.org/bug_view_advanced_page.php?bug_id=0000615 When I compile the original sources from Sourceforge, I have no error and everything went fine. When I compile the source from debian, then I got the error. I don't know much about the debian/rule file but I thing there must be an error in the compiler flags. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16.16 Locale: [EMAIL PROTECTED], [EMAIL PROTECTED] (charmap=ISO-8859-15) ----- End forwarded message ----- ----- Forwarded message from Jakob Haufe <[EMAIL PROTECTED]> ----- From: Jakob Haufe <[EMAIL PROTECTED]> Date: Thu, 18 May 2006 18:34:12 +0200 Reply-To: Jakob Haufe <[EMAIL PROTECTED]>, [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Bug#367424: bacula-sd segfaults on start with autochanger defined -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! I've got the same problem here. I played a bit with it and found the following: The segfault is in src/stored/autochanger.c:48. There, the list of devices belonging to an autochanger gets iterated. Then something strange happens: The iteration variable (DEVRES* device) is a null pointer which the program tries to dereference. I examined the list that gets iterated with gdb. Its contents is cerrect. Then, for debugging purposes, I added a printf("HERE!") before the first if clause and recompiled. Now the SD starts up fine. Strange thing... The machine here is a P4 with HT, maybe this is a timing issue or race condition? HTH, Jakob -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFEbKIE1YAhDic+adYRAu70AKCCKIEPSZFP12H8n7R5X7fPB8tBiACfWC52 aX80adirNpQqAyTWP2L0JaQ= =Kv2A -----END PGP SIGNATURE----- ----- End forwarded message ----- -- John Goerzen Author, Foundations of Python Network Programming http://www.amazon.com/exec/obidos/tg/detail/-/1590593715
--- End Message ---
