| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | mad_mac(at)madasafish(dot)com |
| Cc: | pgsql-novice(at)postgresql(dot)org |
| Subject: | Re: Starting ProgreSQL server |
| Date: | 2004-07-22 18:13:52 |
| Message-ID: | 10954.1090520032@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-novice |
"Richard Watt" <warren_tf_mcarthur(at)hotmail(dot)com> writes:
> I tried to create a test database with createdb, and this is the message I get:
>
> createdb: could not connect to database template1: could not connect to server: Connection refused
> Is the server running on host <IP address> and accepting
> TCP/IP connections on port 5321?
Double check that the postmaster is really listening to 5321 and not
some other port ("netstat -l -n --inet" is a good way). It seems
possible there's a stray PGPORT setting somewhere you didn't notice.
If that's not it, I'd guess that the kernel's ipfilter rules are set to
reject traffic to 5321. You'll need to punch a hole in the firewall
rules.
In any case, "connection refused" is a kernel-level failure message;
your connection request did not get delivered to the postmaster at all.
So you should be looking at generic communications problems rather
than Postgres-specific ideas.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Si Chen | 2004-07-22 19:16:38 | how to find transaction associated with a lock |
| Previous Message | Hari Bhanujan | 2004-07-22 17:18:05 | Re: Starting ProgreSQL server |