Just did. Now I get "no PONG received in less than XXX" where XXX is the timeout I set for the uwsgi_read_timeout.
This is a one way web application: the client writes to the web socket but the server does not need to send anything back. On Mon, May 5, 2014 at 12:00 PM, <[email protected]> wrote: > Send uWSGI mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of uWSGI digest..." > > > Today's Topics: > > 1. Errors in nginx logs (Rui Pacheco) > 2. Re: Errors in nginx logs (Aarni Koskela) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 5 May 2014 11:47:26 +0200 > From: Rui Pacheco <[email protected]> > To: [email protected] > Subject: [uWSGI] Errors in nginx logs > Message-ID: > <CALGXG_rS0m06hKHSs= > [email protected]> > Content-Type: text/plain; charset="utf-8" > > I have setup uwsgi to work with nginx but I keep seeing these errors on my > logs: > > 2014/05/05 11:45:14 [error] 9149#0: *268037 upstream timed out > (110:Connection timed out) while reading upstream, client > : 86.36.49.200, server: api.xxx.com, request: "GET /socket HTTP/1.1 > > ", upstream: "uwsgi://unix:/var/run/uwsgi/xxx.sock:", host: "api.xxx.com" > > > Google says I should change my nginx settings: fastcgi_read_timeout 300s; > or proxy_read_timeout 300; but neither seems to work. > > > Has anyone fixed this before? > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.unbit.it/pipermail/uwsgi/attachments/20140505/62f2a02d/attachment-0001.html > > > > ------------------------------ > > Message: 2 > Date: Mon, 5 May 2014 10:09:40 +0000 > From: Aarni Koskela <[email protected]> > To: uWSGI developers and users list <[email protected]> > Subject: Re: [uWSGI] Errors in nginx logs > Message-ID: > < > 7482bf37420645e2a4d5c30570d3f...@db4pr07mb316.eurprd07.prod.outlook.com> > > Content-Type: text/plain; charset="utf-8" > > The relevant nginx configuration entry for uwsgi is (kinda logically) > uwsgi_read_timeout. ( > http://wiki.nginx.org/HttpUwsgiModule#uwsgi_read_timeout) > > Try that? :) > > - Aarni > > From: [email protected] [mailto:[email protected]] > On Behalf Of Rui Pacheco > Sent: 5. toukokuuta 2014 12:47 > To: [email protected] > Subject: [uWSGI] Errors in nginx logs > > I have setup uwsgi to work with nginx but I keep seeing these errors on my > logs: > > 2014/05/05 11:45:14 [error] 9149#0: *268037 upstream timed out (110: > Connection timed out) while reading upstream, client: 86.36.49.200, server: > api.xxx.com, request: "GET /socket HTTP/1.1 > ", upstream: "uwsgi://unix:/var/run/uwsgi/xxx.sock:", host: "api.xxx.com" > > Google says I should change?my nginx settings:?fastcgi_read_timeout 300s; > or?proxy_read_timeout 300; but neither seems to work. > > Has anyone fixed this before? > > ------------------------------ > > _______________________________________________ > uWSGI mailing list > [email protected] > http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi > > > End of uWSGI Digest, Vol 56, Issue 4 > ************************************ >
_______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
