Re: 8.0 Beta3 worked, RC1 didn't!

The SSL line in postgresql.conf has not been touched. By default it should
be set to false. Also, the pg_hba file is set to allow all clients in, no
authentication (TRUST).

I have not seen this problem in any other installation. Note as well, the
only way to access the server in question is via a remote connection (Remote
Administrator). I do remember, however, that even before attempting remote
connections to the database, the same error message would also occur
'locally' (through remote administrator, but I don't see how this interface
would factor into the problem.

I can't see how this would be a result of a configuration setting. If I
install RC1 and attempt a connection locally (before modifying any configs)
it fails with the aforementioned error message. Uninstall RC1 and install
beta 3 and it works (this is repeatable).

One more thing...I may be wrong on this one because I was not paying
attention as well as I should have, but I seem to remember that following
one of my RC1 installation attempts, I was able to log into psql locally,
but only once. After that I was denied every time. Again, I *think* this
is what happened!

Thanks,
Peter

-----Original Message-----
From: Joshua D. Drake [mailto:jd(at)commandprompt(dot)com]
Sent: December 21, 2004 8:06 PM
To: A. Mous
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] 8.0 Beta3 worked, RC1 didn't!

A. Mous wrote:

>Hi all,
>
>I'm using psql 8.0.0 on a client's site who's running win server 2003.
>We've had him on beta 3 for some time, and no problems at all (yes, in a
>sense, he is a beta tester as well, but doesn't know it!). Today I tried
to
>upgrade the db to RC1 and had some problems.
>
>Remote clients connect to this database, so I have to set listen_addresses
=
>'*' in the posrgresql.conf file. This is the only change to the config
>file. Doing this with RC1 and trying to connect locally with through psql
>resulted in the following error message:
>
>"could not receive server response to SSL negotiation packet; connection
>reset by peer (0x00002746/10054)"
>
>

The clients connecting remotely... do they support SSL? It looks
like to me that you have ssl enabled. I would check the pg_hba.conf
and the postgresql.conf for your ssl configuration.

Sincerely,

Joshua D. Drake

>Removing the modified line in the config file resolved the problem
>(locally), however, no clients can connect! Beta 3 does not seem to have
>this issue, so we had to revert back to it for now.
>
>I would appreciate any ideas that some of you may have. Much thanks,
>
>-Peter
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
>
>

--
Command Prompt, Inc., home of Mammoth PostgreSQL - S/ODBC and S/JDBC
Postgresql support, programming shared hosting and dedicated hosting.
+1-503-667-4564 - jd(at)commandprompt(dot)com - http://www.commandprompt.com
PostgreSQL Replicator -- production quality replication for PostgreSQL