BUG #14423: Fail to connect to DB
The following bug has been logged on the website:
Bug reference: 14423
Logged by: Mikael Wallen
Email address: mikael.wallen@spark-vision.com
PostgreSQL version: 9.4.10
Operating system: Windows 10 (Version 1607 OS Build 14393.447)
Description:
After recent Windows updates we are getting connection errors and the logs
are full of the following errors:
2016-11-14 10:00:43 CET LOG: could not reserve shared memory region
(addr=00000000022C0000) for child 0000000000000FE0: error code 487
2016-11-14 10:00:43 CET LOG: could not fork autovacuum worker process: No
error
We are also seeing the same issue on Windows 7 x64 and with PostgreSQL
versions 9.4.8, 9.5.2 and 9.5.5.
Errors saying "could not fork new process for connection: No error" are also
occurring when using pgadminIII as well as psql. Everything worked well
before the recent Windows updates. Is this somehow related to changes in
ASLR (address space layout randomization) and if so, is there any
workaround?
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.com> wrote:
Errors saying "could not fork new process for connection: No error" are also
occurring when using pgadminIII as well as psql. Everything worked well
before the recent Windows updates. Is this somehow related to changes in
ASLR (address space layout randomization) and if so, is there any
workaround?
Let me guess: you are seeing that since you updated to Win7 SP1?
That's not the first complain in the area...
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Not exactly. We are seeing this on both Windows 7 SP1 and Windows 10 and it started after recent Windows security updates.
If we manually restart the PostgreSQL service it starts working again but the problem usually comes back after a day or two.
/Mikael
-----Original Message-----
From: Michael Paquier [mailto:michael.paquier@gmail.com]
Sent: den 15 november 2016 04:10
To: Mikael Wallén <Mikael.Wallen@spark-vision.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: [BUGS] BUG #14423: Fail to connect to DB
On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.com> wrote:
Errors saying "could not fork new process for connection: No error"
are also occurring when using pgadminIII as well as psql. Everything
worked well before the recent Windows updates. Is this somehow related
to changes in ASLR (address space layout randomization) and if so, is
there any workaround?
Let me guess: you are seeing that since you updated to Win7 SP1?
That's not the first complain in the area...
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
Some additional info.
It seems as if this is related to F-Secure and/or anti-virus software in general. A colleague tried to temporarily disable F-Secure and then the errors stopped. However as soon as he enabled F-Secure again the error messages started filling the PostgreSQL logs.
However I have also seen the same error messages on a virtual machine running Windows 10 Pro with the latest Windows updates and there I am not running F-Secure. I am running Windows Defender though.
/Mikael
-----Original Message-----
From: Michael Paquier [mailto:michael.paquier@gmail.com]
Sent: den 15 november 2016 04:10
To: Mikael Wallén <Mikael.Wallen@spark-vision.com>
Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: [BUGS] BUG #14423: Fail to connect to DB
On Mon, Nov 14, 2016 at 1:07 AM, <mikael.wallen@spark-vision.com> wrote:
Errors saying "could not fork new process for connection: No error"
are also occurring when using pgadminIII as well as psql. Everything
worked well before the recent Windows updates. Is this somehow related
to changes in ASLR (address space layout randomization) and if so, is
there any workaround?
Let me guess: you are seeing that since you updated to Win7 SP1?
That's not the first complain in the area...
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
On Wed, Nov 16, 2016 at 1:48 AM, Mikael Wallén
<Mikael.Wallen@spark-vision.com> wrote:
Some additional info.
It seems as if this is related to F-Secure and/or anti-virus software in general. A colleague tried to temporarily disable F-Secure and then the errors stopped. However as soon as he enabled F-Secure again the error messages started filling the PostgreSQL logs.
However I have also seen the same error messages on a virtual machine running Windows 10 Pro with the latest Windows updates and there I am not running F-Secure. I am running Windows Defender though.
Interesting. So would Windows 10 be enforcing Windows Defender or a
virus scanner to be enabled? This OS shines a lot in updating settings
forcibly with its automatic updates, sometimes without caring about
what the user may have changed in the past.
--
Michael
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs