Обсуждение: Troubleshoot "unexpected EOF on client connection"

Поиск
Список
Период
Сортировка

Troubleshoot "unexpected EOF on client connection"

От
Chris Gamache
Дата:
Some of my ODBC connections are dying unexpectedly (and randomly) with the
Postgresql Log Message "unexpected EOF on client connection" ... It happens
about one in every 50K-100K queries.

I would really appreciate some suggestions for a method to find the cause of
these dropped connections.

CG

__________________________________
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
http://taxes.yahoo.com/filing.html

Re: Troubleshoot "unexpected EOF on client connection"

От
Richard Huxton
Дата:
On Wednesday 31 March 2004 15:24, Chris Gamache wrote:
> Some of my ODBC connections are dying unexpectedly (and randomly) with the
> Postgresql Log Message "unexpected EOF on client connection" ... It happens
> about one in every 50K-100K queries.

This is commonly the client crashing / timing out.

> I would really appreciate some suggestions for a method to find the cause
> of these dropped connections.

You could turn logging on at the client end - there are settings in the odbc
driver settings. Could be a big log-file though, if you have to wait 100,000
queries.

--
  Richard Huxton
  Archonet Ltd

Re: Troubleshoot "unexpected EOF on client connection"

От
Chris Gamache
Дата:
PgODBC's logfiles don't have a time index, and you also can't change the output
location of the files unless you recompile the driver (unless you know
something that I don't). My C drive is strictly OS, and there's not much
breathing room there. I can't get PgODBC to build under VisualStudio.NET, so a
recompile to include timestamp and variable logfile location is out of my
ability. I don't know why, but I can not get a trace from the ODBC control
panel either. Can you help?

CG

--- Richard Huxton <dev@archonet.com> wrote:
> On Wednesday 31 March 2004 15:24, Chris Gamache wrote:
> > Some of my ODBC connections are dying unexpectedly (and randomly) with the
> > Postgresql Log Message "unexpected EOF on client connection" ... It happens
> > about one in every 50K-100K queries.
>
> This is commonly the client crashing / timing out.
>
> > I would really appreciate some suggestions for a method to find the cause
> > of these dropped connections.
>
> You could turn logging on at the client end - there are settings in the odbc
> driver settings. Could be a big log-file though, if you have to wait 100,000
> queries.
>
> --
>   Richard Huxton
>   Archonet Ltd


__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/

Re: Troubleshoot "unexpected EOF on client connection"

От
Richard Huxton
Дата:
On Thursday 01 April 2004 20:10, Chris Gamache wrote:
> PgODBC's logfiles don't have a time index, and you also can't change the
> output location of the files unless you recompile the driver (unless you
> know something that I don't). My C drive is strictly OS, and there's not
> much breathing room there. I can't get PgODBC to build under
> VisualStudio.NET, so a recompile to include timestamp and variable logfile
> location is out of my ability. I don't know why, but I can not get a trace
> from the ODBC control panel either. Can you help?

Well - you could turn up the logging on the PG end, but that's not going to
help you if the client is crashing (unless it's always after a particular
query).

If you can't log at the client, I don't think there's much you can do to
diagnose this. I'd be tempted to move some stuff out of C: and make space for
the logs, just while you're looking at this.

--
  Richard Huxton
  Archonet Ltd

Re: Troubleshoot "unexpected EOF on client connection"

От
Chris Gamache
Дата:
--- Richard Huxton <dev@archonet.com> wrote:
> On Thursday 01 April 2004 20:10, Chris Gamache wrote:
> If you can't log at the client, I don't think there's much you can do to
> diagnose this. I'd be tempted to move some stuff out of C: and make space for
> the logs, just while you're looking at this.

Whatabout the lack of a time index? I'm pretty quick, but the WebApplication
only fails under load, and I'm not THAT quick... So there would be no other way
to find the failure except for a timeindex, yes? I've seen it fail on many
different queries. I believe that they are all Select queries, though... No
Insert, Update, or Deletes...

If its not a bug, it is probably as simple as an improper setting. Here's my
connection string in case someone sees a glaring error...

Provider=MSDASQL.1;Password=XXX;Persist Security Info=True;User
ID=XXX;Mode=ReadWrite;Extended

Properties="DRIVER={PostgreSQL};DATABASE=XXX;SERVER=XXX.XXX.XXX.XXX;PORT=5432;UID=XXX;PWD=XXX;READONLY=0;PROTOCOL=6.4;FAKEOIDINDEX=1;SHOWOIDCOLUMN=1;ROWVERSIONING=0;SHOWSYSTEMTABLES=0;CONNSETTINGS="

Am I missing a critical setting for 7.03.01.00 ?

CG

__________________________________
Do you Yahoo!?
Yahoo! Small Business $15K Web Design Giveaway
http://promotions.yahoo.com/design_giveaway/

Re: Troubleshoot "unexpected EOF on client connection"

От
Matthew and Karen Brown
Дата:
Chris,

You should be able to trace from ODBC, but, regardless of how the
control panel applet appears, you must close the applet after starting
the log in order for the log to be generated. Then you have to reopen
the applet to stop the log. Pretty crummy, eh? I have done this when a
query I was running from Access was failing.

Hope this helps.

-- Matt

Chris Gamache wrote:

>PgODBC's logfiles don't have a time index, and you also can't change the output
>location of the files unless you recompile the driver (unless you know
>something that I don't). My C drive is strictly OS, and there's not much
>breathing room there. I can't get PgODBC to build under VisualStudio.NET, so a
>recompile to include timestamp and variable logfile location is out of my
>ability. I don't know why, but I can not get a trace from the ODBC control
>panel either. Can you help?
>
>CG
>
>--- Richard Huxton <dev@archonet.com> wrote:
>
>
>>On Wednesday 31 March 2004 15:24, Chris Gamache wrote:
>>
>>
>>>Some of my ODBC connections are dying unexpectedly (and randomly) with the
>>>Postgresql Log Message "unexpected EOF on client connection" ... It happens
>>>about one in every 50K-100K queries.
>>>
>>>
>>This is commonly the client crashing / timing out.
>>
>>
>>
>>>I would really appreciate some suggestions for a method to find the cause
>>>of these dropped connections.
>>>
>>>
>>You could turn logging on at the client end - there are settings in the odbc
>>driver settings. Could be a big log-file though, if you have to wait 100,000
>>queries.
>>
>>--
>>  Richard Huxton
>>  Archonet Ltd
>>
>>
>
>
>__________________________________
>Do you Yahoo!?
>Yahoo! Small Business $15K Web Design Giveaway
>http://promotions.yahoo.com/design_giveaway/
>
>---------------------------(end of broadcast)---------------------------
>TIP 7: don't forget to increase your free space map settings
>
>
>