[mod-lisp-devel] Re: mod_lisp: broken pipe (UNIX::SIGPIPE-HANDLER) errors

[Marc Battyani]

"Denis Papathanasiou" <denis at banrai.com> wrote:
> Marc Battyani wrote:
>> It's this fix:
>>
>> Version 2.3
>> Force Apache to read all the Lisp reply before eventually closing the 
>> socket or handling another request.
>> This avoids trying to write to a closed socket or having Lisp and Apache 
>> out of sync.
>> (contributed by Edi Weitz)
>
> Hmmm... so we have Edi's fix incorporated in the version we're already 
> using.
>
> I did look a bit further in the mailing list and saw your conversation 
> with him about lisp possibly taking too long for Apache, then timing out 
> (on the Apache side).
>
> I looked in the Apache error log and found entries like this:
>
>> [error] (70007)The timeout specified has expired: error reading from Lisp
>
> but in the backtrace, the lisp reply (in the form the html string) was 
> fully formed.
>
> If it is related to an Apache timeout b/c our lisp process (outside of 
> mod_lisp) took too long, wouldn't we land in the debugger *before* the 
> reply could become fully formed?

Well it looks like you are one the good way to find out. :)
It's probably some mismatch between the Lisp and Apache.
Maybe the content-size is not right. Have you tried to set it to -1 so that 
Apache closes the socket after each reply, just to check?

Marc