BUG #3736: server cannot listen

From: "Derek" <derek(dot)hopkins(at)nisc(dot)coop>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3736: server cannot listen
Date: 2007-11-09 16:18:10
Message-ID: 200711091618.lA9GIACf053022@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 3736
Logged by: Derek
Email address: derek(dot)hopkins(at)nisc(dot)coop
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.

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Jonas Forsman 2007-11-09 16:23:04 BUG #3737: lower/upper fails to match extended chars in LATIN1
Previous Message Peter Eisentraut 2007-11-09 15:53:08 Re: BUG #3735: Can't create xml-stylesheet processing instruction