On Mon, May 16, 2011 at 08:50:25AM -0400, John Drescher wrote:
> On Mon, May 16, 2011 at 8:45 AM, Uwe Schuerkamp
> wrote:
> > On Mon, May 16, 2011 at 08:39:38AM -0400, John Drescher wrote:
> >>
> >> Maybe do what it says.
> >>
> >> echo 0 > /proc/sys/kernel/hung_task_timeout_secs
> >>
> >> John
>
On Mon, 16 May 2011 08:39:38 -0400
John Drescher wrote:
> > for a couple of weeks now I occasionally see messages like these in
> > the kernel log or our bacula server (bacula 5.0.3 compiled from
> > source on centos 5.6 64bit):
> >
> >
On Mon, May 16, 2011 at 8:45 AM, Uwe Schuerkamp
wrote:
> On Mon, May 16, 2011 at 08:39:38AM -0400, John Drescher wrote:
>>
>> Maybe do what it says.
>>
>> echo 0 > /proc/sys/kernel/hung_task_timeout_secs
>>
>> John
>
> Hi John,
>
> thanks for your reply, I was wondering if it's an error that I nee
On Mon, May 16, 2011 at 08:39:38AM -0400, John Drescher wrote:
>
> Maybe do what it says.
>
> echo 0 > /proc/sys/kernel/hung_task_timeout_secs
>
> John
Hi John,
thanks for your reply, I was wondering if it's an error that I need to
look info or bacula's "expected behaviour" in those circumstan
On Mon, May 16, 2011 at 2:14 AM, Uwe Schuerkamp
wrote:
> Hi folks,
>
> for a couple of weeks now I occasionally see messages like these in
> the kernel log or our bacula server (bacula 5.0.3 compiled from source
> on centos 5.6 64bit):
>
> ##
Hi folks,
for a couple of weeks now I occasionally see messages like these in
the kernel log or our bacula server (bacula 5.0.3 compiled from source
on centos 5.6 64bit):
##
INFO: task bacula-sd:12467 blocked for more than 120 s
