Talk About Network

Google


Register and Login
Nick
Password
Register create new account Sign up is FREE and you can post replies, new topics, bookmark posts and more!
Recover lost password


Data Bases > Pgsql Interfaces Odbc > [ psqlodbc-Bugs...
Latest [ Topics | Posts ] Archive Post A New Topic Post a Reply
<< Topic < Post Post 1 of 1 Topic 2336 of 2384
Post > Topic >>

[ psqlodbc-Bugs-1010368 ] connection problem with postgresql driver 8.03.0100 to postgresql 8.3.0

by noreply@[EMAIL PROTECTED] Apr 3, 2008 at 05:20 PM

Bugs item #1010368, was opened at 2008-03-31 07:31
You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010368&group_id=1000125

Category: None
Group: None
Status: Open
Resolution: None
Priority: 3
Submitted By: Sebastian Reitenbach (buzzdee)
>Assigned to: Hiro**** Inoue (hinoue)
Summary: connection problem with postgresql driver 8.03.0100 to postgresql
8.3.0

Initial Comment:
I compiled postgres odbc driver version 8.03.0100, but when I try to
connect 
to a 8.3.0 postgres database, then there connection/authentication
problems 
happen: 

isql FIS MyUser MyPassword -v 
[28000][unixODBC]Communication error during authentication; 
Error while reading from the socket. 
[ISQL]ERROR: Could not SQLConnect 
dbuser@[EMAIL PROTECTED]
> isql FIS MyDatabase MyDatabase -v 
+---------------------------------------+ 
| Connected!                            | 
|                                       | 
| sql-statement                         | 
| help [tablename]                      | 
| quit                                  | 
|                                       | 
+---------------------------------------+ 
SQL> 

I can only connect to the database by a chance of 1/10. Also when I get 
connected, then when I try entering a SQL statement, I get error messages 
about not being connected anymore. 

and below the postgres log from the tries: 


 LOG:  connection authorized: user=MyUser database=MyDatabase 
LOG:  unexpected EOF on client connection 
LOG:  disconnection: session time: 0:00:00.002 user=MyUser 
database=MyDatabase 
host=192.168.15.106 ****t=52224 
DEBUG:  server process (PID 19939) exited with exit code 0 
LOG:  connection received: host=192.168.15.106 ****t=52225 
DEBUG:  forked new backend, pid=19941 socket=6 
LOG:  connection authorized: user=MyUser database=MyDatabase 
LOG:  unexpected EOF on client connection 
LOG:  disconnection: session time: 0:00:00.003 user=MyDatabase 
database=MyDatabase 
host=192.168.15.106 ****t=52225 
DEBUG:  server process (PID 19941) exited with exit code 0 
LOG:  connection received: host=192.168.15.106 ****t=52226 
DEBUG:  forked new backend, pid=19943 socket=6 
LOG:  connection authorized: user=MyUser database=MyDatabase 
LOG:  statement: 
LOG:  statement: select version() 
LOG:  statement: set DateStyle to 'ISO' 
LOG:  statement: set geqo to 'OFF' 
LOG:  statement: set extra_float_digits to 2 
LOG:  statement: select oid, typbasetype from pg_type where typname = 'lo'

LOG:  statement: select pg_client_encoding() 
ERROR:  synt x error at or near " at character 1 
LOG:  could not send data to client: Broken pipe 
LOG:  unexpected EOF on client connection 

This is the part of the configuration from my odbc.ini: 
[FIS] 
Description             = PostgreSQL DB 
Driver                  = PostgreSQL 
commlog = yes 
Database                = MyDatabase 
Host       = localhost 
Server     = localhost 
ServerName = pdtest106.pdtest.intern 
Username                = MyUser 
Password                = MyPassword 
****t                    = 5430 
Protocol                = 6.4 
ReadOnly                = No 
RowVersioning           = No 
ShowSystemTables        = No 
ShowOidColumn           = No 
FakeOidIndex            = No 
ConnSettings            = 

Actually, I have no idea, what the protocol version number means. The 
version 6.4 was the one I found most of the time in the net. I also tried
to 
set it to 8.3, and 8.3.0, but with no difference. Any pointer to an 
explanation would be great. 

when I exchange the odbc driver file, with an older one, odbc drvier
version 
8.1.2, then I do not have connection/login problems at all. 

----------------------------------------------------------------------

>Comment By: Hiro**** Inoue (hinoue)
Date: 2008-04-03 17:20

Message:
Please try the second patch.

regards,
Hiro**** Inoue

----------------------------------------------------------------------

Comment By: Sebastian Reitenbach (buzzdee)
Date: 2008-04-02 10:21

Message:
I just retried to compile against postgresql 8.3.1, but 
with the same result. Note, for the test I did not used 
your patch.

----------------------------------------------------------------------

Comment By: Sebastian Reitenbach (buzzdee)
Date: 2008-04-02 08:40

Message:
Forgot to mention, I compiled with and 
without --disable-unicode --disable-openssl
but both versions show the same results.

----------------------------------------------------------------------

Comment By: Sebastian Reitenbach (buzzdee)
Date: 2008-04-02 08:32

Message:
Thanks for the patch, I just tested. It did not apply 
cleanly: 
/usr/local/src/psqlodbc-08.03.0100 # patch -p0 
< ../psqlodbc.patch
patching file ./socket.c
Hunk #1 succeeded at 347 (offset -6 lines).
Hunk #2 FAILED at 519.
Hunk #3 FAILED at 529.
Hunk #4 succeeded at 811 (offset -6 lines).
Hunk #5 succeeded at 868 (offset -6 lines).
Hunk #6 succeeded at 947 (offset -6 lines).
2 out of 6 hunks FAILED -- saving rejects to 
file ./socket.c.rej

However, after taking a look into the source and the patch 
file, I changed the section to look like this:

#ifdef USE_SSL
/*
 *      The stuff for SSL.
 */
/* included in  <openssl/ssl.h> */
#define SSL_ERROR_NONE                  0
#define SSL_ERROR_SSL                   1
#define SSL_ERROR_WANT_READ             2
#define SSL_ERROR_WANT_WRITE            3
#define SSL_ERROR_WANT_X509_LOOKUP      4
#define SSL_ERROR_SYSCALL               5 // look at error 
stack/return value/errno
#define SSL_ERROR_ZERO_RETURN           6
#define SSL_ERROR_WANT_CONNECT          7
#define SSL_ERROR_WANT_ACCEPT           8
// */

However, the patch did not helped.
I still get these error messages:

isql MyDatabase -v
[28000][unixODBC]Communication error during 
authentication;
Error while reading from the socket.
[ISQL]ERROR: Could not SQLConnect


The mylog_root21305.log is from above message.


isql MyDatabase -v
[S1000][unixODBC]The database does not exist on the server
or user authentication failed.
[ISQL]ERROR: Could not SQLConnect

The mylog_root21305.log is from above message.


----------------------------------------------------------------------

Comment By: Hiro**** Inoue (hinoue)
Date: 2008-04-01 15:53

Message:
Please try the attached patch.

----------------------------------------------------------------------

Comment By: Hiro**** Inoue (hinoue)
Date: 2008-03-31 10:23

Message:
Could you attach the Mylog output ?
You will be able to take the log (/tmp/mylog_xxxx.log) by adding the line
Debug = 1
to your odbc.ini. 

regards,
Hiro**** Inoue


----------------------------------------------------------------------

You can respond by visiting: 
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1010368&group_id=1000125

-- 
Sent via pgsql-odbc mailing list (pgsql-odbc@[EMAIL PROTECTED]
)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-odbc
 




 1 Posts in Topic:
[ psqlodbc-Bugs-1010368 ] connection problem with postgresql dri
noreply@[EMAIL PROTECTED]  2008-04-03 17:20:30 

Post A Reply:
  Go here to Signup

AddThis Feed Button


About - Advertising - Contact - Frequently Asked Questions - Privacy Policy - Terms of Use - Signup

Contact
tan13V112 Thu Jul 24 1:45:53 CDT 2008.