Thread: BUG #1253: Installation problem, connection fails

The following bug has been logged online:

Bug reference:      1253
Logged by:          Markus Varsta

Email address:      markus.varsta@iki.fi

PostgreSQL version: 8.0 Beta

Operating system:   WIN XP Home edition

Description:        Installation problem, connection fails

Details:

Hello !!

PostgreSQL 8.0 Datbase Server 8.0-beta2-dev3

Installation runs fine until attempting to associate procedural languages
with the base. Connection with the base fails, the same happens with
pg_admin.

Database systems logfile has entries like:

2004-09-28 22:27:20 FLE Standard Time LOG:  select() failed in statistics
buffer: An operation was attempted on something that is not a socket.


2004-09-28 22:27:20 FLE Standard Time LOG:  select() failed in statistics
collector: An operation was attempted on something that is not a socket.


2004-09-28 22:27:20 FLE Standard Time LOG:  statistics collector process
(PID 3792) was terminated by signal 1
2004-09-28 22:27:26 FLE Standard Time LOG:  could not receive data from
client: An operation was attempted on something that is not a socket.

Searching the web with the "An operation was attempted.." phrase yielded
results that suggested something had gone astray with "winsock". A suggested
remedy was to clear "winsock" and "winsock2" entries from the registry and
to re-install TCP/IP protocoll. This resolved the problem but an attempt to
reinstall the database reintroduced the problem only to be fixed with the
same kludge.

Yours sincerely: Markus Varsta

>2004-09-28 22:27:20 FLE Standard Time LOG:  statistics=20
>collector process=20
>(PID 3792) was terminated by signal 1=20
>2004-09-28 22:27:26 FLE Standard Time LOG:  could not receive=20
>data from=20
>client: An operation was attempted on something that is not a socket.=20
>
>Searching the web with the "An operation was attempted.."=20
>phrase yielded=20
>results that suggested something had gone astray with=20
>"winsock". A suggested=20
>remedy was to clear "winsock" and "winsock2" entries from the=20
>registry and=20
>to re-install TCP/IP protocoll. This resolved the problem but=20
>an attempt to=20
>reinstall the database reintroduced the problem only to be=20
>fixed with the=20
>same kludge.=20

This is not a postgresql issue, but one with your winsock. If you have
any firewall or antivirus software, try uninstalling it. (Just disabling
it may not  be enough). also, see the specific question about this
problem on http://pginstaller.projects.postgresql.org/FAQ_windows.html
for tip on a tool that might help you to determine what is wrong.

//Magnus