search

kazeburo / Gazelle

Preforked Plack Handler for performance freaks
https://metacpan.org/release/Gazelle
Other
74 stars 19 forks source link

Vague `failed to writev` error #16

Open frioux opened 9 years ago

frioux commented 9 years ago

Sometimes our server prints out the error: failed to writev from either line 265 or line 238, which call write_chunk and write_psgi_response respectively. It would be nice if they included a little bit more information like why writev failed. Not a big deal though.

kazeburo commented 9 years ago

Do you have a sample code that reproduce this problem?

frioux commented 9 years ago

Sadly no, it happens very rarely in production only

sent from a rotary phone, pardon my brevity On Oct 6, 2015 11:15 AM, "Masahiro Nagano" notifications@github.com wrote:

Do you have a sample code that reproduce this problem?

— Reply to this email directly or view it on GitHub https://github.com/kazeburo/Gazelle/issues/16#issuecomment-145916423.

karupanerura commented 8 years ago

In my environment, failed to writev: -1 errno:32 is printed in log. This is EPIPE error. I think that Gazelle should ignore EPIPE error.

dnmfarrell commented 8 years ago

I didn't know what an EPIPE error was. I found this discussion which said:

EPIPE means that writing of (presumably) the HTTP request failed because the other end closed the connection.

vti commented 6 years ago

Agree with @karupanerura, I get these messages a lot in my logs :(

failed to writev: -1 errno:32 at [...]vendor_perl/5.22.1/x86_64-linux/Plack/Handler/Gazelle.pm line 255.

This happens I presume when the client side closes the connection before receiving all the data. Would be nice if it was ignored.

frioux commented 6 years ago

For what it's worth I think this stopped happening to us entirely when we moved to nginx, which does not expose the underlying server to client disconnects at all.

vti commented 6 years ago

I also have nginx in front. Probably I should just switch to uwsgi.

everissimo commented 4 years ago

I am having the same message error in my logs. It happens many times each day. I also think it would be nice if this error is just ignored.