Author: Tobias Dinse <tobias.dinse AT stegbauer DOT info>
Date: Thu, 19 Jul 2012 11:35:16 +0200
Hi all, yesterday we have moved our old physical Servers to an esxi 5 Environment. I created an new VM with Debian 6 x64 - Hardware passtrough for the Controller (h200 / IBM LTO3 Streamer) and bacula
Author: Martin Simmons <martin AT lispworks DOT com>
Date: Thu, 19 Jul 2012 18:11:02 +0100
Looks like you need to upgrade the version of Bacula that is running the bacula-dir to 5.2.6 as well (or both to 5.2.10). __Martin -- Live Security Virtual Conference Exclusive live event will cover
The issue: both bacula-dir and bacula-sd *MUST ALWAYS* be the same version. The clue is the 'Bad Job command', which means the SD was asking to do something it did not understand. Have you put both t
Author: Tobias Dinse <tobias.dinse AT stegbauer DOT info>
Date: Fri, 20 Jul 2012 09:41:26 +0200
on the director: ii bacula-director-common 5.0.2-2.2+b1 network backup, recovery and verification - Director common files ii bacula-director-mysql 5.0.2-2.2+b1 network backup, recovery and verificati
Author: Martin Simmons <martin AT lispworks DOT com>
Date: Fri, 20 Jul 2012 19:11:57 +0100
The next step is to attach gdb to the bacula-sd process before it crashes and then get backtraces with "thread apply all bt". You may need to recompile it with debugging options (CFLAGS="-g"). __Mar
Author: Tobias Dinse <tobias.dinse AT stegbauer DOT info>
Date: Mon, 23 Jul 2012 09:38:44 +0200
Hi, the Debug Informations are on the Attachment. It create it manually like it was shown on the Bacula Homepage. regards Tobias Jul 20 09:35:30 lx03-baculasd-ourcustomer bacula-sd: Bacula interrupte
Author: Martin Simmons <martin AT lispworks DOT com>
Date: Tue, 24 Jul 2012 18:45:48 +0100
That's good, but unfortunately the backtrace doesn't show the function names. Can you recompile bacula with debugging options (just set CFLAGS="-g" in the environment before running configure). Also,
Author: Tobias Dinse <tobias.dinse AT stegbauer DOT info>
Date: Wed, 25 Jul 2012 15:52:19 +0200
Ok, I compiled our 5.0.2 Version of Bacula and attached the new report. I hope this time its better bu I can still see an ????. I also tried to use 5.2.10 with 2 test machines. Both give the same err
Check the actual CFLAGS being used. The SIGSEGV may be due to glibc's buffer overrun protection being inadvertently turned on with the -DFORTIFY_SOURCE flag in CFLAGS. This is particularly true if yo
Author: Martin Simmons <martin AT lispworks DOT com>
Date: Thu, 26 Jul 2012 19:24:17 +0100
Yes, that's better. I think this can be caused by a mismatch between the Director or SD configs. Can you post the Storage, Device and Autochanger sections from the bacula-dir.conf and bacula-sd.conf?
Author: Tobias Dinse <tobias.dinse AT stegbauer DOT info>
Date: Fri, 27 Jul 2012 09:24:24 +0200
Ok, here are the parts of our Configuration Files. Tobias Am 26.07.2012 20:24, schrieb Martin Simmons: Yes, that's better. I think this can be caused by a mismatch between the Director or SD configs.
Author: Martin Simmons <martin AT lispworks DOT com>
Date: Tue, 31 Jul 2012 18:38:14 +0100
There is an inconsistency: bacula-dir.conf: Autochanger = no bacula-sd.conf: Autochanger = yes I think you want Autochanger = no in the bacula-sd.conf because you're not specifying an Autochanger res