[erlang-questions] Common cold or exotic disease

[Marthin Laubscher]

> Claes Wikstrom wrote:
> 
> Marthin Laubscher wrote:
> > Guys,
> >
> > My yaws log is riddled with
> > Yaws process died: {{error,econnreset},
> >                     [{yaws,gen_tcp_send,2},
> >                      {yaws_server,deliver_accumulated,5},
> >                      {yaws_server,handle_ut,4},
> >                      {yaws_server,aloop,3},
> >                      {yaws_server,acceptor0,2},
> >                      {proc_lib,init_p,5}]}
> > Results (what gets to clients) - apparently not affected.
> > Performance - affected.
> > Frequency - Sickeningly often but sadly not consistently enough for a
> > straight forward trace.
> >
> > Before I waste time and energy to trace, isolate and replicate the
> problem,
> > does anybody recognise it as symptomatic of some known problem on my,
> 
> Same error/issue as we've had up on the list here earlier. It's
> the client that close its end before we get to deliver all data for
> a request. It's not an error and thus shouldn't produce any data
> in the errorlog. Fixed this one as well in CVS.
> Next release .....
> 
> 
> /klacke

Thank you so much.

I looked for but missed the previous discussion probably because of wrong
keywords. Perhaps you refer to the 
http://erlang.org/ml-archive/erlang-questions/200603/msg00173.html
thread which got a bit inflamed? 

If it's going to happen often and means nothing then not crashing but
recovering quickly seems the way to go.

On a pragmatic level, is it truly not an error or (another) something a
server has no opportunity/means to control?

Most importantly, how would (with/without the mod) one interpret the log
when trying prove/disprove incomplete data causing client issues. In our
case we're not aware of anything (of value) actually not reaching the client
but I would need to consider whether that's what happens or not.

Thanks again,

Marthin