Thanks much. I am experienced with crmsh because I have been using it for
years, but I recently tried pcs and I really like the way it handles
constraints. Would be nice if it worked on openSUSE. Oh well.
--Eric
From: Eric Ren [mailto:z...@suse.com]
Sent: Monday, November 06, 2017 10:28 PM
Hello,
I have many of those above syslog messages from boothd (counting all
servers, that's nearly 1 hundred per day).
All sites are synchronized using NTP, but according to source (https://
github.com/ClusterLabs/booth/blob/master/src/transport.c), that
specific messages isn't event tied to
Hello
I have set up an active/passive HA NFS/DRBD cluster ... on RHEL7.2 ... and
I keep getting this 'Failed Action' message .. not always, but
sometimes :
Stack: corosync
Current DC: ha-nfs2.lan.aaroncody.com (version 1.1.16-12.el7_4.4-94ff4df) -
partition with quorum
Last updated: Mon Nov
Hi,
On 11/07/2017 05:35 AM, Eric Robinson wrote:
I installed corosync 2.4.3 and pacemaker 1.1.17 from the openSUSE Leap
4.23 repos, but I can’t find pcs or pcsd. Anybody know where to
download them from?
openSUSE/SUSE uses CLI tool "crmsh" and web UI "hawk" to mange HA cluster.
Please
I installed corosync 2.4.3 and pacemaker 1.1.17 from the openSUSE Leap 4.23
repos, but I can't find pcs or pcsd. Anybody know where to download them from?
--Eric
___
Users mailing list: Users@clusterlabs.org
Hi sbd - developers & users!
Thanks to everybody for contributing to tests and
further development.
I tried to quickly summarize the changes in the
repo since it was labeled v1.3.0:
- Add commands to test/query watchdogs
- Allow 2-node-operation with a single shared-disk
- Overhaul of the
On Sat, 2017-11-04 at 22:46 +0800, lkxjtu wrote:
>
>
> >Another possibility would be to have the start return immediately,
> and
> >make the monitor artificially return success for the first 10
> minutes
> >after starting. It's hacky, and it depends on your situation whether
> >the behavior is
Hi
I am using a two node pacemaker cluster with teaming enabled. The cluster has
1. Two team interfaces with different subents.
2. The team1 has a NFS VIP plumbed to it.
3. The VirtualIP from pacemaker is configured to plumb to team0(Corosync
ring number is 0)
In this case
Hi!
Not saying that the use of start-delay in the monitor-operations is
a good thing. It should in most cases be definitely better to delay
the return of start till a monitor would succeed. Have seen discussion
about deprecating start-delay - don't know the current state though.
But this case -
