From: Nick Renders <postgres@arcict.com>
To: pgsql-general@lists.postgresql.org
Subject: Re: could not open file "global/pg_filenode.map": Operation not
 permitted
Date: Mon, 11 Mar 2024 11:11:09 +0100
Message-ID: <2E2F11F8-718A-4E6A-81E0-4F5CC1F1273A@arcict.com>
In-Reply-To: <d947712004aa39633639bd5a23d6a6d6b6b2665a.camel@cybertec.at>
References: <4D67E594-098F-4234-87D8-68F827AF2531@arcict.com>
 <d947712004aa39633639bd5a23d6a6d6b6b2665a.camel@cybertec.at>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/2E2F11F8-718A-4E6A-81E0-4F5CC1F1273A%40arcict.com>
Precedence: bulk

Thank you for your reply Laurenz.
I don't think it is related to any third party security software. We have=
 several other machines with a similar setup, but this is the only server=
 that has this issue.

The one thing different about this machine however, is that it runs 2 ins=
tances of Postgres:
- cluster A on port 165
- cluster B on port 164
Cluster A is actually a backup from another Postgres server that is resto=
red on a daily basis via Barman. This means that we login remotely from t=
he Barman server over SSH, stop cluster A's service (port 165), clear the=
 Data folder, restore the latest back into the Data folder, and start up =
the service again.
Cluster B's Data and service (port 164) remain untouched during all this =
time. This is the cluster that experiences the intermittent "operation no=
t permitted" issue.

Over the past 2 weeks, I have suspended our restore script and the issue =
did not occur.
I have just performed another restore on cluster A and now cluster B is t=
hrowing errors in the log again.

Any idea why this is happening? It does not occur with every restore, but=
 it seems to be related anyway.

Thanks,

Nick Renders


On 26 Feb 2024, at 16:29, Laurenz Albe wrote:

> On Mon, 2024-02-26 at 15:14 +0100, Nick Renders wrote:
>> 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
>>
>> This has happened 3 times over the last 2 weeks now, without any indic=
ation 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.
>>
>> We are running PostgreSQL 16.2 on macOS 14.3.1.
>
> Perhaps that is some kind of virus checker or something else that locks=
 files.
>
> Yours,
> Laurenz Albe