Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzu6U-007o3T-92 for pgsql-general@arkaria.postgresql.org; Thu, 25 Apr 2024 08:05:14 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rzu6S-004TZO-PN for pgsql-general@arkaria.postgresql.org; Thu, 25 Apr 2024 08:05:12 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rzu6S-004TZF-AK for pgsql-general@lists.postgresql.org; Thu, 25 Apr 2024 08:05:12 +0000 Received: from mail-ua1-x92e.google.com ([2607:f8b0:4864:20::92e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rzu6P-004YQq-Of for pgsql-general@lists.postgresql.org; Thu, 25 Apr 2024 08:05:11 +0000 Received: by mail-ua1-x92e.google.com with SMTP id a1e0cc1a2514c-7eb9cb7b657so267678241.1 for ; Thu, 25 Apr 2024 01:05:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1714032309; x=1714637109; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=XabhVPxzwXmhudmgw3/E8EzbeIO83DwTo0G1uXO6fvs=; b=Orx720ShSh0bWcjtOoyZAcChVEIO2/QZzLLwy1aZyq63R7KA767n/0SBK74QQKrqls 8dIoyN9H0WtLO1dDmDikTK3tcNMds95GGZSxbKH6RPXOoj0PzMHrYJAl8tU27BkKfeQx UtuumcwV7DOUljxS4vwbj3gLSPFqWf919o2bcvLVXBvWq4lKM2DyihyA/Ppu5Q/wV8PI gCKjUXOr5kngiCIh4aVwVGeqnT+56J7ADg85fxRECx7TfxTICdyb3UMlO1BwWC4ivbAq uKE0a10v3XfxJh75q8eQepCTvGT7jCtgRKeTzoUyM3gItFAIW8jZMsgYo23c1zRaq4Tr MY8w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1714032309; x=1714637109; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=XabhVPxzwXmhudmgw3/E8EzbeIO83DwTo0G1uXO6fvs=; b=Cc/Ul/kb799pbaFzP0ADKRIFqKOACCNwXsDj+i1GEoiC7+8YJVX88ZurMBBJ2Gmf9+ 4wv/MkPogeoqr56jWGfYy4fwhK94awMyLFrnpA+TixaXLIw+uhAup+WiwSZC5UAqwwgH w4o85BiuLPwitBjjlpelYOFtA6peEuobUYgQyN8na5rjfHgl8ej0hWc4VFPhyMPMFsGW 7QZQmkJ8hwojQs11jACE0WEkEYsgeVI8NxWMJWka0oYi91O/pmb5M+6l/DSrYmstdgZA 7YT07gu8DdMTFX6O65nJtALdvFmeU3u2DyZlHwpART5GSW5aDQ8npxfvMW1ZhyEuWtbQ mF2w== X-Gm-Message-State: AOJu0Yy8WHvP/NxR7l8jTODNhowLkXkUQ/BT1z7WL0c4rNHmIU8fOZiN ykIGm3q1qZlJlfMxZOCZ88B25q2olgEKtu+xk/00qTnoTQiw1466HzseCTzovHqLtByixE8VtG5 6SFPtiUsSEikeUhZWswk45KQ65j9T/yPl8IM= X-Google-Smtp-Source: AGHT+IG6RLFnbk+rp2owEziZnfVi464rr1E3KTpYFGRQOfwFXeLeYr/uk0XbUw0TDqjhnG/8C4h289qp+OYiZKkZAXM= X-Received: by 2002:a05:6102:2336:b0:47c:f0d:3bb0 with SMTP id b22-20020a056102233600b0047c0f0d3bb0mr3539318vsa.27.1714032308791; Thu, 25 Apr 2024 01:05:08 -0700 (PDT) MIME-Version: 1.0 References: <4D67E594-098F-4234-87D8-68F827AF2531@arcict.com> In-Reply-To: <4D67E594-098F-4234-87D8-68F827AF2531@arcict.com> From: Kashif Zeeshan Date: Thu, 25 Apr 2024 13:04:57 +0500 Message-ID: Subject: Re: could not open file "global/pg_filenode.map": Operation not permitted To: Nick Renders Cc: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e6327c0616e73e79" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e6327c0616e73e79 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Nick On Thu, Apr 25, 2024 at 12:56=E2=80=AFPM Nick Renders = wrote: > Hello, > > We have a Postgres server that intermittently logs the following: > > 2024-02-26 10:29:41.580 CET [63962] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:30:11.147 CET [90610] LOG: could not open file > "postmaster.pid": Operation not permitted; continuing anyway > 2024-02-26 10:30:11.149 CET [63975] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:30:35.941 CET [63986] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:30:41.546 CET [63991] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:30:44.398 CET [63994] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:31:11.149 CET [90610] LOG: could not open file > "postmaster.pid": Operation not permitted; continuing anyway > 2024-02-26 10:31:11.151 CET [64008] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:31:41.546 CET [64023] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:32:11.150 CET [90610] LOG: could not open file > "postmaster.pid": Operation not permitted; continuing anyway > 2024-02-26 10:32:11.153 CET [64035] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:32:41.547 CET [64050] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:33:11.151 CET [90610] LOG: could not open file > "postmaster.pid": Operation not permitted; continuing anyway > 2024-02-26 10:33:11.153 CET [64062] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > 2024-02-26 10:33:41.548 CET [64087] FATAL: could not open file > "global/pg_filenode.map": Operation not permitted > > > This has happened 3 times over the last 2 weeks now, without any > indication what caused it. > The privileges of those 2 files are all in order. > When this happens, the server is no longer accessible, and we need to > restart the service (pg_ctl restart). > Once restarted, Popstgres runs fine again for a couple of days. > Hi This issue seems to be related to the permission issue, please check your script if it's changing the permissions. Regards Kashif Zeeshan Bitnine Global > > We are running PostgreSQL 16.2 on macOS 14.3.1. > > Any idea what might be causing this issue, or how to resolve it? > > > Best regards, > > Nick Renders > > > > > --000000000000e6327c0616e73e79 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi=C2=A0Nick

On Thu, Apr 25, 2024 at 12:56= =E2=80=AFPM Nick Renders <postgre= s@arcict.com> wrote:
Hello,

We have a Postgres server that intermittently logs the following:

2024-02-26 10:29:41.580 CET [63962] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:30:11.147 CET [90610] LOG:=C2=A0 could not open file "po= stmaster.pid": Operation not permitted; continuing anyway
2024-02-26 10:30:11.149 CET [63975] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:30:35.941 CET [63986] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:30:41.546 CET [63991] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:30:44.398 CET [63994] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:31:11.149 CET [90610] LOG:=C2=A0 could not open file "po= stmaster.pid": Operation not permitted; continuing anyway
2024-02-26 10:31:11.151 CET [64008] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:31:41.546 CET [64023] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:32:11.150 CET [90610] LOG:=C2=A0 could not open file "po= stmaster.pid": Operation not permitted; continuing anyway
2024-02-26 10:32:11.153 CET [64035] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:32:41.547 CET [64050] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:33:11.151 CET [90610] LOG:=C2=A0 could not open file "po= stmaster.pid": Operation not permitted; continuing anyway
2024-02-26 10:33:11.153 CET [64062] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted
2024-02-26 10:33:41.548 CET [64087] FATAL:=C2=A0 could not open file "= global/pg_filenode.map": Operation not permitted


This has happened 3 times over the last 2 weeks now, without any indication= what caused it.
The privileges of those 2 files are all in order.
When this happens, the server is no longer accessible, and we need to resta= rt the service (pg_ctl restart).
Once restarted, Popstgres runs fine again for a couple of days.
Hi
=C2=A0
This issue seems to be related to t= he permission issue, please check your script if it's changing the perm= issions.
=C2=A0
Regards
Kashif Zeeshan
<= div>Bitnine Global
=

We are running PostgreSQL 16.2 on macOS 14.3.1.

Any idea what might be causing this issue, or how to resolve it?


Best regards,

Nick Renders




--000000000000e6327c0616e73e79--