Re: PGAdmin will not connect - Mailing list pgadmin-support

Sorry it took so long, but I wanted to check a couple of things and read the manual after the results of this test. I
willread the log file when I get off work today, but it looks like I'm not even being given a connection by postmaster. 

> what does your pg_hba.conf say about alowing hosts? Is your host allowed
> to connect to the database?

I believe so, here a copy of the relevant lines:

--- pg_hba.conf ---
local   all         all                                             trust
local   all         all         127.0.0.1     255.255.255.255       trust
host    all         all         127.0.0.1     255.255.255.255       trust
local   all         all         192.168.0.0   255.255.0.0           trust
host    all         all         192.168.0.0   255.255.0.0           trust
--- pg_hba.conf ---

I have modified it to allow everything (I think), so long as it is coming from my internal network.

> telnet localhost 5432 (do you get a 'connected' status (but otherwise
> no good info, for telnet is not psql ;-)) the database accepts socket
> connections)

BINGO!!

That was a hit. It did not allow me to connect. I received an error indicating that I was unable to connect.

I checked a couple of things: I have the "-i" option, and the config file has "tcpip_socket=true". Not sure what to
checkafter that. 



-----Original Message-----
From: Michiel Lange
Sent: Sunday, March 07, 2004 6:11 PM
Subject: Re: [pgadmin-support] PGAdmin will not connect


what does your pg_hba.conf say about alowing hosts? Is your host allowed
to connect to the database?
Read your logfile and see if there's something that gives a clue as to
why it won't allow the host...

Could also have something to do with encryption? is a certain way of
encryption required and could it be that pgAdmin does not support it?
(would give the bad user/password error, but it's worth the try)

If you're not certain where the fault is, try this checklist
On the database machine itself:
- connect to the database locally (if it's ok, the postmaster is running)
- telnet localhost 5432 (do you get a 'connected' status (but otherwise
no good info, for telnet is not psql ;-)) the database accepts socket
connections)
- telnet <your ip> 5432 (same as above, but the postmaster will see you
as from your local IP, and not localhost)
From the client:
- ping <db server> : going OK? Your network is OK
- telnet <dbserver> 5432: going OK? You can reach the postmaster, so
there's no problems with the database...

if all of these tests were succesfull, you should really check your
logfile for clues as to what went wrong.
A linux / unix way of checking out what's going on:
tail -f logfile
<try to connect> and see what new lines appear in the log...

Hope it helps you on your way...
Michiel