Hi all,
My Flask app is finally up and running, using UWSGI! This is great, but
I’m
hitting a problem if the app takes too long. It talks to an AS400, so
can
sometimes take a while to gather the requested information, parse it,
and
hand back JSON. Sometimes, by the time it does this, Nginx has given up
on
it, so I see an IOError reported in the log because of a broken pipe.
I’m
wondering how I can increase the timeout limit, to make Nginx wait
longer
before closing this connection? Thanks!
On Tue, May 10, 2016 at 03:29:24PM -0400, Alex H. wrote:
Hi there,
Sometimes, by the time it does this, Nginx has given up on
it, so I see an IOError reported in the log because of a broken pipe. I’m
wondering how I can increase the timeout limit, to make Nginx wait longer
before closing this connection? Thanks!
What directive do you use to tell nginx to talk to the upstream service?
Put that directive after “http://nginx.org/r/”, and visit that url. That
should bring you to the documentation for that directive.
Go to the top of the page; there is a list of all of the other
directives
that that module provides.
Probably you care about the “read timeout” directive: you can invite
nginx
to wait longer between successive successful read operations; or you can
configure your upstream service to write something more frequently that
it currently does.
Good luck with it,
f
Francis D. [email protected]
On Tue, May 10, 2016 at 05:09:21PM -0400, Alex H. wrote:
Hi there,
We may be finding the problem… I’m not sure what you mean by ‘upstream
service’.
Somehow, you tell nginx to talk to “the next server”. It can be with
“proxy_pass” or “fastcgi_pass” or, most likely here, “uwsgi_pass”.
“the next server” is the upstream, in this context.
And the directive is whichever *_pass you use here.
Cheers,
f
Francis D. [email protected]
We may be finding the problem… I’m not sure what you mean by ‘upstream
service’. I know I have an upstream context for PHP, which defines the
socket file to use, but I don’t have that for UWSGI. The sample
configurations I found never said to include one, and I don’t have a
deep
enough grasp of how all this works to know what to put in one for UWSGI.
I’ll certainly start looking this up, though.
Hi Alex,
Am 11-05-2016 09:24, schrieb Francis D.:
“the next server” is the upstream, in this context.
And the directive is whichever *_pass you use here.
What Francis could mean could be this.
http://nginx.org/en/docs/http/ngx_http_upstream_module.html
Some basic concept.
http://nginx.org/en/docs/http/load_balancing.html
Maybe you should increase some timeouts in uwsgi
http://nginx.org/en/docs/http/ngx_http_uwsgi_module.html
→ search for timeout.
There are some info’s in the net 
Can you please add the output of
nginx -V
to your answer and the relevant config.
Hth & Best regards
aleks
Yes, I’m using uwsgi_pass:
uwsgi_pass 127.0.0.1:9876;
Hi Alex.
Am 11-05-2016 16:01, schrieb Alex H.:
Yes, I’m using uwsgi_pass:
uwsgi_pass 127.0.0.1:9876 [1];
Hm. I think you have send the mail to early 
Please can you read again my mail and add some more lines to your
answer, thank you.
Best regards
aleks
Ineeed. Sorry about that. The problem is that I can’t capture the output
of
nginx -V, as–for some reason–the > symbol is only producing an empty
file. I can’t copy and paste directly from or to the prompt either. If
you
tell me what you’re looking for in nginx -V, I can tell you that value,
but
there’s a lot of information there.
My site configuration file is:
server {
include restrictions/localOnly;
listen 80;
server_tokens off;
server_name myapp.mysite.com;
location / {
include uwsgi_params;
uwsgi_pass 127.0.0.1:9876;
}
location /static {
alias /var/www/myapp/app/static;
}
}
Hi Alex,
nginx -V uses stderr, so try:
nginx -V 2>/tmp/out.txt
This will redirect stderr to the file instead of stdout.
Kind Regards
Andrew
On 11/05/16 15:34, Alex H. wrote:
listen 80;
Hi there,nginx mailing list
[email protected]
nginx Info Page
–
Andrew H. (LinuxJedi)
Technical Product Manager, NGINX Inc.
Ah, that explains it. Thanks.
nginx -V
nginx version: nginx/1.6.2
TLS SNI support enabled
configure arguments: --with-cc-opt=‘-g -O2 -fstack-protector-strong
-Wformat -Werror=format-security -D_FORTIFY_SOURCE=2’
–with-ld-opt=-Wl,-z,relro --prefix=/usr/share/nginx
–conf-path=/etc/nginx/nginx.conf
–http-log-path=/var/log/nginx/access.log
–error-log-path=/var/log/nginx/error.log
–lock-path=/var/lock/nginx.lock
–pid-path=/run/nginx.pid
–http-client-body-temp-path=/var/lib/nginx/body
–http-fastcgi-temp-path=/var/lib/nginx/fastcgi
–http-proxy-temp-path=/var/lib/nginx/proxy
–http-scgi-temp-path=/var/lib/nginx/scgi
–http-uwsgi-temp-path=/var/lib/nginx/uwsgi --with-debug --with-pcre-jit
–with-ipv6 --with-http_ssl_module --with-http_stub_status_module
–with-http_realip_module --with-http_auth_request_module
–with-http_addition_module --with-http_dav_module
–with-http_geoip_module
–with-http_gzip_static_module --with-http_image_filter_module
–with-http_spdy_module --with-http_sub_module --with-http_xslt_module
–with-mail --with-mail_ssl_module
–add-module=/build/nginx-T5fW9e/nginx-1.6.2/debian/modules/nginx-auth-pam
–add-module=/build/nginx-T5fW9e/nginx-1.6.2/debian/modules/nginx-dav-ext-module
–add-module=/build/nginx-T5fW9e/nginx-1.6.2/debian/modules/nginx-echo
–add-module=/build/nginx-T5fW9e/nginx-1.6.2/debian/modules/nginx-upstream-fair
–add-module=/build/nginx-T5fW9e/nginx-1.6.2/debian/modules/ngx_http_substitutions_filter_module
On Wed, May 11, 2016 at 10:44 AM, Andrew H.
[email protected]