pg.ddx.io  pgsql-general@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Matthias Apitz <guru@unixarea.de>
To: pgsql-general@lists.postgresql.org
Subject: soft lockup - CPU#16 stuck for 3124s! [postmaster:2273]
Date: Fri, 22 Mar 2024 18:12:28 +0100
Message-ID: <Zf27/PpLpsE0fB+i@pureos> (raw)


We have a PostgreSQL 15.1 server in production at a customer for some
weeks (migrated from an older version) on SuSE SLES 15.

The customer is facing machine locks and before the Linux server does
not respond any more (not even on SSH, only power-cycle reset helps to
get it back), short before the fault a lot of messages are in
/var/log/messages of the content:

# grep watchdog: /var/log/messages
...
2024-03-22T13:11:32.056154+01:00 sunrise kernel: [327844.313048][   C25] watchdog: BUG: soft lockup - CPU#25 stuck for 3069s! [migration/25:166]
2024-03-22T13:12:28.056244+01:00 sunrise kernel: [327900.310267][   C16] watchdog: BUG: soft lockup - CPU#16 stuck for 3124s! [postmaster:2273]
2024-03-22T13:12:28.056340+01:00 sunrise kernel: [327900.311052][   C25] watchdog: BUG: soft lockup - CPU#25 stuck for 3121s! [migration/25:166]

Not all related to postmaster, but some of them. The server is in
principle idle, has a lot of CPUs and 32 GByte memory. To the PostgreSQL
server connect around 100 PostgreSQL clients, most of them by ESQL/C and
on localhost.

Looking around, I detected today that the WAL archiving was configured
wrong, leading to messages like (sorry for the German, but you will get
the meaning):

2024-03-22 13:11:50.838 CET [2630] LOG:  Archivbefehl ist fehlgeschlagen mit Statuscode 1
2024-03-22 13:11:50.838 CET [2630] DETAIL:  Der fehlgeschlagene Archivbefehl war: test ! -f /data/postgresql151/wal_archive/000000010000000000000001 && cp pg_wal/000000010000000000000001 /data/postgresql151/wal_archive/000000010000000000000001
cp: reguläre Datei '/data/postgresql151/wal_archive/000000010000000000000001' kann nicht angelegt werden: Datei oder Verzeichnis nicht gefunden
2024-03-22 13:11:51.842 CET [2630] LOG:  Archivbefehl ist fehlgeschlagen mit Statuscode 1
2024-03-22 13:11:51.842 CET [2630] DETAIL:  Der fehlgeschlagene Archivbefehl war: test ! -f /data/postgresql151/wal_archive/000000010000000000000001 && cp pg_wal/000000010000000000000001 /data/postgresql151/wal_archive/000000010000000000000001

The problem was that the directory /data/postgresql151/wal_archive was just
not created (and this for two weeks in production). Since it is now created
and also the backup of the WAL from there is in place, the problem of
the locks went away.

Any chance that the problem of the Pos server not being able to copy the
WALs could have caused the locks? Just to make sure that we hit the beast.

	matthias

-- 
Matthias Apitz, ✉ guru@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub





view thread (4+ messages)  latest in thread

Message-ID: <Zf27/PpLpsE0fB+i@pureos>
Permalink:  ../Zf27%2FPpLpsE0fB+i@pureos/
Also on:    postgresql.org/message-id/Zf27/PpLpsE0fB+i@pureos

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-general@postgresql.org
  Cc: guru@unixarea.de
  Subject: Re: soft lockup - CPU#16 stuck for 3124s! [postmaster:2273]
  In-Reply-To: <Zf27/PpLpsE0fB+i@pureos>
  References: <Zf27/PpLpsE0fB+i@pureos>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox