Re: client connection problem

From: Rasmus Mohr <rmo(at)Netpointers(dot)com>
To: "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>
Subject: Re: client connection problem
Date: 2002-01-17 10:35:14
Message-ID: 910513A5A944D5118BE900C04F67CB5A0BFD03@MAIL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-admin

Bullseye! Packet filtering was the problem, and was solved by allowing
packets destined to port 5432 in ipchains.

thanx a lot!

-----Oprindelig meddelelse-----
Fra: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org]På vegne af Tom Lane
Sendt: 16. januar 2002 16:52
Til: nickf(at)ontko(dot)com
Cc: Rasmus Mohr; pgsql-admin(at)postgresql(dot)org
Emne: Re: [ADMIN] client connection problem

"Nick Fankhauser" <nickf(at)ontko(dot)com> writes:
> Try adding a line to pg_hba.conf for localhost specifically- I'd guess
that
> the request is coming in with that address rather than the local machine's
> IP address.

Another possibility is that the connection request is being dropped on
the floor by kernel packet filtering. The default filtering in RH 7.2
is pretty aggressive (just the other day I had to change quite a few
things to get it to allow incoming and outgoing NFS, for example).
Check your ipchains setup in /etc/sysconfig/ipchains.

IIRC, the default ipchains setup does *not* filter localhost
connections, but I think it would apply to connections showing a source
address of your Ethernet IP.

regards, tom lane

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo(at)postgresql(dot)org

Browse pgsql-admin by date

  From Date Subject
Next Message omid omoomi 2002-01-17 14:08:41 Re: finding file names
Previous Message Jean-Michel POURE 2002-01-17 09:06:41 CREATE OR REPLACE VIEW / TRIGGER