2012/7/23 Andreas Kurz :
> You are using stonith-aciton="poweroff" with external/ipmi? That would
> explain this 4s during which the System does a powerdown caught by
> acpid. Use stonith-aciton="reset" when using external/ipmi ... this
> should bring down the STONITH target nearly immediately, whi
2012/7/23 Lars Marowsky-Bree :
> start-delay=15s on the stonith resource's start action in the crm
> configuration.
Doesn't that delay the startup of the stonith device resource in
pacemaker, rather dan adding a number of seconds between the decision
to stonith and the actual stonithing?
--
Fran
Hi all,
I ran into bug 5063 and/or 5072 while setting the cluster in maintenance mode
and back ("crm configure property maintenance-mode=true" and later "false").
I'm running pacemaker 1.1.6 (Martin's backport for Ubuntu lucid). I thought I
could easily cherry-pick the commits and rebuild the p
On Jul 24, 2012, at 12:25 AM, Vladislav Bogdanov wrote:
> 24.07.2012 04:50, Andrew Beekhof wrote:
>> On Tue, Jul 24, 2012 at 5:38 AM, David Barchas wrote:
>>>
>>> On Monday, July 23, 2012 at 7:48 AM, David Barchas wrote:
>>>
>>>
>>> Date: Mon, 23 Jul 2012 14:15:27 +0300
>>> From: Vladislav Bo
On 07/24/2012 11:02 AM, Frank Van Damme wrote:
> 2012/7/23 Andreas Kurz :
>> You are using stonith-aciton="poweroff" with external/ipmi? That would
>> explain this 4s during which the System does a powerdown caught by
>> acpid. Use stonith-aciton="reset" when using external/ipmi ... this
>> should
On 2012-07-24T11:08:17, Frank Van Damme wrote:
> Doesn't that delay the startup of the stonith device resource in
> pacemaker, rather dan adding a number of seconds between the decision
> to stonith and the actual stonithing?
The effect is the same, since one of the nodes will not have stonith
i
Hi,
here are the results of the corosync status. Can´t find a problem there:
pilotpound:
[root@pilotpound ~]# corosync-cfgtool -s
Printing ring status.
Local node ID 425699520
RING ID 0
id = 192.168.95.25
status = ring 0 active with no faults
RING ID 1
id = 192
Hi,
I´m glad to report that after a restart of all corosync and pacemaker services
the cluster is back on normal operation. A manuel failover is working fine and
eveything shifts smoothly.
Thanks to everyone for their support !
Kind regards
fatcharly
Original-Nachricht
> D
I replaced "target_role" with "target-role", but I get the same error regarding
"target-role" (eg. ERROR: DRBD_data: attribute target_role does not exist).
I also tried removing that attribute, but it seems to break my config. Should I
post the whole XML? I don't want to spam the list if it's not
24.07.2012 14:23, Vadym Chepkov wrote:
>
> On Jul 24, 2012, at 12:25 AM, Vladislav Bogdanov wrote:
>
>> 24.07.2012 04:50, Andrew Beekhof wrote:
>>> On Tue, Jul 24, 2012 at 5:38 AM, David Barchas wrote:
On Monday, July 23, 2012 at 7:48 AM, David Barchas wrote:
Date: Mon,
Hi,My configuration:- centos 5.8 x86_64- heartbeat 3.0.3- pacemaker 1.0.12- latest mysql agent (from github) (there is an error in log message in block 'pre-demote'. 'post-demote' is used and it's confusing in logs. I have done the change in the script)I have mysql in master/slave replication on
Hi,
My configuration:
- centos 5.8 x86_64
- heartbeat 3.0.3
- pacemaker 1.0.12
- latest mysql agent (from github) (there is an error in log message in block
'pre-demote'. 'post-demote' is used and it's confusing in logs. I have done the
change in the script)
I have mysql in master/slave replic
Hi,
Fixed! The problem comes from the squid ocf script
(/usr/lib/ocf/resource.d/heartbeat/Squid) that doesn't handle IPv6
addresses correctly.
All you have to do is modify the line 198 as such :
awk '/(tcp.*[0-9]+\.[0-9]+\.+[0-9]+\.[0-9]+:'$SQUID_PORT'
|tcp.*:::'$SQUID_PORT' )/{
Source:
http://w
Hi all,
Simple crm configure syntax question (I think). I'm trying to make a given
role (a 'Master' in a master/slave set) from being location on a given node.
However, the "obvious" syntax (at least in my mind) doesn't work:
location avoid_being_the_master ms_MySQL:Master -1000: my_
14 matches
Mail list logo
