Re: Server starts, but I can't connect

Tom,

Thanks for replying.

Here is the log:
2011-07-05 22:58:22 CDT LOG: database system is ready to accept connections
2011-07-05 22:58:22 CDT LOG: autovacuum launcher started
2011-07-05 22:59:33 CDT LOG: could not receive data from client:
Connection reset by peer
2011-07-05 22:59:41 CDT FATAL: password authentication failed for user
"postgres"
2011-07-05 22:59:41 CDT FATAL: password authentication failed for user
"postgres"
2011-07-05 23:02:00 CDT LOG: could not receive data from client:
Connection reset by peer
2011-07-05 23:02:01 CDT LOG: could not receive data from client:
Connection reset by peer
2011-07-05 23:04:32 CDT LOG: could not receive data from client:
Connection reset by peer

Here is the main part of my pg_hba.conf file:
# Database administrative login by UNIX sockets
local all postgres trust
#local all postgres ident --wcb
original line

# TYPE DATABASE USER CIDR-ADDRESS METHOD

# "local" is for Unix domain socket connections only
local all all trust
# method above WAS ident --wcb
# IPv4 local connections:
host all all 127.0.0.1/32 md5
# IPv6 local connections:
host all all ::1/128 md5

I did a "find / -name pg_hba.conf" and this was the only file that was
found.

Based on what you are saying and the log file I have set up my
pg_hba.conf file incorrectly.

Any idea where I have gone awry?

Thanks,

Craigbert

On 07/05/2011 10:11 PM, Tom Lane wrote:
> Craigbert<postgresql(at)mysoftforge(dot)com> writes:
>> Hello All,
>> I am running PostgreSQL 8.4 on Kubuntu 11.04.
>> The server starts without any issues, but I can not connect. I keep
>> getting an invalid user/password error.
>> I am connecting to the localhost, default port, user = postgres,
>> database = postgres
>> I have tried setting the authentication methods to trust in the
>> pg_hba.conf file, but it does not make any difference.
>> What am I doing wrong?
> You could not get that type of error when running "trust"
> authentication. So, you aren't. Likely theories are that you forgot to
> reload or restart the server after changing pg_hba.conf, or that you did
> reload but it didn't "take" because of some error in the modified hba
> file (if so, there'll be some complaint about it in the server log
> file), or that the file you're changing isn't the one being used by the
> server you're actually connecting to.
>
> regards, tom lane
>