Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WUhlg-0007W5-RC for pgsql-general@arkaria.postgresql.org; Mon, 31 Mar 2014 19:21:13 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WUhlg-000692-8U for pgsql-general@arkaria.postgresql.org; Mon, 31 Mar 2014 19:21:12 +0000 Received: from makus.postgresql.org ([2001:4800:7903:4::125]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WUhle-00066n-8N for pgsql-general@postgresql.org; Mon, 31 Mar 2014 19:21:10 +0000 Received: from new2-smtp.messagingengine.com ([66.111.4.224]) by makus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WUhlb-0006Bm-8n for pgsql-general@postgresql.org; Mon, 31 Mar 2014 19:21:09 +0000 Received: from compute1.internal (compute1.nyi.mail.srv.osa [10.202.2.41]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id 75C75C9E for ; Mon, 31 Mar 2014 15:21:05 -0400 (EDT) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 31 Mar 2014 15:21:05 -0400 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=aklaver.com; h= message-id:date:from:mime-version:to:cc:subject:references :in-reply-to:content-type:content-transfer-encoding; s=mesmtp; bh=JH90LoiLFYqzxDntckH0Uce9QAc=; b=OQhbOyflZm5VwKnQctuTgogDkAeO j4cfHkTu+R6EdmGtCOEZxRZJk8PWhXUb97Qd+jMz0ZSn5fXw6n4hIcEMc1Rm0HyA SiMBMe492oZgfFApk0SlacX0NWf9jgytQdJxbh8m3Q+scYgpv4F3IUKRk0j7+Jfx BWF3LyibSHgpXNs= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:date:from:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding; s=smtpout; bh=JH90LoiLFYqzxDntckH0Uc e9QAc=; b=FK2F7yWmav5XOr/Rm7C2BH3qASa/NrVQatIn9id9neVjlzkVIJUJXc VaAT2x5plDAGqxhK0i9tLcGtQqfFIw79mw3b4nQOe3K0zc2HdcvgPALdRxeUiH/N ZRjdEBgXHWPLa8amFAUs2d3FPrhGpJ8+fNtM0dQC3g5t/GJq2cKy0= X-Sasl-enc: dXLfpCtmVPD8fIJM6GWP9x9AlwAfbp3I76ovoD6vaAMD 1396293664 Received: from killi.site (unknown [174.21.186.26]) by mail.messagingengine.com (Postfix) with ESMTPA id 3D8BBC007AA; Mon, 31 Mar 2014 15:21:04 -0400 (EDT) Message-ID: <5339C01F.5000301@aklaver.com> Date: Mon, 31 Mar 2014 12:21:03 -0700 From: Adrian Klaver User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Tom Lane CC: Willy-Bas Loos , lst_hoe02@kwsoft.de, pgsql-admin , "pgsql-general@postgresql.org" Subject: Re: [ADMIN]openvz and shared memory trouble References: <53357E83.2040101@aklaver.com> <53370026.2040509@aklaver.com> <53397DE7.2070903@aklaver.com> <15934.1396278062@sss.pgh.pa.us> <5339865C.9020209@aklaver.com> <16649.1396279693@sss.pgh.pa.us> In-Reply-To: <16649.1396279693@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.0 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-general Precedence: bulk Sender: pgsql-general-owner@postgresql.org On 03/31/2014 08:28 AM, Tom Lane wrote: > Adrian Klaver writes: >> At this point the memory allocation as a problem is as much conjecture >> as anything else, at least to me. So what is causing SIGBUS is an open >> question in my mind. > > Agreed, it's unproven what's causing the SIGBUS in the case at hand. > However, in the case I investigated for Josh Kupershmidt, it was provably > the fault of the kernel for failing to supply memory to back the shared > memory segment that it had previously agreed to allocate. The fact that > both users are trying to run their standby server under OpenVZ is, shall > we say, merely suggestive. Yes, the fact that the problem seems to go away with a change in shared_buffers seems to point in that direction also. To get through the smoke to the fire, there are more questions to be answered: 1) The OP says the shared_buffered setting that failed was 4GB and that 'tuning' down the setting solved the problem. So it would be nice to know what setting worked? 2) In hand with 1), the memory settings for the virtualization host and the container(s) involved are? 3) What is the host OS? 4) What version of OpenVZ? 5) What is the layout? Are the primary and standby on the same container, different containers or some other arrangement? In other words could there be some other resource conflict going on, say network? 6) Are the crashes random or do they follow some pattern? > > regards, tom lane > -- Adrian Klaver adrian.klaver@aklaver.com -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general