MIME-Version: 1.0
References: <4D67E594-098F-4234-87D8-68F827AF2531@arcict.com>
 <d947712004aa39633639bd5a23d6a6d6b6b2665a.camel@cybertec.at>
 <2E2F11F8-718A-4E6A-81E0-4F5CC1F1273A@arcict.com> <a08f7e54-0a6f-466b-b3fc-08165076c605@aklaver.com>
 <19556056-40E7-4FA3-A2A1-0A345AEBFD9E@arcict.com> <ZfGPfsckcxYLtagw@tamriel.snowman.net>
 <76FAACAC-F64A-43DA-BDBF-340A40C47045@arcict.com>
In-Reply-To: <76FAACAC-F64A-43DA-BDBF-340A40C47045@arcict.com>
From: Alban Hertroys <haramrae@gmail.com>
Date: Fri, 22 Mar 2024 17:00:43 +0100
Message-ID: <CAF-3MvOKqiKbcG-1M=ZeW-O99PeUJ0THPm8DWrRKcTT263GtAg@mail.gmail.com>
Subject: Re: could not open file "global/pg_filenode.map": Operation not permitted
To: Nick Renders <postgres@arcict.com>
Cc: pgsql-general@lists.postgresql.org
Content-Type: multipart/alternative; boundary="000000000000c3d352061441ed3b"
Archived-At: <https://www.postgresql.org/message-id/CAF-3MvOKqiKbcG-1M%3DZeW-O99PeUJ0THPm8DWrRKcTT263GtAg%40mail.gmail.com>
Precedence: bulk

--000000000000c3d352061441ed3b
Content-Type: text/plain; charset="UTF-8"

On Fri, 22 Mar 2024 at 15:01, Nick Renders <postgres@arcict.com> 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 don't think that having a single Data directory prevents multiple
instances from running. That's more of a matter of how often pg_ctl was
called with the start command for that particular data directory.


> I installed Postgres yesterday and restored a copy from our live database
> in the Data directory.


How did you restore that copy? Was that a file-based copy perhaps? Your
files may have incorrect owners or permissions in that case.


> The Postgres process started up 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
>

It's possible that some other process put a lock on these files. Spotlight
perhaps? Or TimeMachine?


> I stopped and started the process, and it continued working again until
> around 21:20, when the issue popped up again. I wasn't doing anything on
> the machine at that time, so I have no idea what might have triggered it.
>
> Is there perhaps some feature that I can enable that logs which processes
> use these 2 files?
>

IIRC, MacOS comes shipped with the lsof command, which will tell you which
processes have a given file open. See man lsof.

-- 
If you can't see the forest for the trees,
Cut the trees and you'll see there is no forest.

--000000000000c3d352061441ed3b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr"></div><br><div class=3D"gmail_quote"><div=
 dir=3D"ltr" class=3D"gmail_attr">On Fri, 22 Mar 2024 at 15:01, Nick Render=
s &lt;<a href=3D"mailto:postgres@arcict.com">postgres@arcict.com</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
We now have a second machine with this issue: it is an Intel Mac mini runni=
ng macOS Sonoma (14.4) and PostgreSQL 16.2.<br>
This one only has a single Data directory, so there are no multiple instanc=
es running.<br></blockquote><div><br></div><div>I don&#39;t think that havi=
ng a single Data directory prevents multiple instances from running. That&#=
39;s more of a matter of how often pg_ctl was called with the start command=
 for that particular data directory.<br></div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex">
I installed Postgres yesterday and restored a copy from our live database i=
n the Data directory.</blockquote><div><br></div><div>How did you restore t=
hat copy? Was that a file-based copy perhaps? Your files may have incorrect=
 owners or permissions in that case.<br></div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"> The Postgres process started up with=
out problems, but after 40 minutes it started throwing the same errors in t=
he log:<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 2024-03-21 11:49:27.410 CET [1655] FATAL:=C2=A0=
 could not open file &quot;global/pg_filenode.map&quot;: Operation not perm=
itted<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 2024-03-21 11:49:46.955 CET [1760] FATAL:=C2=A0=
 could not open file &quot;global/pg_filenode.map&quot;: Operation not perm=
itted<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 2024-03-21 11:50:07.398 CET [965] LOG:=C2=A0 co=
uld not open file &quot;postmaster.pid&quot;: Operation not permitted; cont=
inuing anyway<br></blockquote><div><br></div><div>It&#39;s possible that so=
me other process put a lock on these files. Spotlight perhaps? Or TimeMachi=
ne?<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex">
I stopped and started the process, and it continued working again until aro=
und 21:20, when the issue popped up again. I wasn&#39;t doing anything on t=
he machine at that time, so I have no idea what might have triggered it.<br=
>
<br>
Is there perhaps some feature that I can enable that logs which processes u=
se these 2 files?
<br>
</blockquote></div><div><br></div><div>IIRC, MacOS comes shipped with the l=
sof command, which will tell you which processes have a given file open. Se=
e man lsof.<br></div><br><span class=3D"gmail_signature_prefix">-- </span><=
br><div dir=3D"ltr" class=3D"gmail_signature">If you can&#39;t see the fore=
st for the trees,<br>Cut the trees and you&#39;ll see there is no forest.<b=
r></div></div>

--000000000000c3d352061441ed3b--