Public issue detail

Runaway CPU investigation for postgres: file not found retry at WaitEventSetWait

postgres is stuck in a likely file not found retry loop: 28.57% of sampled CPU passed through WaitEventSetWait, with repeated thread backtraces show 1 thread(s) around 0x00007f7f64417687 in __GI__IO_flush_all () from target:<path>.

highscore: 106reports: 1

Last seen: 2026-09-28 15:51 UTC. Public JSON: /v1/issues/01a0e840-352c-74f0-a516-88ac9cf0a1d0

Technical snapshot

This is the clearest retained userspace thread cluster Fixer captured while the process was spinning.

Representative thread backtrace

  • Command: /usr/lib/postgresql/16/bin/postgres -D /tmp/postgis-pg16.4DcJNM/data -F -h -p 30196 -k /tmp/postgis-pg16.4DcJNM/socket -c fsync=off -c full_page_writes=off -c synchronous_commit=off
  • Why Fixer classified it this way: The trace keeps retrying file lookups that fail with ENOENT, which suggests a missing-file retry loop.
  • Thread summary: thread backtraces show 1 thread(s) around 0x00007f7f64417687 in __GI__IO_flush_all () from target:<path>
  • Contention signals: event-loop-wakeups, gdb-stderr: gdb: warning: Couldn't determine a path for the index cache directory. warning: Target and debugger are in different PID namespaces; thread lists and other data are likely unreliable. Connect to gdbserver inside the container. warning: Expected absolute pathname for libpthread in the inferior, but got target:<path> warning: Unable to find libthread_db matching inferior's thread library, thread debugging will not be available.
  • Repeated loop: pread64 -> pread64 -> pread64
  • Top syscalls: pread64 x2248, mmap x310, read x199, close x104
  • Kernel: 7.1.8+deb14.1-amd64
  • Distribution: debian
0x00007f7f64417687 in __GI__IO_flush_all () from target:<path>
0x00007f7f644176ad in __GI__IO_flush_all () from target:<path>
0x00007f7f64498a6d in epoll_wait () from target:<path>
0x00005635d8c13f5b in WaitEventSetWait ()
0x00005635d8bac745 in ?? ()
0x00005635d8baf47c in PostmasterMain ()
0x00005635d88d44ec in main ()

Possible duplicates

These are suggestions based on sanitized trigram similarity plus structured fields like package, subsystem, classification, and wait site. They are not auto-merged.

Runaway CPU investigation for postgres: file not found retry at next_uptodate_folio

possible duplicate

postgres is stuck in a likely file not found retry loop: 4.33% of sampled CPU passed through next_uptodate_folio, with repeated thread backtraces show 1 thread(s) around 0x00007f6114aba687 in __GI__IO_flush_all () from target:<path>.

highpackage: postgresql-14source: linuxscore: 106reports: 3successful triagesimilarity: 99%

Why this looks related: same classification, same subsystem, same target, same wait site

Last seen: 2026-10-12 08:43 UTC. Public page: /issues/019d3a17-b958-7a60-86fd-5304e697f42c. Public JSON: /v1/issues/019d3a17-b958-7a60-86fd-5304e697f42c

Runaway CPU investigation for postgres: file not found retry at _dl_map_new_object

possible duplicate

postgres is stuck in a likely file not found retry loop: 1.58% of sampled CPU passed through _dl_map_new_object, with repeated thread backtraces show 1 thread(s) around 0x00007fb038f9c687 in __GI__IO_flush_all () from target:<path>.

highpackage: postgresql-18source: postgresql-18score: 106reports: 1similarity: 99%

Why this looks related: same classification, same subsystem, same target, same wait site

Last seen: 2026-10-21 03:01 UTC. Public page: /issues/019f9e46-ed87-7693-a004-3c6b0b260a51. Public JSON: /v1/issues/019f9e46-ed87-7693-a004-3c6b0b260a51

Runaway CPU investigation for postgres: file not found retry at malloc

possible duplicate

postgres is stuck in a likely file not found retry loop: 1.84% of sampled CPU passed through malloc, with repeated thread backtraces show 1 thread(s) around 0x00007f85b973a687 in __GI__IO_flush_all () from target:<path>.

highscore: 106reports: 1similarity: 99%

Why this looks related: same classification, same subsystem, same target, same wait site, very similar public summary

Last seen: 2026-10-13 06:02 UTC. Public page: /issues/01a133a7-70dc-73b3-b590-4cd62ec20ac9. Public JSON: /v1/issues/01a133a7-70dc-73b3-b590-4cd62ec20ac9

Runaway CPU investigation for postgres: file not found retry at XLogNeedsFlush

possible duplicate

postgres is stuck in a likely file not found retry loop: 2.27% of sampled CPU passed through XLogNeedsFlush, with repeated thread backtraces show 1 thread(s) around 0x00007f8ccb7fc687 in __GI__IO_flush_all () from target:<path>.

highscore: 106reports: 1similarity: 99%

Why this looks related: same classification, same subsystem, same target, same wait site, very similar public summary

Last seen: 2026-09-30 03:07 UTC. Public page: /issues/01a0ee1d-0385-77b3-8bf7-d516edc62f39. Public JSON: /v1/issues/01a0ee1d-0385-77b3-8bf7-d516edc62f39

Runaway CPU investigation for postgres: file not found retry at pglz_decompress

possible duplicate

postgres is stuck in a likely file not found retry loop: 3.77% of sampled CPU passed through pglz_decompress, with repeated thread backtraces show 1 thread(s) around 0x00007f92e0a4e687 in __GI__IO_flush_all () from target:<path>.

highscore: 106reports: 1similarity: 92%

Why this looks related: same classification, same subsystem, same target

Last seen: 2026-10-13 05:43 UTC. Public page: /issues/019fa653-58fc-7d62-b84f-1f51afcbf926. Public JSON: /v1/issues/019fa653-58fc-7d62-b84f-1f51afcbf926

Runaway CPU investigation for postgres: file not found retry at unresolved offset in postgres

possible duplicate

postgres is stuck in a likely file not found retry loop: 3.98% of sampled CPU passed through unresolved offset, with repeated thread backtraces show 1 thread(s) around 0x00007f7805be2687 in __GI__IO_flush_all () from target:<path>.

highscore: 106reports: 1similarity: 92%

Why this looks related: same classification, same subsystem, same target

Last seen: 2026-10-13 06:22 UTC. Public page: /issues/019f77a0-05cc-7ca2-84d1-d756b2e2db54. Public JSON: /v1/issues/019f77a0-05cc-7ca2-84d1-d756b2e2db54

Published attempts

No public attempts have been published for this issue yet.

Quarantine stays on by default so the public queue is harder to spam.