Re: PostgreSQL client not connecting - SOLVED
Well, I went once again through it, and, hm.., I'm little bit ashamed to
say that, but the problem was that my machine has no local loopback
enabled. It somehow disappeared during transition to
/etc/network/interfaces. So, that's it. Thanks.
Radim
On Mon, 28 Feb 2000, Oliver Elphick wrote:
> Radim Gelner wrote:
> >
> >I have 128 buffers defined in postmaster.init. But maybe the problem is
> >not related to PostgreSQL at all, because I've found out, that I got the
> >same error (neighbour table overflow) when I try telnetting on the port.
> >And also, this is, as log states, a kernel error, not an error from psql.
> >Psql is only not able to connect, and asks about postmaster running. But
> >the problem seems to be at a network level. Strange is, that my
> >instalation is a plain new Slink install apt-distupdated to Potato. I did
> >not change even a line in configuration of a system nor recompiled the
> >kernel. At debian-user mailing list is none complaining about this, so
> >that it seems, it's just me experiencing this.
>
> Yes, the error message occurs in the kernel's routing code
> (net/ipv4/route.c). Your route cache is full and cannot be shrunk.
> As for why ... try the kernel mailing lists.
>
> --
> Oliver Elphick Oliver.Elphick@lfix.co.uk
> Isle of Wight http://www.lfix.co.uk/oliver
> PGP key from public servers; key ID 32B8FAA1
> ========================================
> "These things have I written unto you that believe on
> the name of the Son of God; that ye may know that ye
> have eternal life, and that ye may believe on the name
> of the Son of God." I John 5:13
>
>
Reply to: