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

From Laurenz Albe
Subject Re: could not open file "global/pg_filenode.map": Operation not permitted
Date
Msg-id 07da1996f07145107f261157abceec77bb9011e9.camel@cybertec.at
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 Mon, 2024-03-11 at 11:11 +0100, Nick Renders wrote:
> We have several other machines with a similar setup, but this is the only server that has this issue.
>
> [...] Cluster A is actually a backup from another Postgres server that is restored on a
> daily basis via Barman. This means that we login remotely from the 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 not 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 throwing 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.

I don't know Barman, but with that incomplete description anybody will have
problems determining the cause.  For example, how are A and B connected?

Yours,
Laurenz Albe



pgsql-general by date:

Previous
From: Michał Kłeczek
Date:
Subject: Pgxs - How to reference another extension
Next
From: normandavis1990
Date:
Subject: Create a standby server