Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

On Mon, 2018-01-15 at 12:40 +, Adam Spiers wrote: > Ulrich Windl wrote: > > > > > Vladislav Bogdanov schrieb: > > > > > > 15.01.2018 11:23, Ulrich Windl wrote: > > > > > > > Vladislav Bogdanov schrieb: > > > > >

[ClusterLabs] Opinions wanted: another logfile question for Pacemaker 2.0

Currently, Pacemaker will use the same detail log as corosync if one is specified (as "logfile:" in the "logging {...}" section of corosync.conf). The corosync developers think that is a bad idea, and would like pacemaker 2.0 to always use its own log. Corosync and pacemaker both use libqb to

Re: [ClusterLabs] Antw: Re: GFS2 problem after host name change

On a fresh boot, fsck.gfs2 found no errors on either node. On 2018-01-15 01:03 AM, Ulrich Windl wrote: > I'd deal with "fatal: filesystem consistency error" first. > > Digimer schrieb am 14.01.2018 um 21:48 in Nachricht >

Re: [ClusterLabs] Opinions wanted: another logfile question for Pacemaker 2.0

On 01/15/2018 05:51 PM, Ken Gaillot wrote: > Currently, Pacemaker will use the same detail log as corosync if one is > specified (as "logfile:" in the "logging {...}" section of > corosync.conf). > > The corosync developers think that is a bad idea, and would like > pacemaker 2.0 to always use its

Re: [ClusterLabs] Opinions wanted: another logfile question for Pacemaker 2.0

On Mon, 2018-01-15 at 18:08 +0100, Klaus Wenninger wrote: > On 01/15/2018 05:51 PM, Ken Gaillot wrote: > > Currently, Pacemaker will use the same detail log as corosync if > > one is > > specified (as "logfile:" in the "logging {...}" section of > > corosync.conf). > > > > The corosync developers

Re: [ClusterLabs] GFS2 problem after host name change

On 2018-01-15 05:45 AM, Bob Peterson wrote: > - Original Message - > | I recently changed the host name of a cluster. It may or may not be > | related, but after I noticed that I can cleanly start gfs2 when the node > | boots. However, if the node is withdrawn and then I try to rejoin it >

Re: [ClusterLabs] Changes coming in Pacemaker 2.0.0

On Thu, 2018-01-11 at 10:24 -0600, Ken Gaillot wrote: > On Thu, 2018-01-11 at 01:21 +0100, Jehan-Guillaume de Rorthais wrote: > > On Wed, 10 Jan 2018 16:10:50 -0600 > > Ken Gaillot wrote: > > > > > Pacemaker 2.0 will be a major update whose main goal is to remove > > >

Re: [ClusterLabs] Opinions wanted: another logfile question for Pacemaker 2.0

On 01/15/2018 06:08 PM, Klaus Wenninger wrote: > On 01/15/2018 05:51 PM, Ken Gaillot wrote: >> Currently, Pacemaker will use the same detail log as corosync if one is >> specified (as "logfile:" in the "logging {...}" section of >> corosync.conf). >> >> The corosync developers think that is a bad

[ClusterLabs] Proper procedure for pacemaker RPM upgrades in active cluster

Hello, I'm looking for some guidance on pacemaker RPM upgrades in a running cluster environment. I'm looking to automate the process of upgrading the RPMs when we decide to plan an upgrade cycle for our clusters. What I found is that during the RPM upgrade process the pacemaker.x86_64 RPM will

[ClusterLabs] Antw: Opinions wanted: another logfile question for Pacemaker 2.0

>>> Ken Gaillot schrieb am 15.01.2018 um 17:51 in >>> Nachricht <1516035094.5232.9.ca...@redhat.com>: > Currently, Pacemaker will use the same detail log as corosync if one is > specified (as "logfile:" in the "logging {...}" section of > corosync.conf). > > The corosync

Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

Ken Gaillot wrote: On Mon, 2018-01-15 at 12:40 +, Adam Spiers wrote: Ulrich Windl wrote: But for a general solution, do you think it's more clean to have the same directory with identical properties in multiple packages, or to have

Re: [ClusterLabs] Proper procedure for pacemaker RPM upgrades in active cluster

On Mon, 2018-01-15 at 15:42 -0500, Doug Cahill wrote: > Hello, > > I'm looking for some guidance on pacemaker RPM upgrades in a running > cluster environment.  I'm looking to automate the process of > upgrading > the RPMs when we decide to plan an upgrade cycle for our clusters. > > What I found

Re: [ClusterLabs] GFS2 problem after host name change

- Original Message - | I recently changed the host name of a cluster. It may or may not be | related, but after I noticed that I can cleanly start gfs2 when the node | boots. However, if the node is withdrawn and then I try to rejoin it | without a reboot, it hangs with this in syslog;

Re: [ClusterLabs] Antw: Re: Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

15.01.2018 11:23, Ulrich Windl wrote: Vladislav Bogdanov schrieb am 12.01.2018 um 10:06 in Nachricht <3c5d9060-4714-cc20-3039-aa53b4a95...@hoster-ok.com>: 11.01.2018 18:39, Ken Gaillot wrote: [...] I thought one option aired at the summit to address this was

[ClusterLabs] Antw: Re: Antw: Re: Antw: Changes coming in Pacemaker 2.0.0

>>> Klaus Wenninger schrieb am 15.01.2018 um 08:41 in Nachricht : > On 01/15/2018 08:33 AM, Ulrich Windl wrote: >> > Ken Gaillot schrieb am 11.01.2018 um 17:37 in > Nachricht >>

Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: Changes coming in Pacemaker 2.0.0

On 01/15/2018 10:17 AM, Ulrich Windl wrote: > Klaus Wenninger schrieb am 15.01.2018 um 08:41 in > Nachricht : >> On 01/15/2018 08:33 AM, Ulrich Windl wrote: >> Ken Gaillot schrieb am 11.01.2018 um

Re: [ClusterLabs] Antw: Re: Antw: Re: Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

Ulrich Windl wrote: Vladislav Bogdanov schrieb: 15.01.2018 11:23, Ulrich Windl wrote: Vladislav Bogdanov schrieb: 11.01.2018 18:39, Ken Gaillot wrote: [...] I thought one option aired at the summit to address

[ClusterLabs] Antw: Re: GFS2 problem after host name change

Hi! I can't tell you what was wrong, but I could tell you what not to do in production environments: * Change host names It's not that it cannot be done, but there are too many places where a hostname may be configured, and it's very likely to miss one of those. Our strategy had always been:

[ClusterLabs] Antw: Re: Antw: Re: Coming in Pacemaker 2.0.0: /var/log/pacemaker/pacemaker.log

>>> Vladislav Bogdanov schrieb am 12.01.2018 um 10:06 in Nachricht <3c5d9060-4714-cc20-3039-aa53b4a95...@hoster-ok.com>: > 11.01.2018 18:39, Ken Gaillot wrote: > > [...] I thought one option aired at the summit to address this was /var/log/clusterlabs, but it's

[ClusterLabs] Antw: Re: GFS2 problem after host name change

I'd deal with "fatal: filesystem consistency error" first. >>> Digimer schrieb am 14.01.2018 um 21:48 in Nachricht <6a036895-8964-ca76-3774-4b7e9bcf5...@alteeve.ca>: > On 2018-01-14 12:29 PM, Digimer wrote: >> I recently changed the host name of a cluster. It may or may not be