| From: | Jackson Pauls <j(at)uklinux(dot)net> | 
|---|---|
| To: | pgsql-general(at)postgresql(dot)org | 
| Subject: | Re: connecting with a 8.0.0 client with ssl | 
| Date: | 2005-01-21 16:39:32 | 
| Message-ID: | 1106325572.7459.40.camel@localhost.localdomain | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgsql-general | 
On Thu, 2005-01-20 at 17:42 +0000, Jackson Pauls wrote:
> On Thu, 2005-01-20 at 14:14 +0000, Jackson Pauls wrote:
> 
> > i'm trying to create a connection from a postgres 8.0.0 client to a
> > remote server running postgres 7.4.6 that requires ssl.
> > 
> > this connection worked on the client machine when connecting using a
> > 7.4.6 postgres client, and still works when connecting from a 3rd
> > machine with 7.4.6. so i think that narrows it down to some change in
> > the new postgres 8.0.0 client.
> > 
> > client was configured with ./configure --with-openssl.
> > 
> > psql (lack of) output:
> > 
> > $ psql -U user -h remoteIP db
> > psql: [j(at)localhost]$
> > 
> > php output:
> > 
> > Warning: pg_connect() [function.pg-connect]: Unable to connect to
> > PostgreSQL server: in ...
> > 
> > for each failed connection, the server log contains the line:
> > 
> > LOG:  could not initialize SSL connection: No SSL error reported
> > 
> > there is no root.crt file on the server, and no certificates present on
> > the client.
> > 
> > server tuns fedora core 1, openssl-0.9.7a-33.10 (rpm), client runs
> > fedora core 3, openssl-0.9.7a-40 (rpm).
> 
> ... adding to my own post. i just noticed errors aren't being reported
> in psql in the 8.0.0 client (connected to a local 8.0.0 server):
> 
> db=> select 'a' + 1;
> db=>
> 
> but do appear in the local server log: 'ERROR:  invalid input syntax for
> integer: "a"'
> 
> i'm using the default settings for error reporting and logging. 
> 
> is there is a way to reinstate error messages in psql? it might be
> trying to tell me something useful when i'm trying to connect to the
> remote server.
fixed all the above: i didn't realise i needed to "make clean" when
reconfiguring postgres to include openssl support. and now i can see
error messages in psql again as well.
j
-- 
Play Alienballs at www.j.uklinux.net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruno Wolff III | 2005-01-21 16:52:37 | Re: Multiline plpython procedure | 
| Previous Message | Greg Stark | 2005-01-21 16:37:15 | Re: Restoring fscked up postgres 7.1 |