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 1rebkw-00CKH7-NE for pgsql-general@arkaria.postgresql.org; Mon, 26 Feb 2024 14:14:59 +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 1rebku-00DxbZ-Hd for pgsql-general@arkaria.postgresql.org; Mon, 26 Feb 2024 14:14:57 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rebku-00DxbQ-4j for pgsql-general@lists.postgresql.org; Mon, 26 Feb 2024 14:14:56 +0000 Received: from mail.arcict.com ([91.183.106.63] helo=arcict.com) by magus.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rebks-001B6W-68 for pgsql-general@lists.postgresql.org; Mon, 26 Feb 2024 14:14:56 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=simple/simple; d=arcict.com; s=cra20arc; bh=mcMcF/cKEY/cM9tcoy2K7Dm3yBwWlfgXHwCxutpVIIk=; h=Content-Transfer-Encoding:Content-Type:MIME-Version:Message-ID:Date:Subject :To:From; b=UiFC6gYJcD6RjE3Me5RuAoKygXEww89a8ww6i96qP5/zaGhhJBVgbqKC/mel+ffhb kWN88c7vfC867mBbfOhlu32sodR3YhVJJCAtzJjaFLFza2xVuJ9altSpypEUSX23CHxe5mni6mlkB d3p973n+7b2fV0Hjti3lMeyUMjWsw= Received: from [192.163.1.153] (HELO [169.254.239.202]) by arcict.com (CommuniGate Pro SMTP 6.3.18) with ESMTPS id 5945267 for pgsql-general@lists.postgresql.org; Mon, 26 Feb 2024 15:14:52 +0100 From: Nick Renders To: pgsql-general@lists.postgresql.org Subject: could not open file "global/pg_filenode.map": Operation not permitted Date: Mon, 26 Feb 2024 15:14:52 +0100 X-Mailer: MailMate (1.14r5964) Message-ID: <4D67E594-098F-4234-87D8-68F827AF2531@arcict.com> MIME-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk 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/p= g_filenode.map": Operation not permitted 2024-02-26 10:30:11.147 CET [90610] LOG: could not open file "postmaster= =2Epid": Operation not permitted; continuing anyway 2024-02-26 10:30:11.149 CET [63975] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:30:35.941 CET [63986] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:30:41.546 CET [63991] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:30:44.398 CET [63994] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:31:11.149 CET [90610] LOG: could not open file "postmaster= =2Epid": Operation not permitted; continuing anyway 2024-02-26 10:31:11.151 CET [64008] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:31:41.546 CET [64023] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:32:11.150 CET [90610] LOG: could not open file "postmaster= =2Epid": Operation not permitted; continuing anyway 2024-02-26 10:32:11.153 CET [64035] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:32:41.547 CET [64050] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:33:11.151 CET [90610] LOG: could not open file "postmaster= =2Epid": Operation not permitted; continuing anyway 2024-02-26 10:33:11.153 CET [64062] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted 2024-02-26 10:33:41.548 CET [64087] FATAL: could not open file "global/p= g_filenode.map": Operation not permitted This has happened 3 times over the last 2 weeks now, without any indicati= on 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 res= tart the service (pg_ctl restart). Once restarted, Popstgres runs fine again for a couple of days. 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