From: Dave Haywood <tla@oak.selfip.net>
To: "hpanvin@gmail.com" <hpa@zytor.com>
Cc: Josh Boyer <jwboyer@gmail.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: Postgres fails to start due to kernel issue?
Date: Fri, 20 Jan 2012 10:06:05 +0000 [thread overview]
Message-ID: <4F193C8D.3010506@oak.selfip.net> (raw)
In-Reply-To: <534a6e5c-4c14-48bd-a9dc-d5b884daeb63@email.android.com>
On 20/01/2012 03:13, hpanvin@gmail.com wrote:
> Yes, it almost certainly is. Fixed in rc1.
Correct, working again under 3.3.0-rc1. Thanks!
Linux s1 3.3.0-rc1 #135 SMP Fri Jan 20 09:59:56 GMT 2012 i686
Pentium III (Coppermine) GenuineIntel GNU/Linux
>
> Josh Boyer<jwboyer@gmail.com> wrote:
>
>> On Thu, Jan 19, 2012 at 7:45 PM, Dave Haywood<tla@oak.selfip.net>
>> wrote:
>>> Hi,
>>>
>>> I noticed after upgrading to 3.2.0-08812-gc2bc3a3 that Postgres-9.1
>> server
>>> fails to start with error:
>>>
>>> FATAL: could not create shared memory segment: Function not
>> implemented
>>> DETAIL: Failed system call was shmget(key=5432001, size=30523392,
>> 03600).
>>> After some googling, I thought it was a SYSV shared memory sizing
>> issue but
>>> manually changing kernel.shmmax and kernel.shmall had no effect.
>>>
>>> The problem has been introduced between 3.2.0-08694-g53999bf and
>>> 3.2.0-08812-gc2bc3a3.
>>>
>>> Let me know if you need any more information. Bisecting is *very*
>> slow on
>>> this machine!
>> If you run strace on it, does it fail with ENOSYS? This might be
>> related to an issue Peter just fixed.
>>
>> josh
prev parent reply other threads:[~2012-01-20 10:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 0:45 PROBLEM: Postgres fails to start due to kernel issue? Dave Haywood
2012-01-20 1:40 ` Josh Boyer
2012-01-20 3:13 ` hpanvin@gmail.com
2012-01-20 10:06 ` Dave Haywood [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4F193C8D.3010506@oak.selfip.net \
--to=tla@oak.selfip.net \
--cc=hpa@zytor.com \
--cc=jwboyer@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox