Kern Sibbald wrote:
> At this point some sort of SCSI hardware problem is the highest probability as
> I see it. If you can show that it is closelog(), then I would re-evaluate
> that.
Just so this gets to the mailing list archives: I think I've tracked
this down to a problem with calling closel
On Monday 22 March 2010 17:59:26 Hugh Brown wrote:
> Kern Sibbald wrote:
> > Since we still have an open bug, please add this to the bug report.
>
> Hi Kern -- I'm unsure what to do; the bug has been marked closed, and
> I'm reluctant to reopen it just to attach files.
It is OK to re-open the bug
Kern Sibbald wrote:
> Since we still have an open bug, please add this to the bug report.
Hi Kern -- I'm unsure what to do; the bug has been marked closed, and
I'm reluctant to reopen it just to attach files.
If it's a hardware problem, it's a hardware problem -- however, what
confuses me is why
t, 20 Mar 2010 07:59:44 +0100
> CC: [email protected]; [email protected]
> Subject: Re: [Bacula-devel] Problem with SD hang in 5.0.1
>
> Since we still have an open bug, please add this to the bug report.
>
> Kern
>
> On Saturday 20 March 2010 00:06:01 H
Since we still have an open bug, please add this to the bug report.
Kern
On Saturday 20 March 2010 00:06:01 Hugh Brown wrote:
> Kern Sibbald wrote:
> > OK, I think the solution is for Hugh to:
> > 1. Figure out why his alert command is broken
> > 2. Create a script with a timer
> > 3. Disable the
Kern Sibbald wrote:
> OK, I think the solution is for Hugh to:
> 1. Figure out why his alert command is broken
> 2. Create a script with a timer
> 3. Disable the alert
Here's what I've done:
-- Ran backups, no change; got a hang. Restarted sd and director.
-- Commented out the "Alert" sections
On Friday 19 March 2010 20:46:30 Eric Bollengier wrote:
> Le Vendredi 19 Mars 2010 20:41:40, Kern Sibbald a écrit :
> > On Friday 19 March 2010 20:31:34 Hugh Brown wrote:
> > > Kern Sibbald wrote:
> > > > On Friday 19 March 2010 19:19:29 Eric Bollengier wrote:
> > > > By the way, Hugh: If you are 9
Le Vendredi 19 Mars 2010 20:41:40, Kern Sibbald a écrit :
> On Friday 19 March 2010 20:31:34 Hugh Brown wrote:
> > Kern Sibbald wrote:
> > > On Friday 19 March 2010 19:19:29 Eric Bollengier wrote:
> > > By the way, Hugh: If you are 99.9% sure that the problem comes from
> > > "alert" please don't s
On Friday 19 March 2010 20:31:34 Hugh Brown wrote:
> Kern Sibbald wrote:
> > On Friday 19 March 2010 19:19:29 Eric Bollengier wrote:
> > By the way, Hugh: If you are 99.9% sure that the problem comes from
> > "alert" please don't submit a bug report. If there is a race condition,
> > we definitely
Kern Sibbald wrote:
> On Friday 19 March 2010 19:19:29 Eric Bollengier wrote:
> By the way, Hugh: If you are 99.9% sure that the problem comes from "alert"
> please don't submit a bug report. If there is a race condition, we
> definitely would like to see it.
Sorry, I submitted a bug before I saw
On Friday 19 March 2010 19:20:53 Hugh Brown wrote:
> Kern Sibbald wrote:
> > Hello,
> >
> > I recommend that you submit this as a bug report. Please include your
> > bacula-dir.conf and bacula-sd.conf as well as the two files you included
> > here.
>
> Shall do.
>
> > On the timeout for the alert
On Friday 19 March 2010 19:19:29 Eric Bollengier wrote:
> Le Vendredi 19 Mars 2010 19:09:01, Kern Sibbald a écrit :
> > Hello,
> >
> > I recommend that you submit this as a bug report. Please include your
> > bacula-dir.conf and bacula-sd.conf as well as the two files you included
> > here.
> >
>
Kern Sibbald wrote:
> Hello,
>
> I recommend that you submit this as a bug report. Please include your
> bacula-dir.conf and bacula-sd.conf as well as the two files you included
> here.
Shall do.
> On the timeout for the alert command. Adding it would require yet another
> Bacula directive to s
Le Vendredi 19 Mars 2010 19:09:01, Kern Sibbald a écrit :
> Hello,
>
> I recommend that you submit this as a bug report. Please include your
> bacula-dir.conf and bacula-sd.conf as well as the two files you included
> here.
>
> On the timeout for the alert command. Adding it would require yet a
Hello,
I recommend that you submit this as a bug report. Please include your
bacula-dir.conf and bacula-sd.conf as well as the two files you included
here.
On the timeout for the alert command. Adding it would require yet another
Bacula directive to specify the timeout, and that is really a
(Sorry, once more with actual attachments.)
Kern Sibbald wrote:
> At this point, before sending anything, first, please ensure the patch is
> applied. If so, 90% probability you will not have any more problems. If you
> do, the lock manager will produce a nice dump with additional information --
Kern Sibbald wrote:
> At this point, before sending anything, first, please ensure the patch is
> applied. If so, 90% probability you will not have any more problems. If you
> do, the lock manager will produce a nice dump with additional information --
> if it is not emailed to you, you should fi
On Wednesday 17 March 2010 21:18:51 Hugh Brown wrote:
> Kern Sibbald wrote:
> > Yes, that is probably what we want. However, did you apply the patch
> > that Eric recommended?
>
> Nope...I was hoping to duplicate the problem.
OK, being a physicist by training, I understand, but once we squash a b
Kern Sibbald wrote:
> Yes, that is probably what we want. However, did you apply the patch that
> Eric recommended?
Nope...I was hoping to duplicate the problem.
> At this point, before sending anything, first, please ensure the patch is
> applied.
Shall do. Again, thanks very much for your ti
On Wednesday 17 March 2010 19:59:10 Hugh Brown wrote:
> Kern Sibbald wrote:
> > It appears that you have backtraced only a single thread. We need to see
> > all threads. If it was an automatic dump, something went wrong. If you
> > did it manually, probabably you did not enter "thread apply all
Kern Sibbald wrote:
> It appears that you have backtraced only a single thread. We need to see all
> threads. If it was an automatic dump, something went wrong. If you did it
> manually, probabably you did not enter "thread apply all bt" as explained in
> the Kaboom chapter of the manual.
Aha -
Hello,
Eric is travelling. See below.
On Wednesday 17 March 2010 16:49:51 Hugh Brown wrote:
> Eric Bollengier wrote:
> > > After doing some searching, I came across bug #1527
> > > (http://bugs.bacula.org/view.php?id=1527), which looks similar to
> > > problem in one respect: the output of "stat
Eric Bollengier wrote:
> > After doing some searching, I came across bug #1527
> > (http://bugs.bacula.org/view.php?id=1527), which looks similar to
> > problem in one respect: the output of "status storage" in bconsole
> > just hung when it got to "Used volume status". (I'm afraid I did not
> > k
Hi,
Le Mercredi 17 Mars 2010 00:17:59, Hugh Brown a écrit :
> This is a complicated problem; apologies in advance if there's any
> missing information.
>
> I'm running Bacula 5.0.1 on CentOS 5.4, x86_64. I came back from a
> week's vacation today to discover that the storage daemon had become
>
This is a complicated problem; apologies in advance if there's any
missing information.
I'm running Bacula 5.0.1 on CentOS 5.4, x86_64. I came back from a
week's vacation today to discover that the storage daemon had become
hung one day after my vacation started. :-(
Three jobs were running, and
25 matches
Mail list logo
