Re: LOG: unexpected EOF on client connection - Mailing list pgsql-odbc
From | Iain |
---|---|
Subject | Re: LOG: unexpected EOF on client connection |
Date | |
Msg-id | 003401c421be$42c50ed0$7201a8c0@mst1x5r347kymb Whole thread Raw |
In response to | LOG: unexpected EOF on client connection (Chris Gamache <cgg007@yahoo.com>) |
List | pgsql-odbc |
Hi Chris, Sorry, I forgot to cc the list last time. It was definitely client side. I'll check for you. regards Iain ----- Original Message ----- From: "Chris Gamache" <cgg007@yahoo.com> To: "Iain" <iain@mst.co.jp> Sent: Wednesday, April 14, 2004 3:09 AM Subject: Re: [ODBC] LOG: unexpected EOF on client connection > > That sounds like it is what's happening here... It started happening after we > upgraded to the latest stable version of the driver. Could you dig up the > details on which setting you increased? Was it server-side or client-side? > > CG > > --- Iain <iain@mst.co.jp> wrote: > > Hi, > > > > I may be way off here, but this looks like something we encountered after > > upgrading to the new ODBC driver. > > > > The old version ignored some timeout setting, so the application never used > > it, but after upgrading to the later driver this (I think it was) error > > started appearing. If it's the same one we had, we fixed it by increasing a > > timeout value. That's not a DB lock timeout, it's something to do with the > > connection. I wasn't directly involved with that system, but maybe I can get > > the details for you if you cant work it out. > > > > Regards > > Iain > > ----- Original Message ----- > > From: "Chris Gamache" <cgg007@yahoo.com> > > To: <pgsql-odbc@postgresql.org> > > Sent: Tuesday, April 13, 2004 5:33 AM > > Subject: [ODBC] LOG: unexpected EOF on client connection > > > > > > > I'm still getting this message at every ODBC connection. I think that > > there > > > might be a problem. I am having issues with ODBC connections being > > terminated > > > without a disconnect issued. This isn't due to script error or to the > > script > > > terminating. PostgreSQL's log reads: > > > > > > LOG: could not receive data from client: Connection reset by peer > > > LOG: unexpected EOF on client connection > > > > > > I would love to track down the reason for the disconnects. > > > > > > Any assistance in this matter would be greatly appreciated. Thank you! > > > > > > conn=48183040, PGAPI_DriverConnect( > > > > > in)='DRIVER={PostgreSQL};UID=adduser;PWD=xxxxx;DATABASE=xxxxx;SERVER=xxx.xxx > > .xxx.xxx;PORT=5432;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=1;RO > > WVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS=;', > > > fDriverCompletion=0 > > > Global Options: Version='07.03.0200', fetch=100, socket=4096, > > unknown_sizes=0, > > > max_varchar_size=254, max_longvarchar_size=8190 > > > disable_optimizer=1, ksqo=1, unique_index=1, > > use_declarefetch=0 > > > text_as_longvarchar=1, unknowns_as_longvarchar=0, > > > bools_as_char=1 NAMEDATALEN=64 > > > extra_systable_prefixes='dd_;', conn_settings='' > > > conn_encoding='OTHER' > > > conn=48183040, query=' ' > > > conn=48183040, query='select version()' > > > [ fetched 1 rows ] > > > [ PostgreSQL version string = 'PostgreSQL 7.4.2 on i686-pc-linux-gnu, > > > compiled by GCC gcc (GCC) 3.3.2 20031218 (Gentoo Linux 3.3.2-r5, > > > propolice-3.3-7)' ] > > > [ PostgreSQL version number = '7.4' ] > > > conn=48183040, query='set DateStyle to 'ISO'' > > > conn=48183040, query='set geqo to 'OFF'' > > > conn=48183040, query='set extra_float_digits to 2' > > > conn=48183040, query='select oid from pg_type where typname='lo'' > > > [ fetched 0 rows ] > > > conn=48183040, query='select pg_client_encoding()' > > > [ fetched 1 rows ] > > > [ Client encoding = 'SQL_ASCII' (code = 0) ] > > > conn=48183040, > > > > > PGAPI_DriverConnect(out)='DRIVER={PostgreSQL};DATABASE=xxxxx;SERVER=xxx.xxx. > > xxx.xxx;PORT=5432;UID=adduser;PWD=xxxxx;ReadOnly=0;Protocol=6.4;FakeOidIndex > > =1;ShowOidColumn=1;RowVersioning=0;ShowSystemTables=0;ConnSettings=;Fetch=10 > > 0;Socket=4096;UnknownSizes=0;MaxVarcharSize=254;MaxLongVarcharSize=8190;Debu > > g=0;CommLog=1;Optimizer=1;Ksqo=1;UseDeclareFetch=0;TextAsLongVarchar=1;Unkno > > wnsAsLongVarchar=0;BoolsAsChar=1;Parse=0;CancelAsFreeStmt=0;ExtraSysTablePre > > fixes=dd_;;LFConversion=1;UpdatableCursors=1;DisallowPremature=0;TrueIsMinus > > 1=0;BI=0;ByteaAsLongVarBinary=0;UseServerSidePrepare=0' > > > STATEMENT ERROR: func=PGAPI_SetDescField, desc='', errnum=11, > > errmsg='can't > > > SQLSetDescField for this parameter number' > > --------------------------------------------------------- > > --- > > > hdbc=48183040, stmt=48177616, result=0 > > > manual_result=0, prepare=0, internal=0 > > > bindings=0, bindings_allocated=0 > > > parameters=0, parameters_allocated=0 > > > statement_type=-2, statement='(NULL)' > > > stmt_with_params='(NULL)' > > > data_at_exec=-1, current_exec_param=-1, put_data=0 > > > currTuple=-1, current_col=-1, lobj_fd=-1 > > > maxRows=0, rowset_size=1, keyset_size=0, cursor_type=0, > > > scroll_concurrency=1 > > > cursor_name='' > > > ----------------QResult > > Info ------------------------------- > > > CONN ERROR: func=PGAPI_SetDescField, desc='', errnum=0, errmsg='(NULL)' > > ------------------------------------------------------------ > > > henv=48176920, conn=48183040, status=1, num_stmts=16 > > > sock=48176976, stmts=48177048, lobj_type=-999 > > > ---------------- Socket Info ------------------------------- > > > socket=1324, reverse=0, errornumber=0, errormsg='(NULL)' > > > buffer_in=48194040, buffer_out=48198144 > > > buffer_filled_in=63, buffer_filled_out=0, buffer_read_in=63 > > > > > > > > > __________________________________ > > > Do you Yahoo!? > > > Yahoo! Tax Center - File online by April 15th > > > http://taxes.yahoo.com/filing.html > > > > > > ---------------------------(end of broadcast)--------------------------- > > > TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org > > > > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Tax Center - File online by April 15th > http://taxes.yahoo.com/filing.html
pgsql-odbc by date: