Thread: psql can not connect to the server on Win2000 NT

Hello,

I have installed PostgreSQL 8.beta2.dev3 on Windows 2000 NT using the
installer. There were two dialogs with messages like "Couldn't connect to
the server" or so. Then when I try to connect I get this message:

C:\Program Files\PostgreSQL\8.0-beta2-dev3\bin>psql.exe
psql.exe: server closed the connection unexpectedly
        This probably means the server terminated abnormally
        before or while processing the request.

The information in the log file is:

"2004-09-17 10:06:53 Central European Daylight Time LOG:  could not receive
data from client: An operation was attempted on something that is not a
socket.


2004-09-17 10:06:53 Central European Daylight Time LOG:  incomplete startup
packet"


Beside that, once every minute the following lines are written there too:

"2004-09-17 10:07:54 Central European Daylight Time LOG:  select() failed in
statistics collector: An operation was attempted on something that is not a
socket.


2004-09-17 10:07:54 Central European Daylight Time LOG:  select() failed in
statistics buffer: An operation was attempted on something that is not a
socket.


2004-09-17 10:07:54 Central European Daylight Time LOG:  statistics
collector process (PID 2396) was terminated by signal 1"

The PID is different every time.

I was told to send a bug report in the #postgresql channel on
irc.freenode.net IRC server.

I apologize if it is a known bug or not a bug at all.

Regards,
Kouber Saparev

>Hello,
>
>I have installed PostgreSQL 8.beta2.dev3 on Windows 2000 NT using the
>installer. There were two dialogs with messages like "Couldn't=20
>connect to
>the server" or so. Then when I try to connect I get this message:
>
>C:\Program Files\PostgreSQL\8.0-beta2-dev3\bin>psql.exe
>psql.exe: server closed the connection unexpectedly
>        This probably means the server terminated abnormally
>        before or while processing the request.
>
>The information in the log file is:
>
>"2004-09-17 10:06:53 Central European Daylight Time LOG:=20=20
>could not receive
>data from client: An operation was attempted on something that is not a
>socket.

This sounds a lot like FAQ item 3.2 on
http://pginstaller.projects.postgresql.org/FAQ_windows.html. Check those
instructions as a first step.

//Magnus

> > This sounds a lot like FAQ item 3.2 on=20
> > http://pginstaller.projects.postgresql.org/FAQ_windows.html. Check=20
> > those instructions as a first step.
>=20
> Maybe you're right that there's something installed on my=20
> computer that's bugging the postmaster. The only networking=20
> tool that I have installed is NetLimiter - but it only offers=20
> a possibility to manually limit the speed of some connections=20
> - not to forbid access or so. Anyway, I will try some tricks=20
> over there and will report the solution, if there's such.

NetLimiter is known to cause problems with PostgreSQL (along with some
other apps). It is just the kind of LSP that often breaks things.


//Magnus

> This sounds a lot like FAQ item 3.2 on
> http://pginstaller.projects.postgresql.org/FAQ_windows.html. Check those
> instructions as a first step.

Maybe you're right that there's something installed on my computer that's
bugging the postmaster. The only networking tool that I have installed is
NetLimiter - but it only offers a possibility to manually limit the speed of
some connections - not to forbid access or so. Anyway, I will try some
tricks over there and will report the solution, if there's such.

Thank you both Magnus and Harald.

Regards,
Kouber Saparev

Kouber Saparev wrote:
>>This sounds a lot like FAQ item 3.2 on
>>http://pginstaller.projects.postgresql.org/FAQ_windows.html. Check those
>>instructions as a first step.
>
>
> Maybe you're right that there's something installed on my computer that's
> bugging the postmaster. The only networking tool that I have installed is
> NetLimiter

This is a good example of a misleading error message, probably resulting
from examining errno. Using GetLastError() on those socket calls might
help reducing support requests.

Regards,
Andreas

>> Maybe you're right that there's something installed on my=20
>computer that's
>> bugging the postmaster. The only networking tool that I have=20
>installed is
>> NetLimiter
>
>This is a good example of a misleading error message, probably=20
>resulting=20
>from examining errno. Using GetLastError() on those socket calls might=20
>help reducing support requests.

Nope. The error is exactly the one stated. "Socket operation attempted
on something that is not a socket". This is what's returned from
GetLastError().


//Magnus