Connect() failed (113: No route to host)

Hi,

I’ve seen lots of errors like “connect() failed (113: No route to host)
while connecting to upstream” in the nginx error log. The upstream
server is a Tomcat sitting behind nginx. I’ve checked the tomcat status
and it seems to be running OK with only about 1/3 of the max allowed
threads are being used. Any idea what could be the cause here?

Thanks!
Michael

Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,7903,7903#msg-7903

On Sun, Sep 20, 2009 at 04:36:10AM -0400, gogobu wrote:

Hi,

I’ve seen lots of errors like “connect() failed (113: No route to host) while connecting to upstream” in the nginx error log. The upstream server is a Tomcat sitting behind nginx. I’ve checked the tomcat status and it seems to be running OK with only about 1/3 of the max allowed threads are being used. Any idea what could be the cause here?

Probably, this is network issues between hosts where nginx and Tomcat
are running.

Since tomcat and nginx are both running in the same intranet, I doubt
it’s network problem…

Just a wild guess, I’m running linux kernel 2.6.18, is there some kind
of sysctl settings I need to tune a bit?

Thanks,
Michael

Igor S. Wrote:

running OK with only about 1/3 of the max allowed
http://sysoev.ru/en/
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,7903,8062#msg-8062

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs