Re: [ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?

2022-06-15 Thread Klaus Wenninger
On Wed, Jun 15, 2022 at 8:32 AM Ulrich Windl wrote: > > >>> Ulrich Windl schrieb am 14.06.2022 um 15:53 in Nachricht <62A892F0.174 : > >>> 161 : > 60728>: > > ... > > Yes it's odd, but isn't the cluster just to protect us from odd situations? > > ;-) > > I have more odd stuff: > Jun 14 20:40:09

[ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?

2022-06-15 Thread Ulrich Windl
>>> Ulrich Windl schrieb am 14.06.2022 um 15:53 in Nachricht <62A892F0.174 : >>> 161 : 60728>: ... > Yes it's odd, but isn't the cluster just to protect us from odd situations? > ;-) I have more odd stuff: Jun 14 20:40:09 rksaph18 pacemaker-execd[7020]: warning:

Re: [ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?

2022-06-14 Thread Ken Gaillot
On Tue, 2022-06-14 at 15:53 +0200, Ulrich Windl wrote: > > > > Ken Gaillot schrieb am 14.06.2022 um > > > > 15:49 in > Nachricht > : > > On Tue, 2022‑06‑14 at 14:36 +0200, Ulrich Windl wrote: > > > Hi! > > > > > > I had a case where a VirtualDomain monitor operation ended in a > > > core > > >

[ClusterLabs] Antw: [EXT] Re: Why not retry a monitor (pacemaker‑execd) that got a segmentation fault?

2022-06-14 Thread Ulrich Windl
>>> Ken Gaillot schrieb am 14.06.2022 um 15:49 in Nachricht : > On Tue, 2022‑06‑14 at 14:36 +0200, Ulrich Windl wrote: >> Hi! >> >> I had a case where a VirtualDomain monitor operation ended in a core >> dump (actually it was pacemaker‑execd, but it counted as "monitor" >> operation), and the