Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pX3PJ-0001Ak-3H for pgsql-admin@arkaria.postgresql.org; Tue, 28 Feb 2023 17:04:53 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pX3PG-00054l-Sb for pgsql-admin@arkaria.postgresql.org; Tue, 28 Feb 2023 17:04:50 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pVrrf-0004oS-Mk for pgsql-admin@lists.postgresql.org; Sat, 25 Feb 2023 10:33:15 +0000 Received: from mail-cy.bbox.fr ([194.158.98.48]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pVrrc-0004aJ-Em for pgsql-admin@lists.postgresql.org; Sat, 25 Feb 2023 10:33:14 +0000 Received: from mail.jppozzi.dyndns.org (mer91-h01-176-172-74-140.dsl.sta.abo.bbox.fr [176.172.74.140]) by mail-cy.bbox.fr (Postfix) with ESMTP id 92CA339; Sat, 25 Feb 2023 11:33:08 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.jppozzi.dyndns.org (Postfix) with ESMTP id 4A24C30026F; Sat, 25 Feb 2023 11:33:08 +0100 (CET) Received: from mail.jppozzi.dyndns.org ([127.0.0.1]) by localhost (mail.jppozzi.dyndns.org [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 92Am6sx2jF36; Sat, 25 Feb 2023 11:33:05 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.jppozzi.dyndns.org (Postfix) with ESMTP id B3F5E303423; Sat, 25 Feb 2023 11:33:05 +0100 (CET) X-Virus-Scanned: amavisd-new at mail.jppozzi.dyndns.org Received: from mail.jppozzi.dyndns.org ([127.0.0.1]) by localhost (mail.jppozzi.dyndns.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id PzuhC6BMKPkA; Sat, 25 Feb 2023 11:33:05 +0100 (CET) Received: from mail.jppozzi.dyndns.org (mail.jpp.fr [192.168.2.21]) by mail.jppozzi.dyndns.org (Postfix) with ESMTP id 0E63530026F; Sat, 25 Feb 2023 11:33:05 +0100 (CET) Date: Sat, 25 Feb 2023 11:33:04 +0100 (CET) From: JP Pozzi To: Ron Cc: pgsql-admin Message-ID: <505557535.2230.1677321184966.JavaMail.zimbra@jppozzi.dyndns.org> In-Reply-To: <4b583c4a-022f-f452-c0c8-0a932a6ee411@gmail.com> References: <4b583c4a-022f-f452-c0c8-0a932a6ee411@gmail.com> Subject: Re: New PG14 server won't start with >2GB shared_buffers MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="=_7208d730-0a89-4d40-b1a3-1d0e921801a5" X-Originating-IP: [192.168.2.8] X-Mailer: Zimbra 8.8.15_GA_4484 (ZimbraWebClient - FF102 (Linux)/8.8.15_GA_4481) Thread-Topic: New PG14 server won't start with >2GB shared_buffers Thread-Index: EeUybQqXJfXI0RjaekbIfFVyqHojcQ== X-VADE-SPAMSTATE: clean X-VADE-SPAMSCORE: 0 X-VADE-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudekgedgudegvdcutefuodetggdotefrodftvfcurfhrohhfihhlvgemuceuqfgfjgfifgfgufdpucfqfgfvpdcuggftfghnshhusghstghrihgsvgenuceurghilhhouhhtmecufedttdenucenucfjughrpeffhffvvefkjghfufggtghiofhtsegrtdgtreertdejnecuhfhrohhmpeflrfcurfhoiiiiihcuoehjphhpsehjphhpohiiiihirdguhihnughnshdrohhrgheqnecuggftrfgrthhtvghrnheptdelfeeitdekueevfeffheffieeffeeliedtheevkedvhfffteehhfffudfhtedunecuffhomhgrihhnpegrfigvsggvrhhinhhtrdgtohhmnecukfhppedujeeirddujedvrdejgedrudegtddpudelvddrudeikedrvddrkeenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhepihhnvghtpedujeeirddujedvrdejgedrudegtddphhgvlhhopehmrghilhdrjhhpphhoiiiiihdrugihnhgunhhsrdhorhhgpdhmrghilhhfrhhomhepjhhpphesjhhpphhoiiiiihdrugihnhgunhhsrdhorhhgpdhnsggprhgtphhtthhopedvpdhrtghpthhtoheprhhonhhljhhohhhnshhonhhjrhesghhmrghilhdrtghomhdprhgtphhtthhopehpghhsqhhlqdgrughmihhnsehlihhsthhsrdhpohhsthhgrhgvshhqlhdrohhrgh List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --=_7208d730-0a89-4d40-b1a3-1d0e921801a5 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello,=20 Something with large pages ?=20 Regards=20 De: "Ron" =20 =C3=80: "pgsql-admin" =20 Envoy=C3=A9: Samedi 25 F=C3=A9vrier 2023 11:25:10=20 Objet: Re: New PG14 server won't start with >2GB shared_buffers=20 Why did you have to drop shared buffers to 500MB, instead of something just= below 2GB?=20 And what's "your kernel's SHMALL parameter"?=20 On 2/24/23 20:08, Chris Hoover wrote:=20 Hello All,=20 Have a strange issue that I can not solve.=20 I have a new server that has 1TB ram (not a typo). I have been fighting wit= h this evening to start up with a shared_buffer setting over 2GB. When the = memory allocation breaks 2GB, the database won=E2=80=99t start. I=E2=80=99v= e dropped it down to 500M to get the database online. We=E2=80=99ve tried b= oth SysV memory and mmap memory.=20 Any ideas on what is going on and how to resolve? I=E2=80=99m sure I=E2=80= =99m missing something obvious, but it is totally eluding me.=20 OS: Ubuntu 18.04=20 Memory: 1007GB=20 CPU: Intel(R) Xeon(R) CPU X7550 @ 2.00GHz (64 cores total)=20 Kernel Memory:=20 kernel.shmmax =3D 274877906944=20 kernel.shmall =3D 17179869184=20 Postgres Config:=20 name | setting=20 autovacuum_max_workers | 3=20 autovacuum_work_mem | -1=20 effective_cache_size | 98992128=20 fsync | on=20 full_page_writes | on=20 maintenance_work_mem | 2097152=20 shared_buffers | 64000=20 shared_memory_type | sysv=20 temp_buffers | 4096=20 wal_buffers | 2048=20 work_mem | 119990=20 If you need additional parameters, please ask=20 SysV Error:=20 Feb 25 01:55:16 appdb-server01.production.aweberint.com postgres[34680]: FA= TAL: could not create shared memory segment: Cannot allocate memory=20 DETAIL: Failed system call was shmget(key=3D2359323, size=3D2063564800, 036= 00).=20 HINT: This error usually means that PostgreSQL's request for a shared memor= y segment exceeded your kernel's SHMALL parameter. You might need to reconf= igure the kernel with larger SHMALL.=20 Mmap Error:=20 FATAL: could not map anonymous shared memory: Cannot allocate memory=20 HINT: This error usually means that PostgreSQL's request for a shared memor= y segment exceeded available memory, swap space, or huge pages. To reduce t= he request size (currently 1635737600 bytes), reduce PostgreSQL's shared me= mory usage, perhaps by reducing shared_buffers or max_connections.=20 Thanks,=20 Chris Hoover=20 Senior DBA=20 AWeber.com=20 Cell: (803) 528-2269=20 Email: [ mailto:chrish@aweber.com | chrish@aweber.com ]=20 --=20 Born in Arizona, moved to Babylonia.=20 --=_7208d730-0a89-4d40-b1a3-1d0e921801a5 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable
Hello,

Something with large pages ?

Regards

De: "Ron" <ronljohnsonjr@gmail.com>
= =C3=80: "pgsql-admin" <pgsql-admin@lists.postgresql.org>
En= voy=C3=A9: Samedi 25 F=C3=A9vrier 2023 11:25:10
Objet: Re: Ne= w PG14 server won't start with >2GB shared_buffers

Why did you have to drop shared buf= fers to 500MB, instead of something just below 2GB?

And what's "your kernel's SHMALL parameter"?

On 2/24/23 20:08, Chris Hoover wrote:
=20
Hello All,

Have a strange issue that I can not solve.

I have a new server that has 1TB ram (not a typo).  I have been fighting with this evening to start up with a shared_buffer setting over 2GB.  When the memory allocation  breaks 2GB= , the database won=E2=80=99t start.  I=E2=80=99ve dropped it down to= 500M to get the database online.  We=E2=80=99ve tried both SysV memory and mma= p memory.

Any ideas on what is going on and how to resolve?  I=E2=80= =99m sure I=E2=80=99m missing something obvious, but it is totally eluding me= .

OS: Ubuntu 18.04
Memory:  1007GB
CPU: Intel(R) Xeon(R) CPU          = ; X7550  @ 2.00GHz (64 cores total)

Kernel Memory:
kernel.shmmax =3D 274877906944
kernel.shmall =3D 17179869184

Postgres Config:
                 = name                    =              |                  setting
 autovacuum_max_workers          = ;       | 3
 autovacuum_work_mem           &= nbsp;         | -1
 effective_cache_size           =                 | 98992128
 fsync               &= nbsp;                    =                | on
 full_page_writes           &nbs= p;                     &n= bsp;| on
 maintenance_work_mem           =          | 2097152
 shared_buffers            =                     &nbs= p;  | 64000
 shared_memory_type           &n= bsp;             | sysv
 temp_buffers             &= nbsp;                    =     | 4096
 wal_buffers             &n= bsp;                     =       | 2048
 work_mem              = ;                     &nb= sp;      | 119990

If you need additional parameters, please ask

SysV Error:
Feb 25 01:55:16 appdb-server01.production.aweberint.com postgres[34680]: FATAL:  could not create shared memory segment: Cannot allocate memory
DETAIL:  Failed system call was shmget(key=3D2359323, size=3D2063564800, 03600).
HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded your kernel's SHMALL parameter.  You might need to reconfigure the kernel with larger SHMALL.

Mmap Error:
FATAL:  could not map anonymous shared memory: Cannot allocate memory
HINT:  This error usually means that PostgreSQL's request for a shared memory segment exceeded available memory, swap space, or huge pages. To reduce the request size (currently 1635737600 bytes), reduce PostgreSQL's shared memory usage, perhaps by reducing shared_buffers or max_connections.

Thanks,


Chris Hoover
Senior DBA
AWeber.com
Cell: (803) 528-2269




--
Born in Arizona, moved to Babylonia.

--=_7208d730-0a89-4d40-b1a3-1d0e921801a5--