From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Casey, J Bart" <CaseyJB(at)wofford(dot)edu> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Problem Connecting to 5432 |
Date: | 2006-06-14 14:18:46 |
Message-ID: | 23570.1150294726@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
"Casey, J Bart" <CaseyJB(at)wofford(dot)edu> writes:
> I have read message after message and searched the internet for hours,
> yet I still can't get a remote computer to connect to port 5432 on my
> Fedora Core 3 system running Postgresql 7.4.7.
You need to restart (not just SIGHUP) the postmaster to get it to accept
the tcpip_socket flag. If you don't see it listening in netstat then
my first guess is you forgot that step. If it's not apparent what's
happening then you need to look at the postmaster's log output ... which
I think the default configuration in FC3 will deliver to /dev/null :-(
You could tweak the initscript to change that, or start the postmaster
"by hand" from a terminal window to see if it prints any useful messages.
Once you see that it's listening, try "psql -h localhost ..." to see if
a TCP connection actually works. I am not sure that it will work by
default --- I think that the default iptables firewall configuration on
FC3 disallows connections to 5432. (Even if they're allowed on local
loopback, they're very likely not allowed remotely.) So fixing the
iptables configuration will be your second hurdle.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Casey, J Bart | 2006-06-14 14:48:32 | Re: Problem Connecting to 5432 |
Previous Message | Tom Lane | 2006-06-14 13:56:55 | Re: Partitioning... |