I was checking logs, and I noticed some odd behavior on a 404.
uwsgi/pyramid was listing a SIGPIPE + IOError
This was on an earlier version of uwsgi (1.9.14). I upgraded to latest and
everything works as it should.
I'd just like to make sure I'm not missing anything. Has anyone
experienced this before? I couldn't find anything about this behavior in
the uwsgi changelogs. i just want to make sure this was a uwsgi error that
is now fixed by the upgrade, and not something from pyramid.
----
SIGPIPE: writing to a closed pipe/socket/fd (probably the client
disconnected) on request /path/to/404 (ip 206.217.86.228) !!!
uwsgi_response_write_body_do(): Broken pipe [core/writer.c line 260]
IOError: write error
[pid: 11156|app: 0|req: 27/39] 206.217.86.228 () {50 vars in 1964 bytes}
[Fri Feb 12 20:28:00 2016] GET /path/to/404 => generated 0 bytes in 8 msecs
(HTTP/1.1 404) 3 headers in 442 bytes (0 switches on core 0)
--
You received this message because you are subscribed to the Google Groups
"pylons-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to pylons-discuss+unsubscr...@googlegroups.com.
To post to this group, send email to pylons-discuss@googlegroups.com.
Visit this group at https://groups.google.com/group/pylons-discuss.
For more options, visit https://groups.google.com/d/optout.
