Show all posts by user
A portal to and from the mailing list.
Re: Premature failover to backup upstream - 11 years ago
Oh, I see what you mean. We're proxying to Tomcat upstreams on separate hosts, not a local fcgi or anything like that. So, still looking for some clues.by adam - Nginx Mailing List - English
Re: Premature failover to backup upstream - 11 years ago
> Are you using UNIX sockets? If so, try using TCP sockets, it might help. Is that a configuration option at compile time?by adam - Nginx Mailing List - English
Premature failover to backup upstream - 11 years ago
Hello! I am using Nginx 1.0.5 to reverse proxy to a pool of three upstreams. One of them is configured as a backup upstream. From time to time, very rarely, a request will be proxied to the backup upstream when it should not be. The two normal upstreams are completely healthy, and at extremely low load. Why might this be happening? I see in the documentation (http://wiki.nginx.org/Httpby adam - Nginx Mailing List - English
Re: Worker processes in hung state after reload - 12 years ago
> That may be my fault. I'm not quite sure. Can your try the latest > development branch of nginx_upstream_check_module( > https://github.com/yaoweibin/nginx_upstream_check_module/tree/development)? Actually since I posted this question, we've been unable to reproduce the condition, no matter how hard we try. If we can reproduce the condition, I will try that branch. I still needby adam - Nginx Mailing List - English
Re: Worker processes in hung state after reload - 12 years ago
> Are you able to reproduce the problem without third party > modules/patches and with latest stable release (1.0.4)? Yes, that was going to be my first stop unless somebody knew of a config fix right away. I will give tha a try. I had seen this in the changelog for version 1.0.0: "Bugfix: a cache manager might hog CPU after reload." Is that what you're thinking?by adam - Nginx Mailing List - English
Worker processes in hung state after reload - 12 years ago
We use Nginx as a reverse proxy. After 2 or 3 reloads (kill -HUP), the parent's one child worker process remains "stuck"; the parent spawns a new one which is also often "stuck." The number of worker_processes we have configured is 1. After a reload, there are 2 workers in the process list. After another reload, 3 workers, and so on. Usually all of these workers are in statby adam - Nginx Mailing List - English
Nginx doesn't pass $server_port through to upstream? - 12 years ago
Hello! I've been using Apache with the proxy_balancer module as a front-end to Tomcat. Part of my Tomcat app needs to know what port the original request came in on ($server_port). It detects this not via header, but by directly grabbing the CGI variable. I'm trying to replace Apache with Nginx, but I've noticed that the $server_port CGI var is not passed by Nginx through to Tomcat in theby adam - Migration from Other Servers
 |
 |
 |
 |
|