Hi,
I have latest nginx which I am using as a reverse proxy for an application
of mine running on apache on another server. The nginx config is like this:
upstream upstreamname {
server ip:port;
}
location / {
proxy_pass http://upstreamname;
proxy_redirect off;
proxy_set_h
Hello!
On Sat, Oct 5, 2013 at 2:31 AM, mex wrote:
> your points are valid, but i talk about heisenbugs and the ability
> to monitor a certain ip; you know, theres WTF??? - errors :)
>
It's trivial to do with dynamic tracing tools like systemtap and
dtrace. You don't even need to reload Nginx for
Hi,
I managed to fix it by changing uwsgi as fcgi runner from version 1.4.6 to
version 1.9.17.1, this fixed the issues, not sure what side was wrong.
--
Arkaitz
On Sat, Oct 5, 2013 at 2:45 PM, arkai...@gmail.com wrote:
> Hi all,
>
>
> My version is 0.7.67-3 coming from Debian Squeeze.
> I hav
Maxim Dounin Wrote:
---
> Your use case seems to be perfectly covered by a keepalive connections
>
> support, which is already here. See http://nginx.org/r/keepalive.
OK, yeah that would work for me. Thanks.
There is still the possibility th
Hi all,
My version is 0.7.67-3 coming from Debian Squeeze.
I have tried with squeeze-backports which is version 1.2.1-2.2~bpo60+2 but
I got the same results.
I have reduced this to the smallest config for fastcgi available and it
still does the same.
There are no intercept_redirects directives
hi agentzh,
your points are valid, but i talk about heisenbugs and the ability
to monitor a certain ip; you know, theres WTF??? - errors :)
please note, on the infrastructure i talk about we have usually
debug-logs disabled, and the bottleneck is usually the app-servers.
but thanx for your a
hi maxim,
thanx, thats what i did expected.
i did installed the --with-debug - enabled version on site with ~ 2000 rp/s
during daytime, nothing to see so far.
thanx for checking!
regards,
mex
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,243201,243451#msg-243451
_
