[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-meisters] Restart of apache required

From: Felix
Subject: Re: [Chicken-meisters] Restart of apache required
Date: Mon, 09 May 2011 07:14:51 +0200 (CEST)

From: Peter Bex <address@hidden>
Subject: Re: [Chicken-meisters] Restart of apache required
Date: Sun, 8 May 2011 14:38:59 +0200

> On Wed, May 04, 2011 at 05:57:16AM -0400, Felix wrote:
>> > I put the logs in /home/mario/spiffy-hang/2011-05-04
>> > 
>> > It says the following in init.log:
>> > 
>> > switching to #<thread: thread181594>
>> > #<thread: thread181594> blocks for timeout -2147409012.0
>> > ##sys#thread-block-for-timeout!: invalid timeout
>> > [] 
>> > ...more...
>> > 
>> > What's going on?
>> A negative timeout value. This seems to happen from time to time, I
>> don't know the reason for this. The places where this procedure is
>> called are the srfi-18 API functions, so this already is an invalid
>> argument passed to library functions. There are some lowlevel eggs
>> like sendfile that call these internal blocking-procedures, IIRC, and
>> there also incorrect timeout-argument values are possible.
> I'm not sure, but it looks like another bug today.  Spiffy didn't
> respond either and at first I thought it had simply crashed, but when
> I did a "restart" it killed off a process.  Have a look at
> spiffy-hang/2011-05-08/debug.log: there you see LOTS of messages
> "thread29893: closing off".  That shouldn't only happen once for each
> thread.  Somehow the thread returned by (current-thread) is the same
> more than once.  It should only get to the part where it says
> "closing off" once.

Who produces this message?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]