Lots of "No route to host" in Nginx error log

xufengnju xufengnju at sina.com
Wed Jan 6 05:04:42 MSK 2010

Hi All,

We got lots of "No route to host" in Nginx error log.
2010/01/05 22:28:01 [error] 29366#0: *26063920 connect() failed (113: No route to host) while connecting to upstream, client:, server: test.com, request: GET /herundong/index.php HTTP/1.1, upstream: http://x.y.z.a:80/herundong/index.php, host: events.test.com  ' 
Using curl on the Nginx proxy server like 
curl -v -H "Host: events.test.com" http://x.y.z.a/herundong/index.php 
works as expected.
I searched in Nginx source code, and find even no 'No route to host' in its source code.

Nginx version: 0.7.63
Backend are Apache servers.

Current Nginx connections ~2k;
Current Apache Connections ~800(counting all active and inactive connections)
I saw on some connections of apache, there was a high Send-Q on established nginx-apache connections.
Current Apache load average is under 1;

Any suggestions?

Thanks in advance.


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20100106/53f2f0a3/attachment.html>

More information about the nginx mailing list