>>> "Walker, Chris" <christopher.wal...@hpe.com> schrieb am 19.10.2021 um 20:11 in Nachricht <ph0pr84mb1648ab8d30171fde0b5fb98197...@ph0pr84mb1648.namprd84.prod.outlook.com>
> That looks great … is that a string that an RA can set on failure? I’d love > to be able to communicate RA‑specific failure reasons back to crm_mon > consumers… What about: ocf_exit_reason "$0 $1 not implemented" Regards, Ulrich > Thanks! > Chris > > From: Users <users‑boun...@clusterlabs.org> > Date: Tuesday, October 19, 2021 at 1:17 PM > To: users@clusterlabs.org <users@clusterlabs.org> > Subject: [ClusterLabs] Coming in Pacemaker 2.1.2: better display of internal > failures > Hi all, > > I hope to get the first release candidate for Pacemaker 2.1.2 out in a > couple of weeks. > > One improvement will be in status displays (crm_mon, and the > crm_resource ‑‑force‑* options) for failed actions. > > OCF resource agents already have the ability to output an "exit reason" > for failures. These are displayed in the status, to give more detailed > information than just "error". > > Now, Pacemaker will set exit reasons for internal failures as well. > This includes problems such as an agent or systemd unit not being > installed, timeouts in Pacemaker communication as opposed to the agent > itself, an agent process being killed by a signal, etc. > > As an example, sending a kill ‑9 to a running agent monitor would > previously result in status with no explanation, requiring some log > diving to figure it out: > > * rsc1_monitor_60000 on node1 'error' (1): call=188, status='Error', > exitreason='', last‑rc‑change='Fri Sep 24 14:45:02 2021', queued=0ms, > exec=0ms > > Now, the exit reason will plainly say what happened: > > * rsc1_monitor_60000 on node1 'error' (1): call=188, status='Error', > exitreason='Process interrupted by signal', last‑rc‑change='Fri Sep 24 > 14:45:02 2021', queued=0ms, exec=0ms > > ‑‑ > Ken Gaillot <kgail...@redhat.com> > > _______________________________________________ > Manage your subscription: > https://lists.clusterlabs.org/mailman/listinfo/users<https://lists.clusterlab > s.org/mailman/listinfo/users> > > ClusterLabs home: https://www.clusterlabs.org/<https://www.clusterlabs.org/> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/