pg.ddx.io pgsql-interfaces@postgresql.org mailing list archive
help / color / mirror / Atom feedRe: AWL: postgres odbc woes, continued .......
5+ messages / 2 participants
[nested] [flat]
* Re: AWL: postgres odbc woes, continued .......
@ 1999-01-15 02:26 Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 14:23 ` Re: AWL: postgres odbc woes, continued ....... Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 5+ messages in thread
From: Thomas G. Lockhart @ 1999-01-15 02:26 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
> Any thoughts would be greatly appreciated.
I'm having trouble running the development tree version of psqlODBC.
Picking up the odbc source code from the v6.4 Postgres tarball and
inserting it into src/interfaces/odbc gives me back a driver which seems
to work.
Byron, do you have any ideas on what might have changed? I vaguely
recall that the newest code is using v6.4 protocol, and the v6.4 tarball
code was using the v6.3.2 protocol?? I've enclosed my log files.
TIA
- Tom
Attachments:
mylog_tgl2539.log (text/plain, 665B) download
globals.extra_systable_prefixes = 'dd_;'
CC_connect: entering...
CC_connect(): DSN = 'Test', server = 'localhost', port = '', database = 'test', username = 'tgl', password='no$way'
connecting to the server socket...
connection to the server socket failed.
CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server'
**** SQLError: henv=0, hdbc=134613032, hstmt=0
calling CC_get_error
enter CC_get_error
enter CC_create_errormsg
msg = 'Could not connect to the server'
exit CC_create_errormsg
exit CC_get_error
CC_get_error: status = 101, msg = #Could not connect to the server;
Could not connect to remote socket.#
psqlodbc_tgl2539.log (text/plain, 1.2K) download
DSN info: DSN='Test',server='localhost',port='5432',dbase='test',user='tgl',passwd='no$way'
readonly='0',protocol='',showoid='',fakeoidindex='',showsystable=''
conn_settings=''
translation_dll='',translation_option=''
conn = 134613032, SQLConnect(DSN='Test', UID='tgl', PWD='no$way')
Global Options: Version='06.40.0002', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
text_as_longvarchar=0, unknowns_as_longvarchar=0, bools_as_char=1
extra_systable_prefixes='dd_;', conn_settings=''
CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server'
------------------------------------------------------------
henv=134613016, conn=134613032, status=0, num_stmts=16
sock=134619360, stmts=134627608, lobj_type=-999
---------------- Socket Info -------------------------------
socket=-1, reverse=0, errornumber=4, errormsg='Could not connect to remote socket.'
buffer_in=134619400, buffer_out=134623504
buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0
* Re: AWL: postgres odbc woes, continued .......
1999-01-15 02:26 Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
@ 1999-01-15 14:23 ` Byron Nikolaidis <byronn@insightdist.com>
1999-01-15 15:22 ` Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 1 reply; 5+ messages in thread
From: Byron Nikolaidis @ 1999-01-15 14:23 UTC (permalink / raw)
To: Thomas G. Lockhart <lockhart@alumni.caltech.edu>; +Cc: pgsql-interfaces
Thomas G. Lockhart wrote:
> > Any thoughts would be greatly appreciated.
>
> I'm having trouble running the development tree version of psqlODBC.
> Picking up the odbc source code from the v6.4 Postgres tarball and
> inserting it into src/interfaces/odbc gives me back a driver which seems
> to work.
>
> Byron, do you have any ideas on what might have changed? I vaguely
> recall that the newest code is using v6.4 protocol, and the v6.4 tarball
> code was using the v6.3.2 protocol?? I've enclosed my log files.
>
> TIA
>
> - Tom
>
> ------------------------------------------------------------------------
> globals.extra_systable_prefixes = 'dd_;'
> CC_connect: entering...
> CC_connect(): DSN = 'Test', server = 'localhost', port = '', database = 'test', username = 'tgl', password='no$way'
> connecting to the server socket...
> connection to the server socket failed.
> CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server'
> **** SQLError: henv=0, hdbc=134613032, hstmt=0
> calling CC_get_error
> enter CC_get_error
> enter CC_create_errormsg
> msg = 'Could not connect to the server'
> exit CC_create_errormsg
> exit CC_get_error
> CC_get_error: status = 101, msg = #Could not connect to the server;
> Could not connect to remote socket.#
>
> ------------------------------------------------------------------------
> DSN info: DSN='Test',server='localhost',port='5432',dbase='test',user='tgl',passwd='no$way'
> readonly='0',protocol='',showoid='',fakeoidindex='',showsystable=''
> conn_settings=''
> translation_dll='',translation_option=''
> conn = 134613032, SQLConnect(DSN='Test', UID='tgl', PWD='no$way')
> Global Options: Version='06.40.0002', fetch=100, socket=4096, unknown_sizes=0, max_varchar_size=254, max_longvarchar_size=4094
> disable_optimizer=1, ksqo=1, unique_index=0, use_declarefetch=0
> text_as_longvarchar=0, unknowns_as_longvarchar=0, bools_as_char=1
> extra_systable_prefixes='dd_;', conn_settings=''
> CONN ERROR: func=SQLConnect, desc='Error on CC_connect', errnum=101, errmsg='Could not connect to the server'
> ------------------------------------------------------------
> henv=134613016, conn=134613032, status=0, num_stmts=16
> sock=134619360, stmts=134627608, lobj_type=-999
> ---------------- Socket Info -------------------------------
> socket=-1, reverse=0, errornumber=4, errormsg='Could not connect to remote socket.'
> buffer_in=134619400, buffer_out=134623504
> buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0
This is a physical socket connection problem. The Socket Info (above) shows errornumber=4, which is a failure in the connect()
system call. At this point in communications, protocol has not have come into play yet.
I would suggest checking to see if the postmaster is running with -i, and can connect from the machine, and all that network jazz.
Byron
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: AWL: postgres odbc woes, continued .......
1999-01-15 02:26 Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 14:23 ` Re: AWL: postgres odbc woes, continued ....... Byron Nikolaidis <byronn@insightdist.com>
@ 1999-01-15 15:22 ` Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 15:44 ` Re: AWL: postgres odbc woes, continued ....... Byron Nikolaidis <byronn@insightdist.com>
0 siblings, 1 reply; 5+ messages in thread
From: Thomas G. Lockhart @ 1999-01-15 15:22 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
> This is a physical socket connection problem. The Socket Info (above)
> shows errornumber=4, which is a failure in the connect()
> system call. At this point in communications, protocol has not have
> come into play yet.
> I would suggest checking to see if the postmaster is running with -i,
> and can connect from the machine, and all that network jazz.
I copied the older version's source code to the new tree and it worked
fine. No other changes, and I left postmaster running in between these
tests.
Are there any things to look at that a successful psql would not be
testing? I've also tried psql -h localhost...
- Tom
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: AWL: postgres odbc woes, continued .......
1999-01-15 02:26 Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 14:23 ` Re: AWL: postgres odbc woes, continued ....... Byron Nikolaidis <byronn@insightdist.com>
1999-01-15 15:22 ` Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
@ 1999-01-15 15:44 ` Byron Nikolaidis <byronn@insightdist.com>
1999-01-20 02:23 ` Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 1 reply; 5+ messages in thread
From: Byron Nikolaidis @ 1999-01-15 15:44 UTC (permalink / raw)
To: Thomas G. Lockhart <lockhart@alumni.caltech.edu>; +Cc: pgsql-interfaces
Thomas G. Lockhart wrote:
> > This is a physical socket connection problem. The Socket Info (above)
> > shows errornumber=4, which is a failure in the connect()
> > system call. At this point in communications, protocol has not have
> > come into play yet.
> > I would suggest checking to see if the postmaster is running with -i,
> > and can connect from the machine, and all that network jazz.
>
> I copied the older version's source code to the new tree and it worked
> fine. No other changes, and I left postmaster running in between these
> tests.
>
I was looking at the logfile again, and this might explain it. Notice the
port has some junk in it. That would make the connect() call fail
alright.CC_connect(): DSN = 'Test', server = 'localhost', port = '',
database = 'test', username= 'tgl', password='no$way'
I'm not sure why the port has that stuff. It could be a bug, but check your
odbcinst.ini and odbc.ini files for anything weird.
Byron
^ permalink raw reply [nested|flat] 5+ messages in thread
* Re: AWL: postgres odbc woes, continued .......
1999-01-15 02:26 Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 14:23 ` Re: AWL: postgres odbc woes, continued ....... Byron Nikolaidis <byronn@insightdist.com>
1999-01-15 15:22 ` Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 15:44 ` Re: AWL: postgres odbc woes, continued ....... Byron Nikolaidis <byronn@insightdist.com>
@ 1999-01-20 02:23 ` Thomas G. Lockhart <lockhart@alumni.caltech.edu>
0 siblings, 0 replies; 5+ messages in thread
From: Thomas G. Lockhart @ 1999-01-20 02:23 UTC (permalink / raw)
To: Byron Nikolaidis <byronn@insightdist.com>; +Cc: pgsql-interfaces
> > > This is a physical socket connection problem.
*sigh* I sat down to debug this, and can not reproduce the problem. I
hate computers... ;)
I had just replaced the psqlodbc standalone tar file on postgresql.org
with the older v6.4 version. Will upgrade it back to the newer version.
- Tom
^ permalink raw reply [nested|flat] 5+ messages in thread
end of thread, other threads:[~1999-01-20 02:23 UTC | newest]
Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-01-15 02:26 Re: AWL: postgres odbc woes, continued ....... Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 14:23 ` Byron Nikolaidis <byronn@insightdist.com>
1999-01-15 15:22 ` Thomas G. Lockhart <lockhart@alumni.caltech.edu>
1999-01-15 15:44 ` Byron Nikolaidis <byronn@insightdist.com>
1999-01-20 02:23 ` Thomas G. Lockhart <lockhart@alumni.caltech.edu>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox