Have you checked your PostgreSQL configuration? Have you checked
your firewall? Did you read the last line of the text you posted,
where it says "Please check this thoroughly before reporting a bug to
the PostgreSQL community" ?
I give kudos to the support team for being very tolerant and
patient. Please don't blame them for my saying this is probably a
system configuration error, and if you had bothered to read the
message, or the installation guide, you would not be reporting a bug.
On Nov 9, 2007, at 4:18 PM, Derek wrote:
The following bug has been logged online:
Bug reference: 3736
Logged by: Derek
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1.10
Operating system: Windows XP Professional
Description: server cannot listen
Details:
when i try to connect to the postgreSQL database i get this error
message:
Server doesn't listen
The server doesn't accept connections: the connection library reports
could not connect to server: Connection refused (0x0000274D/10061)
Is the
server running on host "127.0.0.1" and accepting TCP/IP connections
on port
5432?
If you encounter this message, please check if the server you're
trying to
contact is actually running PostgreSQL on the given port. Test if
you have
network connectivity from your client to the server host using ping or
equivalent tools. Is your network / VPN / SSH tunnel / firewall
configured
correctly?
For security reasons, PostgreSQL does not listen on all available IP
addresses on the server machine initially. In order to access the
server
over the network, you need to enable listening on the address first.
For PostgreSQL servers starting with version 8.0, this is
controlled using
the "listen_addresses" parameter in the postgresql.conf file. Here,
you can
enter a list of IP addresses the server should listen on, or simply
use '*'
to listen on all available IP addresses. For earlier servers
(Version 7.3 or
7.4), you'll need to set the "tcpip_socket" parameter to 'true'.
You can use the postgresql.conf editor that is built into pgAdmin
III to
edit the postgresql.conf configuration file. After changing this
file, you
need to restart the server process to make the setting effective.
If you double-checked your configuration but still get this error
message,
it's still unlikely that you encounter a fatal PostgreSQL
misbehaviour. You
probably have some low level network connectivity problems (e.g.
firewall
configuration). Please check this thoroughly before reporting a bug
to the
PostgreSQL community.
---------------------------(end of
broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
Douglas Toltzman
[EMAIL PROTECTED]
(910) 526-5938
