Hi Nick
On Thu, Apr 25, 2024 at 12:56 PM Nick Renders wrote:
> 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/pg_filenode.map": Operation not permitted
&
On Sat, Mar 23, 2024 at 3:01 AM Nick Renders 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.
BTW if you're running
On Thu, Apr 4, 2024 at 3:11 AM Nick Renders wrote:
> In the macOS Finder, when you show the Info (command+i) for an external drive
> (or any partition that is not the boot drive), there is a checkbox "Ignore
> ownership on this volume" in the Permissions section. I think it is by
> default
On 29 Mar 2024, at 4:25, Thomas Munro wrote:
>
> I don't have any specific ideas and I have no idea what "ignore
> ownership" means ... what kind of filesystem is running on it? For
> the simple SSD, is it directly connected, running a normal Apple APFS
> filesystem, or something more
On Fri, Mar 29, 2024 at 4:47 AM Nick Renders wrote:
> Looking at the 2 machines that are having this issue (and the others that
> don't), I think it is somehow related to the following setup:
> - macOS Sonoma (14.4 and 14.4.1)
> - data directory on an external drive
>
> That external drive (a
-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]
-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.3
lobal/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 p
ive database in
the Data directory. 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
202
Greetings,
* Nick Renders (postg...@arcict.com) wrote:
> > ...run them under different users on the system.
>
> Are you referring to the "postgres" user / role? Does that also mean setting
> up 2 postgres installation directories?
Yes, two separate MacOS user accounts is what I was suggesting.
hough the issue is most likely related to
the script, it does not cause it every time.
I'm not seeing anything obvious, caveat I'm on my first cup of coffee.
From your first post:
2024-02-26 10:29:41.580 CET [63962] FATAL: could not open file
"global/pg_filenode.map": Operation n
On 11 Mar 2024, at 16:04, Adrian Klaver wrote:
> On 3/11/24 03:11, Nick Renders wrote:
>> 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
On 3/11/24 03:11, Nick Renders wrote:
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,
Greetings,
* Nick Renders (postg...@arcict.com) wrote:
> The one thing different about this machine however, is that it runs 2
> instances of Postgres:
> - cluster A on port 165
> - cluster B on port 164
> Cluster A is actually a backup from another Postgres server that is restored
> on a daily
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
urenz 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: could not open file
>> "global/pg_filenode.map": Operation not permi
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: could not open file
> "global/pg_filenode.map": Operation not permitted
> 2024-02-26 10:30:11.14
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/pg_filenode.map": Operation not permitted
2024-02-26 10:30:11.147 CET [90610] LOG: could not open file "postmaster.pid":
Ope
18 matches
Mail list logo
