Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gRJBI-0002XI-Bb for pgsql-performance@arkaria.postgresql.org; Mon, 26 Nov 2018 15:52:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gRJBH-0003o4-60 for pgsql-performance@arkaria.postgresql.org; Mon, 26 Nov 2018 15:52:15 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gRJBG-0003nA-ND for pgsql-performance@lists.postgresql.org; Mon, 26 Nov 2018 15:52:14 +0000 Received: from mail-it1-x130.google.com ([2607:f8b0:4864:20::130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gRJBD-0001B1-Ad for pgsql-performance@postgresql.org; Mon, 26 Nov 2018 15:52:13 +0000 Received: by mail-it1-x130.google.com with SMTP id h65so28393386ith.3 for ; Mon, 26 Nov 2018 07:52:11 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=5JpRU3KqnIm4R1gm6THVLPaDkMJwRf7wGUKxz9PDXK4=; b=e7kDqXEaiTfq/4bQ3Gspv32kOwvu0NlTek5PJFJRJJ6uSJjo6MtVJgC3OGYmr7QO+W SkyF2HH8M38wk7jmSM+a68QER2u6B3UNaKn4LLD4uABWTdlWS0Y3F5xeMfsnDZqIUdR8 sEKxX96YdtBgOA63HWztcbW2MuYBub/kFvoZBaehFAq0NQFhCqPIh56OyFBdT6wBesbb 1BwkAniBJjCzpO8sz3b3FIzunieG/azA0GUDGOntb4esnUGuPxmyfm1vTihy+0JSyL0/ 9QjyhqkjKHlIuiMxiJ6009MJVdt0VRpquMx0Y3vQoxyBEYltdsKduUO0/cuTP3VHoRjR C5sQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=5JpRU3KqnIm4R1gm6THVLPaDkMJwRf7wGUKxz9PDXK4=; b=B6Pqe9U/TxzJx/PMHPibHsPAx1ONjJgH/Xx+0agkkMiBnVPlASGNv59G5w7gU3TY0a l1eGyzv8nPzemFg3mFQ8SbCBkmI1KRH1KGzX3sCbph8/4ejcVoUhE5gjbzneWJZaDzfh NcVIzZpo4aYScsMJBvA8X957FSC8NoHoZ3hanK/Oju2RtVETzpuDdl8H+kJ+/FROBRXF p7mUvr+UN75Us9/rQH20bDPsmt4DS9M146U0PFZLViER8yWGkIMMM1R+VawpQx6zSDCK yvSoMXaIsBSgRGy9OUkPe304ktwowDlMxnVVvjxkBaaggeYE6BFgckOl5QCcFJ19W05x lFog== X-Gm-Message-State: AGRZ1gIQ2vgJJRQLgZnP9lWza0aMFxNUdaP1lgplEAoeDgziQJf/CX1y DYBIN3F28nW6CvOLTu4lukF5sw== X-Google-Smtp-Source: AFSGD/WTFEZb6o3QTyh6AdR9pE/LgoAwj935+1wPFyGrpwNWycxzQY3KFY/wFDEg8uQqqmxNeyw/1A== X-Received: by 2002:a24:d1c6:: with SMTP id w189-v6mr24184458itg.38.1543247530149; Mon, 26 Nov 2018 07:52:10 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id 72-v6sm425838itk.36.2018.11.26.07.52.09 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 26 Nov 2018 07:52:09 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 38740804CB3; Mon, 26 Nov 2018 09:52:08 -0600 (CST) Date: Mon, 26 Nov 2018 09:52:08 -0600 From: Justin Pryzby To: Jakub Glapa Cc: pgsql-performance@postgresql.org, Thomas Munro Subject: Re: dsa_allocate() faliure Message-ID: <20181126155207.GZ10913@telsasoft.com> References: <20181122160958.GJ10913@telsasoft.com> <20181123161028.GL10913@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hi, thanks for following through. On Mon, Nov 26, 2018 at 04:38:35PM +0100, Jakub Glapa wrote: > I had a look at dmesg and indeed I see something like: > > postgres[30667]: segfault at 0 ip 0000557834264b16 sp 00007ffc2ce1e030 > error 4 in postgres[557833db7000+6d5000] That's useful, I think "at 0" means a null pointer dereferenced. Can you check /var/log/messages (or ./syslog or similar) and verify the timestamp matches the time of the last crash (and not an unrelated crash) ? The logs might also indicate if the process dumped a core file anywhere. I don't know what distribution/OS you're using, but it might be good to install abrt (RHEL) or apport (ubuntu) or other mechanism to save coredumps, or to manually configure /proc/sys/kernel/core_pattern. On centos, I usually set: /etc/abrt/abrt-action-save-package-data.conf OpenGPGCheck = no Also, it might be good to install debug symbols, in case you do find a core dump now or get one later. On centos: yum install postgresql10-debuginfo or debuginfo-install postgresql10-server Make sure this exactly matches the debug symbols exactly match the server version. Justin