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

From: Torsten Krah <krah(dot)tm(at)gmail(dot)com>
To: pgsql-general(at)lists(dot)postgresql(dot)org
Subject: could not open file "base/XX/XX": Interrupted system call
Date: 2023-09-20 08:49:22
Message-ID: c15876f7330705cc5e1ba7935b4af8ed1367fd47.camel@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

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, compiled by 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

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2023-09-20 11:11:59 Re: could not open file "base/XX/XX": Interrupted system call
Previous Message Александр Петросян (web) 2023-09-20 05:30:08 debugger from superuser only.... why?