Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Ken Gaillot
On Fri, 2022-10-21 at 13:05 +0200, Lentes, Bernd wrote: > - On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@redhat.com > wrote: > > > This turned out to be interesting. > > > > In the first case, the resource history contains a start action and > > a > > recurring monitor. The parameters to

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Ken Gaillot
t released with 2.1.5-rc1, to ensure resources are restarted if a parameter changes that was specified on an operation rather than the resource itself. SUSE may have backported that already. > > Klaus > > From: Users on behalf of Lentes, > > Bernd > > Sent: Monday, October 24, 20

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Klaus Wenninger
t have 'fixed' the issue. Maybe Ken can still tell from the top of his mind. Klaus > >- > > -- > *From:* Users on behalf of Lentes, Bernd < > bernd.len...@helmholtz-muenchen.de> > *Sent:* Monday, October 24, 2022 4:46 PM > *To:* Pacema

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Xin Liang via Users
/untrace * From: Users on behalf of Lentes, Bernd Sent: Monday, October 24, 2022 4:46 PM To: Pacemaker ML Subject: Re: [ClusterLabs] crm resource trace - On 24 Oct, 2022, at 10:08, Klaus Wenninger kwenn...@redhat.com wrote: > On Mon, Oct 24, 2022 at 9:50

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Klaus Wenninger
On Mon, Oct 24, 2022 at 10:46 AM Lentes, Bernd < bernd.len...@helmholtz-muenchen.de> wrote: > > - On 24 Oct, 2022, at 10:08, Klaus Wenninger kwenn...@redhat.com > wrote: > > > On Mon, Oct 24, 2022 at 9:50 AM Xin Liang via Users < [ > > mailto:users@clusterlabs.org | users@clusterlabs.org ] >

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Lentes, Bernd
- On 24 Oct, 2022, at 10:08, Klaus Wenninger kwenn...@redhat.com wrote: > On Mon, Oct 24, 2022 at 9:50 AM Xin Liang via Users < [ > mailto:users@clusterlabs.org | users@clusterlabs.org ] > wrote: > Did you try a cleanup in between? When i do a cleanup before trace/untrace the resource is

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Klaus Wenninger
when trace/untrace resource > > > Regards, > Xin > > > -- > *From:* Users on behalf of Xin Liang via > Users > *Sent:* Monday, October 24, 2022 10:29 AM > *To:* Cluster Labs - All topics related to open-source clustering > welcomed > *Cc:* Xin Liang > *Subje

Re: [ClusterLabs] crm resource trace

2022-10-24 Thread Xin Liang via Users
cs related to open-source clustering welcomed Cc: Xin Liang Subject: Re: [ClusterLabs] crm resource trace Hi Bernd, On which version you're running for crmsh and SLE? Regards, Xin From: Users on behalf of Lentes, Bernd Sent: Monday, October 17, 2022 6:43 PM To:

Re: [ClusterLabs] crm resource trace

2022-10-23 Thread Xin Liang via Users
Hi Bernd, On which version you're running for crmsh and SLE? Regards, Xin From: Users on behalf of Lentes, Bernd Sent: Monday, October 17, 2022 6:43 PM To: Pacemaker ML Subject: Re: [ClusterLabs] crm resource trace Hi, i try to find out why

Re: [ClusterLabs] crm resource trace

2022-10-21 Thread Lentes, Bernd
- On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@redhat.com wrote: > This turned out to be interesting. > > In the first case, the resource history contains a start action and a > recurring monitor. The parameters to both change, so the resource > requires a restart. > > In the second

Re: [ClusterLabs] crm resource trace

2022-10-18 Thread Ken Gaillot
On Tue, 2022-10-18 at 20:48 +0200, Lentes, Bernd wrote: > - On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@redhat.com > wrote: > > > This turned out to be interesting. > > > > In the first case, the resource history contains a start action and > > a > > recurring monitor. The parameters to

Re: [ClusterLabs] crm resource trace

2022-10-18 Thread Lentes, Bernd
- On 17 Oct, 2022, at 21:41, Ken Gaillot kgail...@redhat.com wrote: > This turned out to be interesting. > > In the first case, the resource history contains a start action and a > recurring monitor. The parameters to both change, so the resource > requires a restart. > > In the second

Re: [ClusterLabs] crm resource trace

2022-10-18 Thread Klaus Wenninger
On Mon, Oct 17, 2022 at 9:42 PM Ken Gaillot wrote: > This turned out to be interesting. > > In the first case, the resource history contains a start action and a > recurring monitor. The parameters to both change, so the resource > requires a restart. > > In the second case, the resource's

Re: [ClusterLabs] crm resource trace

2022-10-17 Thread Ken Gaillot
This turned out to be interesting. In the first case, the resource history contains a start action and a recurring monitor. The parameters to both change, so the resource requires a restart. In the second case, the resource's history was apparently cleaned at some point, so the cluster re-probed

Re: [ClusterLabs] crm resource trace

2022-10-17 Thread Ken Gaillot
On Mon, 2022-10-17 at 12:43 +0200, Lentes, Bernd wrote: The section you highlighted does contain the key difference: > Oct 14 19:05:52 [26000] ha-idg-1pengine: info: > rsc_action_digest_cmp: Parameters to vm-genetrap_start_0 on ha-idg- > 1 changed: was e2eeb4e5d1604535fabae9ce5407d685

Re: [ClusterLabs] crm resource trace

2022-10-17 Thread Lentes, Bernd
Hi, i try to find out why there is sometimes a restart of the resource and sometimes not. Unpredictable behaviour is someting i expect from Windows, not from Linux. Here you see two "crm resource trace "resource"". In the first case the resource is restarted , in the second not. The command i

Re: [ClusterLabs] crm resource trace (Was: Re: trace of resource - sometimes restart, sometimes not)

2022-10-10 Thread Lentes, Bernd
- On 7 Oct, 2022, at 21:37, Reid Wahl nw...@redhat.com wrote: > On Fri, Oct 7, 2022 at 6:02 AM Lentes, Bernd > wrote: >> - On 7 Oct, 2022, at 01:18, Reid Wahl nw...@redhat.com wrote: >> >> > How did you set a trace just for monitor? >> >> crm resource trace dlm monitor. > > crm resource

[ClusterLabs] crm resource trace (Was: Re: trace of resource - sometimes restart, sometimes not)

2022-10-07 Thread Reid Wahl
On Fri, Oct 7, 2022 at 6:02 AM Lentes, Bernd wrote: > > > > - On 7 Oct, 2022, at 01:18, Reid Wahl nw...@redhat.com wrote: > > > How did you set a trace just for monitor? > > crm resource trace dlm monitor. crm resource trace adds "trace_ra=1" to the end of the monitor operation: