Skip site navigation (1) Skip section navigation (2)

Re: BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument"

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: maczniak(at)gmail(dot)com
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #6521: cannot make connection due to "getsockname() failed: Invalid argument"
Date: 2012-04-09 14:15:27
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-bugs
On Tue, Mar 6, 2012 at 12:46 AM,  <maczniak(at)gmail(dot)com> wrote:
> The following bug has been logged on the website:
> Bug reference:      6521
> Logged by:          Jeongho Jeon
> Email address:      maczniak(at)gmail(dot)com
> PostgreSQL version: 9.1.1
> Operating system:   Windows 7
> Description:
> Hi!
> PostgreSQL does not accept connections from clients sometimes.
> PostgreSQL is installed by Windows installer and it is started by Windows
> service on boot time automatically.  PostgreSQL logs are like below.  My
> coworkers encounter these phenomena occasionally.  After restarting the
> PostgreSQL service, it works well.  This log entry comes from
> src/backend/libpq/pqcomm.c.  I am not certain that this is a bug. I searched
> but could not find a clue.  Thanks!

Sometimes this sort of issue can be caused by anti-virus software
(even if it's disabled).

Robert Haas
The Enterprise PostgreSQL Company

In response to

pgsql-bugs by date

Next:From: Robert HaasDate: 2012-04-09 14:18:28
Subject: Re: corrupted table postgresql 8.3
Previous:From: Robert HaasDate: 2012-04-09 14:10:34
Subject: Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group