On 2013-11-19T19:20:43, "Masopust, Christian"
wrote:
> at this point I'd like to jump in as I'm completely new to fencing :)
>
> My question is: which node exactly does the fencing?
One of the nodes that remain in the quorate partition.
Regards,
Lars
--
Architect Storage/HA
SUSE LINUX
On 2013-11-20T09:45:54, Andrey Groshev wrote:
> > A "fence" request is executed when a node is deemed to be in an
> > untrustworthy state - when a stop has failed, or when a network error
> > occurs. Note that in the last case, login via ssh is obviously no longer
> > possible at all.
> In last c
Hello,
I have a PostgreSQL replication set up. It consists of master A and
standby B & C which are directly connecting to master. I am using a
tool called WANPRoxy for compression of data to be transferred between
master and standby. In case of failure of master, I want WANProxy to
run on any of
Am Mittwoch, 20. November 2013, 10:28:18 schrieb Andrew Beekhof:
> On 19 Nov 2013, at 4:19 pm, Michael Schwartzkopff wrote:
> > Andrew Beekhof schrieb:
> >> On 19 Nov 2013, at 1:23 am, Michael Schwartzkopff wrote:
> >>> Hi,
> >>>
> >>> I installed pacemaker on a RHEL 6.4 machine. Now crm tells
On 2013-11-20T11:20:45, Michael Schwartzkopff wrote:
> I removed the pacemaker installation 1.1.9 from the opensuse build
> server and installed the 1.1.10 from the RHEL-HA repository. now
> everything is working as expected.
>
> Besides some kernel panics, that are not related to the cluster
>
Am Mittwoch, 20. November 2013, 11:33:55 schrieb Lars Marowsky-Bree:
> On 2013-11-20T11:20:45, Michael Schwartzkopff wrote:
> > I removed the pacemaker installation 1.1.9 from the opensuse build
> > server and installed the 1.1.10 from the RHEL-HA repository. now
> > everything is working as expec
HI Andrew,
tnx for replay.
I have fixed this. It was missconfiguration with cluster name. It was
different on bouth nodes.
br,
miha
Dne 11/19/2013 4:28 AM, pis(e Andrew Beekhof:
On 18 Nov 2013, at 11:59 pm, Miha wrote:
HI,
I am for the first time setting cluster with pacemaker & corosync
hi, after the newest rhel6.4 pacemaker update it seems that my config file
is corrupt.
my 2nd node is still pending (crm status)
and if check my config it seems that my config has trouble now.
How can i fix it?
The Error is
crm configure
INFO: object cli-prefer-mysql cannot be represented in th
Hello,
trying to relax timeout because of backups that runs usign Netbackup
and VMware storage api and causing cluster reconfiguration
Based on docs I thought that the timeout should be
token x token_retransmits_before_loss_const
but actually through my tests I see that setting or not setting th
On 2013-11-20T16:43:51, Beo Banks wrote:
> INFO: object cli-prefer-mysql cannot be represented in the CLI notation
>
>
> crm configure show | grep xml
> INFO: object cli-prefer-mysql cannot be represented in the CLI notation
> xml rsc="mysql" score="INFINITY"/>
This does not mean your configu
Hello,
I have troubles setting up 'best connectivity' rule using pcs on RHEL
6.4. I have two nodes setup with ping resource defined as:
pcs resource create ping ocf:pacemaker:ping host_list="10.242.40.251
10.242.40.252" multiplier="1000"
and location rule defined as:
pcs constraint location
- Original Message -
> From: "Aarti Sawant"
> To: "The Pacemaker cluster resource manager"
> Sent: Wednesday, November 20, 2013 3:55:40 AM
> Subject: [Pacemaker] Use of Pacemaker to configure a new resource
>
> Hello,
>
> I have a PostgreSQL replication set up. It consists of master
Hi Andrew,
Hi Takatsuka san,
What kind of procedure did the problem that became this problem cause it in?
If a problem easily happens in the environment of the user, we think that it is
necessary to contact a user using Pacemaker1.0.13.
Best Regards,
Hideo Yamauchi.
--- On Thu, 2013/11/14, TAKA
On 21 Nov 2013, at 6:08 am, Lars Marowsky-Bree wrote:
> On 2013-11-20T16:43:51, Beo Banks wrote:
>
>> INFO: object cli-prefer-mysql cannot be represented in the CLI notation
>>
>>
>> crm configure show | grep xml
>> INFO: object cli-prefer-mysql cannot be represented in the CLI notation
>> x
With over 400 updates since the release of 1.1.10, its time to start
thinking about a new release.
Today I have tagged release candidate 1[1].
The most notable fixes include:
+ attrd: Implementation of a truely atomic attrd for use with corosync 2.x
+ cib: Allow values to be added/updated and
Hi, Andrew
I understand.
More, a lower batch-limit, there is a possibility that the operation
of the cluster becomes too late.
I examine avoiding by changing adjustment of a parameter, or the motive method.
Thank you for various adjustments.
Yusuke
2013/11/19 Andrew Beekhof :
>
> On 16 Nov 2013,
16 matches
Mail list logo