pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
connection problems
8+ messages / 6 participants
[nested] [flat]

* connection problems
@ 2008-04-01 14:44  Shavonne Marietta Wijesinghe <shavonne.marietta@studioform.it>
  0 siblings, 1 reply; 8+ messages in thread

From: Shavonne Marietta Wijesinghe @ 2008-04-01 14:44 UTC (permalink / raw)
  To: pgsql-admin

Hello

I have my postgresql(ver. 8 ) db on one computer (as localhost) and i'm trying to access it from another computer but i get the error
"could not connect to Server: Connection refused"

I followed the guide and changed the listen_address in the postgresql.conf file 
listen_addresses='*' 

and in the pg_hba.conf file I added the IP address of the pc i'm using
host all all 192.168.X.X/32 trust 

But i get the same error. What should i do??

Thank you,
Shavonne

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: connection problems
@ 2008-04-01 14:56  Tino Schwarze <postgresql@tisc.de>
  parent: Shavonne Marietta Wijesinghe <shavonne.marietta@studioform.it>
  0 siblings, 0 replies; 8+ messages in thread

From: Tino Schwarze @ 2008-04-01 14:56 UTC (permalink / raw)
  To: pgsql-admin

On Tue, Apr 01, 2008 at 04:44:29PM +0200, Shavonne Marietta Wijesinghe wrote:

> I have my postgresql(ver. 8 ) db on one computer (as localhost) and i'm trying to access it from another computer but i get the error
> "could not connect to Server: Connection refused"
> 
> I followed the guide and changed the listen_address in the postgresql.conf file 
> listen_addresses='*' 
> 
> and in the pg_hba.conf file I added the IP address of the pc i'm using
> host all all 192.168.X.X/32 trust 
> 
> But i get the same error. What should i do??

Did you restart the postmaster after setting listen_addresses?
Does netstat -tln display the appropiate port listening on *:5432 (or
whatever your port number is)?

Tino.

-- 
„Es gibt keinen Weg zum Frieden. Der Frieden ist der Weg.” (Mahatma Gandhi)

www.craniosacralzentrum.de
www.forteego.de



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: connection problems
@ 2008-04-01 15:52  Shavonne Marietta Wijesinghe <shavonne.marietta@studioform.it>
  0 siblings, 1 reply; 8+ messages in thread

From: Shavonne Marietta Wijesinghe @ 2008-04-01 15:52 UTC (permalink / raw)
  To: pgsql-admin

Thanks Tino. But what do you mean by "netstat -tln" i use the pgadmin.

Shavonne
 Did you restart the postmaster after setting listen_addresses?
Does netstat -tln display the appropiate port listening on *:5432 (or
whatever your port number is)?

Tino.

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: connection problems
@ 2008-04-01 16:11  Tino Schwarze <postgresql@tisc.de>
  parent: Shavonne Marietta Wijesinghe <shavonne.marietta@studioform.it>
  0 siblings, 0 replies; 8+ messages in thread

From: Tino Schwarze @ 2008-04-01 16:11 UTC (permalink / raw)
  To: pgsql-admin

On Tue, Apr 01, 2008 at 05:52:01PM +0200, Shavonne Marietta Wijesinghe wrote:
> Thanks Tino. But what do you mean by "netstat -tln" i use the pgadmin.

So you're on Windows? You didn't mention any operating system...
What does Postgres say on startup?

Tino.

-- 
„Es gibt keinen Weg zum Frieden. Der Frieden ist der Weg.” (Mahatma Gandhi)

www.craniosacralzentrum.de
www.forteego.de



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: connection problems
@ 2008-04-01 16:29  Melissa Peterson <Melissa@gigacrete.com>
  0 siblings, 1 reply; 8+ messages in thread

From: Melissa Peterson @ 2008-04-01 16:29 UTC (permalink / raw)
  To: pgsql-admin

Netstat is a separate program that shows the status of your network
interfaces. It should come with your operating system. On Windows, you
can get to it via the command console. Typing "netstat -ab" at the
command prompt should generate a list of the ports on which your server
is listening, the ports that have a connection established, and the
program bound to that port. For the port that PostgreSQL is supposed to
be listening on, you can check that it is actually doing so.

 

Mel Peterson

R&D Engineer

melissa@gigacrete.com <mailto:cmelissa@gigacrete.com> 

GigaCrete, Inc.

6775 Speedway Boulevard, Suite M-104

Las Vegas, NV  89115

Phone 702-643-6363

Fax 702-543-7010

www.gigacrete.com <http://www.gigacrete.com/; 

 

B U I L D  S T R O N G.  B U I L D  F O R W A R D.

 

This message and any attachments are solely for the intended recipient
and may contain confidential or privileged information.  If you are not
the intended recipient, any disclosure, copying, use, or distribution of
the information included in this message and any attachments is strictly
prohibited.  If you have received this communication in error, please
notify us by reply email and immediately and permanently delete this
message and any attachments.

________________________________

From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Shavonne Marietta
Wijesinghe
Sent: Tuesday, April 01, 2008 8:52 AM
To: pgsql-admin@postgresql.org
Subject: Re: [ADMIN] connection problems

 

Thanks Tino. But what do you mean by "netstat -tln" i use the pgadmin.

 

Shavonne

	 
	Did you restart the postmaster after setting listen_addresses?
	Does netstat -tln display the appropiate port listening on
*:5432 (or
	whatever your port number is)?
	 
	Tino.

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: connection problems
@ 2008-04-01 17:27  Benjamin Krajmalnik <kraj@illumen.com>
  parent: Melissa Peterson <Melissa@gigacrete.com>
  0 siblings, 0 replies; 8+ messages in thread

From: Benjamin Krajmalnik @ 2008-04-01 17:27 UTC (permalink / raw)
  To: Melissa Peterson <Melissa@gigacrete.com>; pgsql-admin

Another option on Windows would be to get the Sysinternals utilities,
and use tcpview, which is superior to netstat.
 


________________________________

	From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Melissa Peterson
	Sent: Tuesday, April 01, 2008 10:29 AM
	To: pgsql-admin@postgresql.org
	Subject: Re: [ADMIN] connection problems
	
	

	Netstat is a separate program that shows the status of your
network interfaces. It should come with your operating system. On
Windows, you can get to it via the command console. Typing "netstat -ab"
at the command prompt should generate a list of the ports on which your
server is listening, the ports that have a connection established, and
the program bound to that port. For the port that PostgreSQL is supposed
to be listening on, you can check that it is actually doing so.

	 

	Mel Peterson

	R&D Engineer

	melissa@gigacrete.com <mailto:cmelissa@gigacrete.com> 

	GigaCrete, Inc.

	6775 Speedway Boulevard, Suite M-104

	Las Vegas, NV  89115

	Phone 702-643-6363

	Fax 702-543-7010

	www.gigacrete.com <http://www.gigacrete.com/; 

	 

	B U I L D  S T R O N G.  B U I L D  F O R W A R D.

	 

	This message and any attachments are solely for the intended
recipient and may contain confidential or privileged information.  If
you are not the intended recipient, any disclosure, copying, use, or
distribution of the information included in this message and any
attachments is strictly prohibited.  If you have received this
communication in error, please notify us by reply email and immediately
and permanently delete this message and any attachments.

	
________________________________


	From: pgsql-admin-owner@postgresql.org
[mailto:pgsql-admin-owner@postgresql.org] On Behalf Of Shavonne Marietta
Wijesinghe
	Sent: Tuesday, April 01, 2008 8:52 AM
	To: pgsql-admin@postgresql.org
	Subject: Re: [ADMIN] connection problems

	 

	Thanks Tino. But what do you mean by "netstat -tln" i use the
pgadmin.

	 

	Shavonne

		 
		Did you restart the postmaster after setting
listen_addresses?
		Does netstat -tln display the appropiate port listening
on *:5432 (or
		whatever your port number is)?
		 
		Tino.

^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* connection problems
@ 2016-09-22 13:44  Rainer Leo <leo@workfile.de>
  0 siblings, 1 reply; 8+ messages in thread

From: Rainer Leo @ 2016-09-22 13:44 UTC (permalink / raw)
  To: pgsql-admin

Hello guys,

I have trouble with our postgresql installation
on a windows 10 machine. The application which is
working with postgres spontanously looses connection
to the db-server (which runs on the same machine). 
The next moment the connection is up again.

The only interessting entry in the log is

"verwende veraltete Statistiken anstatt aktueller, weil der
Statistiksammelprozess nicht antwortet"

which - I think - means

"using older statitics, because the statistic collector does
not answer"

Does this have anything to do with the connection losses?


Regards,
Rainer Leo

workfile Datenbankservice                   
Bocksberg 20c                                       
D-22395 Hamburg                                

Fon: 040.60 44 90 41
Fax: 040.34 92 61 08
www.workfile.de



-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 8+ messages in thread

* Re: connection problems
@ 2016-09-22 14:17  Tom Lane <tgl@sss.pgh.pa.us>
  parent: Rainer Leo <leo@workfile.de>
  0 siblings, 0 replies; 8+ messages in thread

From: Tom Lane @ 2016-09-22 14:17 UTC (permalink / raw)
  To: Rainer Leo <leo@workfile.de>; +Cc: pgsql-admin

Rainer Leo <leo@workfile.de> writes:
> I have trouble with our postgresql installation
> on a windows 10 machine. The application which is
> working with postgres spontanously looses connection
> to the db-server (which runs on the same machine). 
> The next moment the connection is up again.

> The only interessting entry in the log is
> "verwende veraltete Statistiken anstatt aktueller, weil der
> Statistiksammelprozess nicht antwortet"
> which - I think - means
> "using older statitics, because the statistic collector does
> not answer"

> Does this have anything to do with the connection losses?

Not directly, but both behaviors could be triggered by transient
loss of local TCP connectivity.  I have no idea what would
cause that, but hey, it's Windows :-(.  Maybe something is trying
to reset your network connections?

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin



^ permalink  raw  reply  [nested|flat] 8+ messages in thread


end of thread, other threads:[~2016-09-22 14:17 UTC | newest]

Thread overview: 8+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2008-04-01 14:44 connection problems Shavonne Marietta Wijesinghe <shavonne.marietta@studioform.it>
2008-04-01 14:56 ` Tino Schwarze <postgresql@tisc.de>
2008-04-01 15:52 Re: connection problems Shavonne Marietta Wijesinghe <shavonne.marietta@studioform.it>
2008-04-01 16:11 ` Tino Schwarze <postgresql@tisc.de>
2008-04-01 16:29 Re: connection problems Melissa Peterson <Melissa@gigacrete.com>
2008-04-01 17:27 ` Benjamin Krajmalnik <kraj@illumen.com>
2016-09-22 13:44 connection problems Rainer Leo <leo@workfile.de>
2016-09-22 14:17 ` Tom Lane <tgl@sss.pgh.pa.us>

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox