Re: Infinite increment of postgre.exe in taskmanager

From: "Magnus Hagander" <mha(at)sollentuna(dot)net>
To: "Stefan van Aalst" <Stefan(dot)vanAalst(at)zonnet(dot)nl>
Cc: <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Infinite increment of postgre.exe in taskmanager
Date: 2006-06-02 17:25:59
Message-ID: 6BCB9D8A16AC4241919521715F4D8BCEA0F9DB@algol.sollentuna.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

[list re-added]

> In the eventlog I found quite often the following (therefore
> I assume it has to do with those many postgres.exe's). Does
> this give an indication where to look for the problem/solution?

Yes, it definitly does.

> gegevens zijn deel van de gebeurtenis: LOG: unexpected EOF
> on client connection (Can't find description of event-ID (0)
> in the source (PosgreSQL) The local computer might not have
> the necessary registry data or DLL-message files to display
> messages from an external computer. You might want to try
> the option /AUXsource= to obtain these descriptions, see Help
> and support for more details. The following data are part of
> the event: LOG: unexpected EOF on the client connection)

First - the fact that it can't find the DLL message file shows that
PostgreSQL is not properly installed. I take it it wasn't installed
using the official installer?

The "unepxected EOF" message is normal for any client that exits without
explicitly closing the connection.

> support for more details. The following data are part of the
> event: FATAL: could not duplicate socket 1772 for use in the
> backend: error code 10038)

This is a not too uncommon error, meaning that something broke your
TCP/IP stack. We've seen this many times, and it's usually either
antivirus or personal firewall software. If you have any of those on the
machine, try uninstalling them and see if that helps (sometimes it's
enough to disable them for the pg processes, sometimes you need to
uninstall them completely).

If that doesn't help, search for LSPfix - it's a tool that can help you
fix it.

//Magnus

Browse pgsql-bugs by date

  From Date Subject
Next Message Patrick Hayes 2006-06-02 19:47:02 BUG #2465: Installation
Previous Message Sebastien MAYER 2006-06-02 16:11:48 BUG #2464: 'After' are not called the first time of the user session