Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-04 Thread Robert LeBlanc
On Fri, Jul 2, 2010 at 9:17 AM, Kern Sibbald k...@sibbald.com wrote: Hello Robert, Eric and I finished Bacula Enterprise version 4.0.0 today, a bit faster than I expected, so I am not running all the final tests, which gave me some time to look at the problem. I downloaded the zlib

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Kern Sibbald
On Friday 02 July 2010 06:02:10 Robert LeBlanc wrote: On Wed, Jun 30, 2010 at 8:35 AM, Robert LeBlanc rob...@leblancnet.uswrote: On Wed, Jun 30, 2010 at 1:06 AM, Kern Sibbald k...@sibbald.com wrote: This seems to a support issue. The dump that you posted shows no indication of a crash,

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Robert LeBlanc
On Fri, Jul 2, 2010 at 2:59 AM, Kern Sibbald k...@sibbald.com wrote: The question that I have is am I missing some debug symbols in other packages like open-ssl that would help? I'm not a programmer so backtraces are pretty much a wall of text to me. I want to give helpful info so that

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Kern Sibbald
Hello Robert, Eric and I finished Bacula Enterprise version 4.0.0 today, a bit faster than I expected, so I am not running all the final tests, which gave me some time to look at the problem. I downloaded the zlib source code, and I don't immediately see anything in the file that would

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Frank Sweetser
On 07/02/2010 11:17 AM, Kern Sibbald wrote: Having said this, I cannot rule out a problem on openssl at this point. I forgot to mention one other *very* important data point. After the ticket I opened up came back as a problem outside of bacula, I did some more testing on the system in

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Robert LeBlanc
On Fri, Jul 2, 2010 at 9:44 AM, Frank Sweetser f...@wpi.edu wrote: On 07/02/2010 11:17 AM, Kern Sibbald wrote: Having said this, I cannot rule out a problem on openssl at this point. I forgot to mention one other *very* important data point. After the ticket I opened up came back as a

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Kern Sibbald
On Friday 02 July 2010 17:30:19 Robert LeBlanc wrote: On Fri, Jul 2, 2010 at 9:17 AM, Kern Sibbald k...@sibbald.com wrote: Hello Robert, Eric and I finished Bacula Enterprise version 4.0.0 today, a bit faster than I expected, so I am not running all the final tests, which gave me some

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Kern Sibbald
On Friday 02 July 2010 17:44:33 Frank Sweetser wrote: On 07/02/2010 11:17 AM, Kern Sibbald wrote: Having said this, I cannot rule out a problem on openssl at this point. I forgot to mention one other *very* important data point. After the ticket I opened up came back as a problem outside of

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-02 Thread Kern Sibbald
On Friday 02 July 2010 18:24:13 Robert LeBlanc wrote: On Fri, Jul 2, 2010 at 9:44 AM, Frank Sweetser f...@wpi.edu wrote: On 07/02/2010 11:17 AM, Kern Sibbald wrote: Having said this, I cannot rule out a problem on openssl at this point. I forgot to mention one other *very* important data

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-07-01 Thread Robert LeBlanc
On Wed, Jun 30, 2010 at 8:35 AM, Robert LeBlanc rob...@leblancnet.uswrote: On Wed, Jun 30, 2010 at 1:06 AM, Kern Sibbald k...@sibbald.com wrote: This seems to a support issue. The dump that you posted shows no indication of a crash, which means that your understanding of a crash an mine

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-30 Thread Kern Sibbald
On Tuesday 29 June 2010 05:05:59 Robert LeBlanc wrote: On Thu, Jun 24, 2010 at 2:23 AM, Kern Sibbald k...@sibbald.com wrote: Hello, Either the handle SIGUSR2 nostop noprint pass confused gdb (note it is not necessary when you use -s) or you have something broken on your

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-30 Thread Robert LeBlanc
On Wed, Jun 30, 2010 at 1:06 AM, Kern Sibbald k...@sibbald.com wrote: This seems to a support issue. The dump that you posted shows no indication of a crash, which means that your understanding of a crash an mine are different. This is possibly a deadlock, but I won't spend any more time

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-28 Thread Robert LeBlanc
On Thu, Jun 24, 2010 at 2:23 AM, Kern Sibbald k...@sibbald.com wrote: Hello, Either the handle SIGUSR2 nostop noprint pass confused gdb (note it is not necessary when you use -s) or you have something broken on your build/os/machine. gdb with -s should ignore SIGPIPE and Bacula always

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-24 Thread Kern Sibbald
Hello, Either the handle SIGUSR2 nostop noprint pass confused gdb (note it is not necessary when you use -s) or you have something broken on your build/os/machine. gdb with -s should ignore SIGPIPE and Bacula always ignores SIGPIPE, so the backtrace below is useless and doesn't correspond to

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-23 Thread Kern Sibbald
On Wednesday 23 June 2010 19:41:24 Martin Simmons wrote: On Wed, 23 Jun 2010 08:42:25 -0600, Robert LeBlanc said: My SD has been crashing every night and I finally got a backtrace. I don't know what all this means, but I could sure use some help to figure out why it keeps crashing and

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-23 Thread Robert LeBlanc
On Wed, Jun 23, 2010 at 1:17 PM, Kern Sibbald k...@sibbald.com wrote: Yes, as Martin says, SIGUSR2 is something that should be ignored.  We use it internally to signal between threads, and when you are running the debugger on Bacula, you need to tell the debugger to ignore it -- as Martin

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-23 Thread Kern Sibbald
On Wednesday 23 June 2010 21:24:20 Robert LeBlanc wrote: On Wed, Jun 23, 2010 at 1:17 PM, Kern Sibbald k...@sibbald.com wrote: Yes, as Martin says, SIGUSR2 is something that should be ignored.  We use it internally to signal between threads, and when you are running the debugger on Bacula,

Re: [Bacula-users] [Bacula-devel] Storage Daemon crash backtrace

2010-06-23 Thread Robert LeBlanc
On Wed, Jun 23, 2010 at 1:59 PM, Kern Sibbald k...@sibbald.com wrote: On Wednesday 23 June 2010 21:24:20 Robert LeBlanc wrote: On Wed, Jun 23, 2010 at 1:17 PM, Kern Sibbald k...@sibbald.com wrote: Yes, as Martin says, SIGUSR2 is something that should be ignored. We use it internally to