From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Matthias Apitz <guru(at)unixarea(dot)de> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: soft lockup - CPU#16 stuck for 3124s! [postmaster:2273] |
Date: | 2024-03-22 17:27:15 |
Message-ID: | 944273.1711128435@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Matthias Apitz <guru(at)unixarea(dot)de> writes:
> 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]
Sounds like failing hardware to me :-(
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Johnson | 2024-03-22 17:31:43 | Re: soft lockup - CPU#16 stuck for 3124s! [postmaster:2273] |
Previous Message | Matthias Apitz | 2024-03-22 17:12:28 | soft lockup - CPU#16 stuck for 3124s! [postmaster:2273] |