| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Nick Renders <postgres(at)arcict(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: could not open file "global/pg_filenode.map": Operation not permitted |
| Date: | 2024-02-26 15:29:59 |
| Message-ID: | d947712004aa39633639bd5a23d6a6d6b6b2665a.camel@cybertec.at |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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.147 CET [90610] LOG: could not open file "postmaster.pid": Operation not permitted; continuing anyway
>
> This has happened 3 times over the last 2 weeks now, without any indication 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thiemo Kellner | 2024-02-26 15:51:54 | pPL/pgSQL restriction on characters for copying types? |
| Previous Message | Nick Renders | 2024-02-26 14:14:52 | could not open file "global/pg_filenode.map": Operation not permitted |