Welcome! Log In Create A New Profile

Advanced

RE: Nginx upstream servers status

All files from this thread

File Name File Size   Posted by Date  
emailsiglogo.png 6.6 KB open | download Sajan Parikh 07/03/2013 Read message
smime.p7s 4.4 KB open | download Sajan Parikh 07/03/2013 Read message
emailsiglogo.png 6.6 KB open | download Sajan Parikh 07/03/2013 Read message
smime.p7s 4.4 KB open | download Sajan Parikh 07/03/2013 Read message
emailsiglogo.png 6.6 KB open | download Sandeep L 07/03/2013 Read message
Sandeep L
July 04, 2013 01:40AM
Hi,
After experimenting with some parameters I used following configuration.
upstream appcluster { server host1.example.com:8080 max_fails=1 fail_timeout=1s; server host2.example.com:8080 max_fails=1 fail_timeout=1s; } server { listen *; location / { proxy_pass http://appcluster; proxy_next_upstream error timeout http_404 http_500 http_502 http_503 http_504; proxy_set_header X-Real-IP $remote_addr; proxy_connect_timeout 2; proxy_send_timeout 2; proxy_read_timeout 5; } }
The issue I am facing here is - with similar configuration in lighttpd response time per request 0.3 seconds, where as with nginx it is around 2.5 seconds.
Can someone suggest me how to response time with nginx?
Thanks,Sandeep.

From: sandeepvreddy@outlook.com
To: nginx@nginx.org
Subject: RE: Nginx upstream servers status
Date: Wed, 3 Jul 2013 14:29:23 +0530




While looking at logs following message appeared:
[error] 16488#0: *80 upstream timed out (110: Connection timed out) while connecting to upstream, client: IP, server: , request: "GET /assets/images/transparent.png HTTP/1.1", upstream: "http://host2.example.com:8080/assets/images/transparent.png", host: "hostname", referrer: "http://hostname"
Thanks,Sandeep.

> To: nginx@nginx.org
> Subject: Re: RE: Nginx upstream servers status
> From: nginx-forum@nginx.us
> Date: Wed, 3 Jul 2013 02:39:33 -0400
>
> i'd suggest you'll start with low-level-debugging:
> - goto host1 and make a tcpdump port 8080 / tail -f against access-logs
> of that server;
> - make a request
> - check., what happens to that request, e.g. where it "hangs"
>
> you could also, just in case, make a "tcpdump port 808 and host host2" onm
> your nginx, just to make sure that nginx is sending the requests to the
> right server
>
> Posted at Nginx Forum: http://forum.nginx.org/read.php?2,240513,240523#msg-240523
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://mailman.nginx.org/mailman/listinfo/nginx


_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx _______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Subject Author Posted

Nginx upstream servers status

Sandeep L July 03, 2013 12:56AM

Re: Nginx upstream servers status Attachments

Sajan Parikh July 03, 2013 01:06AM

Re: Nginx upstream servers status

mex July 03, 2013 01:11AM

RE: Nginx upstream servers status

Sandeep L July 03, 2013 01:38AM

Re: Nginx upstream servers status Attachments

Sajan Parikh July 03, 2013 01:48AM

RE: Nginx upstream servers status Attachments

Sandeep L July 03, 2013 01:56AM

Re: RE: Nginx upstream servers status

mex July 03, 2013 02:04AM

RE: Nginx upstream servers status

Sandeep L July 03, 2013 02:12AM

Re: RE: Nginx upstream servers status

mex July 03, 2013 02:39AM

RE: Nginx upstream servers status

Sandeep L July 03, 2013 05:00AM

RE: Nginx upstream servers status

Sandeep L July 04, 2013 01:40AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 74
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready