Eh? Then why does pcs config show nothing new after that command is run?
> On Aug 1, 2018, at 3:08 PM, Ken Gaillot wrote:
>
> A resource can have more than one monitor, so that command by itself
> just adds a second monitor. You have to delete the original one
> separately with pcs resource op
The fence device starts fine, and randomly fails some time later. In the first
message I sent, you can see that the failure message had a different date/time
on each cluster node, but ultimately it failed on all nodes. My second E-mail
on this thread has the log data from one node attached...
https://software.opensuse.org/download.html?project=network%3Aha-clustering%3AStable&package=crmsh
S pozdravem Kristián Feldsam
Tel.: +420 773 303 353, +421 944 137 535
E-mail.: supp...@feldhost.cz
www.feldhost.cz - FeldHost™ – Hostingové služby prispôsobíme vám. Máte
špecifické požiadavky? Pora
Is there a pre-packaged rpm available that will work on RHEL 7.4.
Right now all I have is a much older crmsh-2.1+git98 package. This does
not work for configuration purposes on RHEL7.4. I get these sorts of
errors trying to configure resources.
[root@node2 ~]# crm configure edit
ERROR: CIB no
On Thu, 2018-08-02 at 11:02 +0200, Aurelien Kempiak wrote:
> Hello,
> I'm using Openvpn in failover mode, and it manages a ucarp VIP for
> this. Problem is there's only one managed VIP (let's say I use it for
> WAN), not two (for WAN + LAN).
> My idea is to use Corosync/pacemaker, monitor the openv
Hello,
I'm using Openvpn in failover mode, and it manages a ucarp VIP for this.
Problem is there's only one managed VIP (let's say I use it for WAN),
not two (for WAN + LAN).
My idea is to use Corosync/pacemaker, monitor the openvpn ucarp (WAN)
VIP, and brings up my pacemaker (LAN) VIP dependi
On Thu, 2018-08-02 at 02:25 +, Eric Robinson wrote:
> > > The message likely came from the resource agent calling
> > > crm_attribute
> > > to set a node attribute. That message usually means the cluster
> > > isn't
> > > running on that node, so it's highly suspect. The cib might have
> > > cr
> Hi!
>
> I'm not familiar with Redhat, but is tis normal?:
>
> > > corosync: active/disabled
> > > pacemaker: active/disabled
>
> Regards,
> Ulrich
That's the default after a new install. I had not enabled them to start
automatically yet.
>
> >>> Eric Robinson schrieb am 02.08.2018 u
Отправлено с iPhone
> 2 авг. 2018 г., в 9:27, Ulrich Windl
> написал(а):
>
> Hi!
>
> I'm not familiar with Redhat, but is tis normal?:
>
>>> corosync: active/disabled
>>> pacemaker: active/disabled
>
Some administrators prefer starting cluster stack manually, so it may be
intentional.
