BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log.

On Fri, Nov 11, 2016 at 9:12 PM, <jari.kopponen@patria.fi> wrote:

The following bug has been logged on the website:

Bug reference: 14419
Logged by: jari kopponen
Email address: jari.kopponen@patria.fi
PostgreSQL version: 9.4.4
Operating system: Windows 7 Professional, 64 bit SP 1
Description:

After we installed kb3177467 (Servicing stack update for Windows 7 SP1 and
Windows Server 2008 R2 SP1: September 20, 2016) windows update, we faced
problems with database connections. In postgresql there is log entries
"could not reserve shared memory region (addr:xxx) for child(yyy): error
code 487. This seems to be quite similar problem than described in : BUG
#14050.

From where are those builds? Is ASLR enabled? I saw patterns of broken
shared memory with Win 2k8 R2 because of that.
--
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 11/11/2016 14:47, Michael Paquier wrote:

On Fri, Nov 11, 2016 at 9:12 PM, <jari.kopponen@patria.fi> wrote:

The following bug has been logged on the website:

Bug reference: 14419
Logged by: jari kopponen
Email address: jari.kopponen@patria.fi
PostgreSQL version: 9.4.4
Operating system: Windows 7 Professional, 64 bit SP 1
Description:

After we installed kb3177467 (Servicing stack update for Windows 7 SP1 and
Windows Server 2008 R2 SP1: September 20, 2016) windows update, we faced
problems with database connections. In postgresql there is log entries
"could not reserve shared memory region (addr:xxx) for child(yyy): error
code 487. This seems to be quite similar problem than described in : BUG
#14050.

From where are those builds? Is ASLR enabled? I saw patterns of broken
shared memory with Win 2k8 R2 because of that.

FWIW, there was 3 reports for this issue on french board in the last few
days (including pg 9.3.3 and 9.5.5), I think all of them on W7.

--
Julien Rouhaud
http://dalibo.com - http://dalibo.org

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

On Fri, Nov 11, 2016 at 11:22 PM, Julien Rouhaud
<julien.rouhaud@dalibo.com> wrote:

FWIW, there was 3 reports for this issue on french board in the last few
days (including pg 9.3.3 and 9.5.5), I think all of them on W7.

It may be a good idea to check if ASLR is really enabled. Win2k8 R2
and Win7 SP1 have introduced the "force ASLR" feature...
https://support.microsoft.com/en-us/kb/2639308
Not sure if that's related directly to that, but the reports popping
up with the latest versions of Win7 and win2k8 are pointing out to
something that the OS changed...
--
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 12/11/2016 05:57, Michael Paquier wrote:

On Fri, Nov 11, 2016 at 11:22 PM, Julien Rouhaud
<julien.rouhaud@dalibo.com> wrote:

FWIW, there was 3 reports for this issue on french board in the last few
days (including pg 9.3.3 and 9.5.5), I think all of them on W7.

It may be a good idea to check if ASLR is really enabled. Win2k8 R2
and Win7 SP1 have introduced the "force ASLR" feature...

I just asked and provided a link to this thread. I'll provide any new
information.

https://support.microsoft.com/en-us/kb/2639308
Not sure if that's related directly to that, but the reports popping
up with the latest versions of Win7 and win2k8 are pointing out to
something that the OS changed...

Definitely.

--
Julien Rouhaud
http://dalibo.com - http://dalibo.org

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Installer has been downloaded from: http://www.enterprisedb.com.
Based on Process Explorer, ALSR Is not enabled.
---
Jari

-----Original Message-----
From: Michael Paquier [mailto:michael.paquier@gmail.com]
Sent: 11. marraskuuta 2016 15:48
To: Jari Kopponen <jari.kopponen@patria.fi>
Cc: PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: [BUGS] BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log.

On Fri, Nov 11, 2016 at 9:12 PM, <jari.kopponen@patria.fi> wrote:

The following bug has been logged on the website:

Bug reference: 14419
Logged by: jari kopponen
Email address: jari.kopponen@patria.fi
PostgreSQL version: 9.4.4
Operating system: Windows 7 Professional, 64 bit SP 1
Description:

After we installed kb3177467 (Servicing stack update for Windows 7 SP1
and Windows Server 2008 R2 SP1: September 20, 2016) windows update, we
faced problems with database connections. In postgresql there is log
entries "could not reserve shared memory region (addr:xxx) for
child(yyy): error code 487. This seems to be quite similar problem
than described in : BUG #14050.

From where are those builds? Is ASLR enabled? I saw patterns of broken shared memory with Win 2k8 R2 because of that.
--
Michael

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs

Force ASLR is not enabled for PostgreSQL.

I made further investigations. If I delay PostgreSQL start (by using "Delayed Start" -option with PostgreSQL -service or by starting manually PostgreSQL) the problem disappears.
So trigger for the problems might be high CPU of high hard-disk load on windows startup -phase. Or some dependency to other windows service.
---
Jari

-----Original Message-----
From: Michael Paquier [mailto:michael.paquier@gmail.com]
Sent: 12. marraskuuta 2016 6:58
To: Julien Rouhaud <julien.rouhaud@dalibo.com>
Cc: Jari Kopponen <jari.kopponen@patria.fi>; PostgreSQL mailing lists <pgsql-bugs@postgresql.org>
Subject: Re: [BUGS] BUG #14419: DB connections fails with "could not reserve shared memory region" in postgresql log.

On Fri, Nov 11, 2016 at 11:22 PM, Julien Rouhaud <julien.rouhaud@dalibo.com> wrote:

FWIW, there was 3 reports for this issue on french board in the last
few days (including pg 9.3.3 and 9.5.5), I think all of them on W7.

It may be a good idea to check if ASLR is really enabled. Win2k8 R2 and Win7 SP1 have introduced the "force ASLR" feature...
https://support.microsoft.com/en-us/kb/2639308
Not sure if that's related directly to that, but the reports popping up with the latest versions of Win7 and win2k8 are pointing out to something that the OS changed...
--
Michael

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs