[hunchentoot-devel] socket timeout errors

[Hans Hübner]

On 5. Juli 2008 17:02, Jeff Cunningham <jeffrey at cunningham.net> wrote:
>
> Now that I've cleaned the Google forest out of my logs I can see something
> else that must be wrong. 20 seconds after *every* new set of page GETs in
> the access_log there is a socket timeout in the error_log:
>
> 127.0.0.1 (76.64.38.115) - [2008-07-05 05:54:09] "GET /ts7200.html HTTP/1.1"
> 200 20220 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9)
> Gecko/2008052906 Firefox/3.0"
> 127.0.0.1 (76.64.38.115) - [2008-07-05 05:54:09] "GET /images/jandm.ico
> HTTP/1.1" 200 - "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9)
> Gecko/2008052906 Firefox/3.0"
>
> [2008-07-05 05:54:29 [ERROR]] Error while processing connection: I/O timeout
> reading #<SB-SYS:FD-STREAM for "a socket" {14564111}>.
>
>
> I believe this is new behavior since I upgraded hunchentoot and switched
> from mod_lisp to mod_proxy (with which I am unfamiliar), in case that might
> have anything to do with it.
>
> I don't have any idea what might be going on here. The pages are complete
> and don't appear to be timing out.

It is the connections that time out, which is "normal".  The error
messages are annoying and need to be taken care of, but they are note
indicative of a problem.  Are you using the release version of
Hunchentoot or the Subversion one?

-Hans