[Top][All Lists]

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

Re: [Chicken-users] Spiffy crashes occasionally

From: felix winkelmann
Subject: Re: [Chicken-users] Spiffy crashes occasionally
Date: Wed, 8 Jun 2005 07:43:14 +0200

On 6/7/05, Peter Bex <address@hidden> wrote:
> > I think it *might* be related to another weird thing I noticed.  Sometimes
> > Spiffy, if started on a terminal, dumps a copy of the files it's serving
> > to that terminal.  I don't know when exactly it starts to do this, though :(
> Haven't been able to find the cause of the crash, but I ran spiffy in a
> screen session and logged its output.  And behold, I got binary-looking
> file output again.  After looking at the logfile, I noticed the error
> is the following (with special characters replaced by their hex values):
> thread thread1663 terminated with exception: can not write to socket: (5 "<8A>

The output is just the standard error messages of a failed write. It seems
that the socket is closed unexpectedly. I get this error from time to time,
but mostly with a single newline ("can not write to socket: (5 "\n")"). So
it's likely that spiffy tries to write one byte too much. Is it possible that
the client communicating with spiffy in this case closes the connection
too early? The server should handle this problem more gracefully, though.
I will try to address this.

I have not experienced any lockups with spiffy. The only other problem
I found is with broken clients: for example wget sends a keep-alive header,
even if retrieving a single file. Since spiffy doesn't handle timeout, the
connection stays open until the client is forced to quit.


reply via email to

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