Booth version 0.1.0 has no retry method for packets, one single packet loss and the election does not work anymore.
Also it has a stupid checking of ballot values against promised values, in which case it communicates but does not do things right.
Booth version 0.1.0 is very sensitive about
Von:Andrew Beekhof and...@beekhof.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] Interval-origin in monitor operations does not work
On 2 May 2014, at 4:55 pm, Andrew Beekhof and...@beekhof.net wrote:
On 15 Apr 2014, at 4:12 am, Rainer Brestan
Apr 2014, at 5:10 am, Rainer Brestan rainer.bres...@gmx.net wrote:
Using interval-origin in monitor operation definition does not work any more.
Veryfied on Pacemaker 1.1.10, but we think it does not work since 1.1.8 until now.
Pengine calculates start delay in function unpack_operation and calls
Using interval-origin in monitor operation definition does not work any more.
Veryfied on Pacemaker 1.1.10, but we think it does not work since 1.1.8 until now.
Pengine calculates start delay in function unpack_operation and calls there crm_time_subtract.
The call to crm_time_subtract with
by Pacemaker
I found that on Ubuntu servers, the /bin/sh designation fails, but if
you use /bin/bash, it works fine
On 1/30/2014 3:25 AM, Rainer Brestan wrote:
The resource agent was developed by Stefan Wenk an me.
Plan is to include it into GIT Repo resource-agents by pull request
after some short
I have got the SNMP subagent from pacemaker-mgmt 2.1.2 working with corosync 2.3 and pacemaker 1.1.10.
Some modification are implemented because of wrong attach method to CIB and one nasty bug, where hbagent crashes, when it does not find an operation on parsing a change.
As for all versions of
The resource agent was developed by Stefan Wenk an me.
Plan is to include it into GIT Repo resource-agents by pull request after some short testing period outside or own labs.
Rainer
Gesendet:Donnerstag, 30. Januar 2014 um 00:25 Uhr
Von:Vladimir Broz vladik...@centrum.cz
An:The Pacemaker
Please do not merge colocation and order together in a way that only none or both is present.
Example 1: Resource A communicates with resource B over network but A must run before B.
In this case only order is needed without colocation.
Example 2: Resource A and B share a local directory
+ strcmp(operation, CRMD_ACTION_STATUS) != 0
+ strcmp(operation, CRMD_ACTION_NOTIFY) != 0) {
guint removed = 0;
struct stop_recurring_action_s data;
Thanks,
Takatoshi MATSUO
2013/8/1 Rainer Brestan rainer.bres...@gmx.net:
Base situation for the logs:
Pacemaker stop on int2node1
from RA on int2node1.
Gesendet:Mittwoch, 31. Juli 2013 um 02:10 Uhr
Von:Andrew Beekhof and...@beekhof.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
On 30/07/2013, at 9:13 PM, Rainer Brestan
.
Gesendet: Mittwoch, 31. Juli 2013 um 02:10 Uhr
Von: Andrew Beekhof and...@beekhof.net
An: The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff: Re: [Pacemaker] Announce: Pacemaker 1.1.10 now available
On 30/07/2013, at 9:13 PM, Rainer Brestan rainer.bres...@gmx.net
I can agree, Master monitor operation is broken in 1.1.10 release.
When the slave monitor action is started, the master monitor action is not called any more.
I have created a setup with Stateful resource with two nodes.
Then the Pacemaker installation is changed to different versions
The bug is in the function is_normal_node.
This function checks the attribute type for state normal.
But this attribute is not used any more.
CIB output from Pacemaker 1.1.8
nodes
node id=int2node1 uname=int2node1
instance_attributes id=nodes-int2node1
nvpair id=nodes-int2node1-standby
Seems that it requires now the lifetime
crm node standby node1 forever
The error message is just nonsense.
Rainer
Gesendet:Montag, 13. Mai 2013 um 13:53 Uhr
Von:Michael Schwartzkopff mi...@clusterbau.com
An:pacemaker@oss.clusterlabs.org
Betreff:[Pacemaker] crm subshell 1.2.4 incompatible
:
On 03/05/2013, at 8:46 PM, Rainer Brestan rainer.bres...@gmx.net wrote:
Now i have all the logs for some combinations.
Corosync: 1.4.1-7 for all the tests on all nodes
Base is always fresh installation of each node with all packages equal except pacemaker version.
int2node1 node id
SNMP agent hbagent from pacemaker-mgmt produces segmentation fault if used with pacemaker=1.1.8 and corosync.
The reason is function get_cib_fd in file hbagentv2.c.
It tries to get the file descriptor with function pointer inputfd, which is not initialized any more since change of IPC to
and...@beekhof.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 03/05/2013, at 4:46 AM, Rainer Brestan rainer.bres...@gmx.net wrote:
Hi Lars,
i have tried 1.1.9-2 from download area at clusterlabs for RHEL6 with corosync
Marowsky-Bree l...@suse.com
An:pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] 1.1.8 not compatible with 1.1.7?
On 2013-04-24T11:44:57, Rainer Brestan rainer.bres...@gmx.net wrote:
Current DC: int2node2 - partition WITHOUT quorum
Version: 1.1.8-7.el6-394e906
This may not be the answer you want
I have tried to make this test, because I had the same problem.
Origin:
One node cluster, node int2node1 running with IP address 10.16.242.231, quorum ignore, DC int2node1
[root@int2node1 sysconfig]# crm_mon -1
Last updated: Wed Apr 24 09:49:32 2013
Last change: Wed Apr 24
, 12. April 2013 um 02:03 Uhr
Von:Andrew Beekhof and...@beekhof.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] attrd waits one second before doing update
On 12/04/2013, at 7:17 AM, Rainer Brestan rainer.bres...@gmx.net wrote:
In pacemaker
In pacemaker 1.1.7-6 with corosync 1.4.1-7 update of attributes works almost online.
Used with SysInfo resource agent and manual commands like attrd_updater -U 4 -n test.
In the logfile there is one line
attrd[...] notice: attrd_trigger_update: Sending flush up to all hosts for: ...
and a
Hi Felix,
maybe my hint is worthless, but have you implemented the crm_master calls in your RA ?
See Stateful RA demo CRM_MASTER calls.
Rainer
Gesendet:Mittwoch, 10. April 2013 um 09:58 Uhr
Von:Felix Zachlod fz.li...@sis-gmbh.info
An:The Pacemaker cluster resource manager
Hi Felix,
thats exactly the reason why I took the meta attribute variant.
It is currently available neither via crm_resource nor via crm.
Maybe a good point to submit an request to Dejan about extension of crmsh.
Rainer
Gesendet:Dienstag, 09. April 2013 um 15:32 Uhr
Von:Felix Zachlod
Hi Felix,
basically you have three option to provide information to the resource agent.
- Resource parameters
- Resource meta attributes
- Node attributes
Let me assume some information for an example.
Your nodes are named nodeA and nodeB.
The hardware address for nodeA shall be
: [Pacemaker] issues when installing on pxe booted environment
On Fri, 29 Mar 2013 11:37:37 +1100
Andrew Beekhof and...@beekhof.net wrote:
On Thu, Mar 28, 2013 at 10:43 PM, Rainer Brestan
rainer.bres...@gmx.net wrote:
Hi John,
to get Corosync/Pacemaker running during anaconda installation, i
...@arin.net
An:The Pacemaker cluster resource manager pacemaker@oss.clusterlabs.org
Betreff:Re: [Pacemaker] PGSQL resource promotion issue
On Mar 28, 2013, at 8:13 AM, Rainer Brestan rainer.bres...@gmx.net wrote:
Hi Steve,
i think, you have misunderstood how ip addresses are used with this setup
Hi John,
to get Corosync/Pacemaker running during anaconda installation, i have created a configuration RPM package which does a few actions before starting Corosync and Pacemaker.
An excerpt of the post install of this RPM.
# mount /dev/shm if not already existing, otherwise openais cannot
Hi Steve,
i think, you have misunderstood how ip addresses are used with this setup, PGVIP should start after promotion.
Take a look at Takatoshis Wiki.
https://github.com/t-matsuo/resource-agents/wiki/Resource-Agent-for-PostgreSQL-9.1-streaming-replication
The promotion sequency is very
On Mar 26, 2013, at 8:19 AM, Steven Bambling smbambl...@arin.net wrote:
Excellent thanks so much for the clarification. Ill drop this new RA in and see if I can get things working.
STEVE
On Mar 26, 2013, at 7:38 AM, Rainer Brestan rainer.bres...@gmx.net
wrote:
Hi Steve,
pgsql
Hi Steve,
when Pacemaker does promotion, it has already selected a specific node to become master.
It is far too late in this state to try to update master scores.
But there is another problem with xlog in PostgreSQL.
According to some discussion on PostgreSQL mailing lists, not relevant
, 2013, at 6:32 AM, Rainer Brestan rainer.bres...@gmx.net wrote:
Hi Steve,
when Pacemaker does promotion, it has already selected a specific node to become master.
It is far too late in this state to try to update master scores.
But there is another problem with xlog in PostgreSQL
The resource agent for tomcat is extended to allow the response of the status
url to be checked against a regex.
The RA includes a new parameter statusurlregex.
If this parameter is not present, it behaves as now.
If present, it checks against the regex.
Therefore, it is possible not just
When updating the meta attribute clone-max all instances of the clone are
terminated and immediately restarted.
Following configuration (not symmetric cluster):
primitive resMux_gw ocf:heartbeat:Dummy op start interval=0 timeout=10 op
stop interval=0 timeout=10 op monitor interval=10 timeout=3
33 matches
Mail list logo
