Open kylemacfarlane opened 7 years ago
This issue doesn't seem to exist if uwsgi is accessed directly by running with --http
. This means it must be an nginx setting but I can't figure out what it could be. Adjusting uwsgi_buffers
or even completely turning off uwsgi_buffering
don't help.
Does it make any difference if you enable post-buffering ?
Websockets won't even connect when I use --post-buffering
.
Did you manage to fix this? I'm also having this issue.
@lucasdavid I never managed to completely fix it but for me it's pretty rare in production. I think it's something related to #1716 combined with some nginx setting.
Does it still happen in 2.0.16?
@funkybob I haven't tested 2.0.16 but it was still happening in master from mid-January.
I did find that switching from ugreen to gevent reduced the errors but didn't completely fix it like I claimed in #1716.
Using uWSGI 2.0.15 and Python 3.5.1.
My WSGI script is a copy of: https://github.com/unbit/uwsgi/blob/2.0.15/tests/websockets_chat_async.py
I run it with:
When I try to send messages >200-255kb I get the following error:
1) This "timeout" happens immediately - not after 60s and is not affected by
uwsgi_read_timeout
.2) The max size that can be sent varies each time uWSGI is started but it always seems to be between 200-255kb.
3) I've tried increasing options like
ugreen-stacksize
andwebsockets-max-size
but they have no affect.