Postgres Pro
Downloads
Home   >   mailing lists

Thread: could not open file "base/XX/XX": Interrupted system call

could not open file "base/XX/XX": Interrupted system call

From
Torsten Krah
Date:
Hi,

I am running the postgres docker image with that version:

2023-09-20 10:36:32.478 CEST [1] LOG:  starting PostgreSQL 13.12 (Debian 13.12-1.pgdg120+1) on x86_64-pc-linux-gnu,
compiledby gcc (Debian 12.2.0-14) 12.2.0, 64-bit 
2023-09-20 10:36:32.564 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2023-09-20 10:36:32.564 CEST [1] LOG:  listening on IPv6 address "::", port 5432

And this is happening for some queries:

2023-09-20 10:38:25.076 CEST [47] ERROR:  could not open file "base/16386/17328": Interrupted system call
2023-09-20 10:38:41.897 CEST [49] ERROR:  could not open file "base/16386/68359": Interrupted system call

I can enter the container and view the files above with e.g. strings
$file | less and I can create a md5sum from that file without an error.

What can I do about that EINTR on open, how to fix it?

The host (6.1.53-060153-generic #202309130436 SMP PREEMPT_DYNAMIC) and
the docker daemon (Version: 24.0.6) do have nothing suspicious in there
dmesg / logs.

Anyone an idea how to debug / progress with that one?

Torsten

Re: could not open file "base/XX/XX": Interrupted system call

From
Laurenz Albe
Date:
On Wed, 2023-09-20 at 10:49 +0200, Torsten Krah wrote:
> I am running the postgres docker image with that version:
>
> 2023-09-20 10:36:32.478 CEST [1] LOG:  starting PostgreSQL 13.12 (Debian 13.12-1.pgdg120+1) on x86_64-pc-linux-gnu,
compiledby gcc (Debian 12.2.0-14) 12.2.0, 64-bit 
> 2023-09-20 10:36:32.564 CEST [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
> 2023-09-20 10:36:32.564 CEST [1] LOG:  listening on IPv6 address "::", port 5432
>
> And this is happening for some queries:
>
> 2023-09-20 10:38:25.076 CEST [47] ERROR:  could not open file "base/16386/17328": Interrupted system call
> 2023-09-20 10:38:41.897 CEST [49] ERROR:  could not open file "base/16386/68359": Interrupted system call

Is that an NFS mount?  What are the mount options?

Yours,
Laurenz Albe

Re: could not open file "base/XX/XX": Interrupted system call

From
Torsten Krah
Date:
Am Mittwoch, dem 20.09.2023 um 13:11 +0200 schrieb Laurenz Albe:
> Is that an NFS mount?  What are the mount options?
>
> Yours,
> Laurenz Albe

No mount at all.

Just the docker container filesystem using the overlay2 storage driver,
there is nothing externally mounted in that container, the data is
already in the image (via docker COPY) from which the container gets
created (and that data directory was created in the image build process
via pg_restore from the dump file).

The whole container / image just involves overlay2 fs which itself is
sitting on ext4.

Torsten