Re: [ClusterLabs] SLES12 SP4: Same error logged in two different formats

On 26/08/19 08:16 +0200, Ulrich Windl wrote: > While inspecting the logs to improve my own RA, I noticed that one > error is logged with two different formats: With literal "\n" nd > with a space: > lrmd[7278]: notice: prm_isr_ds3_monitor_0:108007:stderr [ mkdir: cannot > create directory

[ClusterLabs] On crm shell' "configure": "show changed" for deletes

Hi! Working with crm in SLES12 SP4 I noticed that when you delete resources in "crm configure", a "show changed" just displays nothing. How hard would it be to show commands like "delete xyz" for each deleted resource? Regards, Ulrich ___ Manage

[ClusterLabs] Antw: Re: Antw: Re: node name issues (Could not obtain a node name for corosync nodeid 739512332)

>>> Andrei Borzenkov schrieb am 26.08.2019 um 10:52 in Nachricht : > On Mon, Aug 26, 2019 at 9:59 AM Ulrich Windl > wrote: > >> Also see my earlier message. If adding the node name to corosync conf is >> highly recommended, I wonder why SUSE's SLES procedure does not set it... >> > > If you

Re: [ClusterLabs] Antw: Re: node name issues (Could not obtain a node name for corosync nodeid 739512332)

On Mon, Aug 26, 2019 at 9:59 AM Ulrich Windl wrote: > Also see my earlier message. If adding the node name to corosync conf is > highly recommended, I wonder why SUSE's SLES procedure does not set it... > If you mean ha-cluster-init/ha-cluster-join, it just invokes "crm cluster", so you may

[ClusterLabs] pcs 0.10.3 released

I am happy to announce the latest release of pcs, version 0.10.3. Source code is available at: https://github.com/ClusterLabs/pcs/archive/0.10.3.tar.gz or https://github.com/ClusterLabs/pcs/archive/0.10.3.zip This is a bugfix release resolving issues introduced in pcs-0.10.2. Complete change

[ClusterLabs] Antw: Re: node name issues (Could not obtain a node name for corosync nodeid 739512332)

>>> Ken Gaillot schrieb am 22.08.2019 um 17:38 in Nachricht <9bd1f0de082ff66a2a9b14d1d80cc95d7eff4bac.ca...@redhat.com>: > On Thu, 2019‑08‑22 at 09:07 +0200, Ulrich Windl wrote: >> Hi! >> >> When starting pacemaker (1.1.19+20181105.ccd6b5b10‑3.10.1) on a node >> that had been down for a while, I

[ClusterLabs] Antw: Re: node name issues (Could not obtain a node name for corosync nodeid 739512332)

>>> Andrei Borzenkov schrieb am 22.08.2019 um 12:42 in Nachricht : > 22.08.2019 10:07, Ulrich Windl пишет: >> Hi! >> >> When starting pacemaker (1.1.19+20181105.ccd6b5b10-3.10.1) on a node that > had been down for a while, I noticed some unexpected messages about the node > name: >> >>

[ClusterLabs] Antw: Re: Q: "pengine[7280]: error: Characters left over after parsing '10#012': '#012'"

>>> Jan Pokorný schrieb am 22.08.2019 um 12:09 in Nachricht <20190822100910.ge7...@redhat.com>: > On 22/08/19 08:07 +0200, Ulrich Windl wrote: >> When a second node joined a two‑node cluster, I noticed the >> following error message that leaves me kind of clueless: >> pengine[7280]:error:

[ClusterLabs] SLES12 SP4: Same error logged in two different formats

Hi! While inspecting the logs to improve my own RA, I noticed that one error is logged with two different formats: With literal "\n" nd with a space: lrmd[7278]: notice: prm_isr_ds3_monitor_0:108007:stderr [ mkdir: cannot create directory '/run/isredir': File exists ] crmd[7281]: notice: