Skip site navigation (1) Skip section navigation (2)

BUG #5936: Cannot connect to Server

From: "Srikanth" <sri_seshu(at)yahoo(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5936: Cannot connect to Server
Date: 2011-03-19 05:56:21
Message-ID: 201103190556.p2J5uLf1027030@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      5936
Logged by:          Srikanth
Email address:      sri_seshu(at)yahoo(dot)com
PostgreSQL version: 1.8.2
Operating system:   Windows Vista Business
Description:        Cannot connect to Server
Details: 

It was working till 4 days back and suddenly gave the below message.Please
tell me what do do

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

pgsql-bugs by date

Next:From: tomasDate: 2011-03-19 21:17:43
Subject: Re: BUG #5936: Cannot connect to Server
Previous:From: Robert HaasDate: 2011-03-19 02:12:58
Subject: Re: Problem with ALTER TABLE - occasional "tuple concurrently updated"

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group