Re: could not open file "global/pg_filenode.map": Operation not permitted - Mailing list pgsql-general

From Adrian Klaver
Subject Re: could not open file "global/pg_filenode.map": Operation not permitted
Date
Msg-id 57cfcbe1-1be6-4056-b59c-014086857761@aklaver.com
Whole thread Raw
In response to Re: could not open file "global/pg_filenode.map": Operation not permitted  (Nick Renders <postgres@arcict.com>)
List pgsql-general
On 3/22/24 07:01, Nick Renders wrote:
> On 13 Mar 2024, at 12:35, Stephen Frost wrote:

> We now have a second machine with this issue: it is an Intel Mac mini running macOS Sonoma (14.4) and PostgreSQL
16.2.
> This one only has a single Data directory, so there are no multiple instances running.
> 
> I installed Postgres yesterday and restored a copy from our live database in the Data directory. The Postgres process
startedup without problems, but after 40 minutes it started throwing the same errors in the log:
 
> 
>     2024-03-21 11:49:27.410 CET [1655] FATAL:  could not open file "global/pg_filenode.map": Operation not permitted
>     2024-03-21 11:49:46.955 CET [1760] FATAL:  could not open file "global/pg_filenode.map": Operation not permitted
>     2024-03-21 11:50:07.398 CET [965] LOG:  could not open file "postmaster.pid": Operation not permitted; continuing
anyway
> 
> I stopped and started the process, and it continued working again until around 21:20, when the issue popped up again.
Iwasn't doing anything on the machine at that time, so I have no idea what might have triggered it.
 

Have you looked at the OS system logs?

> 
> Is there perhaps some feature that I can enable that logs which processes use these 2 files?
> 
> Thanks,
> 
> Nick Renders
> 
> 

-- 
Adrian Klaver
adrian.klaver@aklaver.com




pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: pg_locks-exclusivelock for select queries
Next
From: Alban Hertroys
Date:
Subject: Re: could not open file "global/pg_filenode.map": Operation not permitted