Welcome! Log In Create A New Profile

Advanced

Re: connect() failed (113: No route to host)

September 21, 2009 03:10AM
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 Sysoev Wrote:
-------------------------------------------------------
> 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.
>
>
> --
> Igor Sysoev
> http://sysoev.ru/en/
Subject Author Posted

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

gogobu September 20, 2009 04:36AM

Re: connect() failed (113: No route to host)

Igor Sysoev September 20, 2009 06:34AM

Re: connect() failed (113: No route to host)

gogobu September 21, 2009 03:10AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 294
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