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


---------------------------(end of broadcast)---------------------------
TIP 7: don't forget to increase your free space map settings

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

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo (AT) postgresql (DOT) org)

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


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

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


---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo (AT) postgresql (DOT) org so that your
message can get through to the mailing list cleanly

Kouber Saparev wrote:
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

---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

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

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org