Re: [Pacemaker] [Openais] Linux HA on debian sparc

2011-05-31 Thread Angus Salkeld
On Tue, May 31, 2011 at 11:52:48PM -0300, william felipe_welter wrote: > Angus, > > I make some test program (based on the code coreipcc.c) and i now i sure > that are problems with the mmap systems call on sparc.. > > Source code of my test program: > > #include > #include > #include > > #d

Re: [Pacemaker] [Openais] Linux HA on debian sparc

2011-05-31 Thread william felipe_welter
Angus, I make some test program (based on the code coreipcc.c) and i now i sure that are problems with the mmap systems call on sparc.. Source code of my test program: #include #include #include #define PATH_MAX 36 int main() { int32_t fd; void *addr_orig; void *addr; char path[PATH_MAX];

[Pacemaker] High: PE: Bug lf#2554 - target-role alone is not sufficient to promote resources

2011-05-31 Thread 项磊
in version 1.1.5, I found a "High: PE: Bug lf#2554 - target-role alone is not sufficient to promote resources" in the ChangLog.what does it mean?which configurations are sufficient to promote resources? who can give me an example cib.xml? I have been troubled by failing to promote resource as u

Re: [Pacemaker] [Openais] Linux HA on debian sparc

2011-05-31 Thread Angus Salkeld
On Tue, May 31, 2011 at 06:25:56PM -0300, william felipe_welter wrote: > Thanks Steven, > > Now im try to run on the MCP: > - Uninstall the pacemaker 1.0 > - Compile and install 1.1 > > But now i have problems to initialize the pacemakerd: Could not initialize > Cluster Configuration Database API

Re: [Pacemaker] [Openais] Linux HA on debian sparc

2011-05-31 Thread william felipe_welter
Thanks Steven, Now im try to run on the MCP: - Uninstall the pacemaker 1.0 - Compile and install 1.1 But now i have problems to initialize the pacemakerd: Could not initialize Cluster Configuration Database API instance error 2 Debbuging with gdb i see that the error are on the confdb.. most spec

Re: [Pacemaker] Linux HA on debian sparc

2011-05-31 Thread Steven Dake
Note. there are three signals you could possibly see that generate a core file. SIGABRT (assert() called in the codebase) SIGSEGV (segmentation violation) SIGBUS (alignment error) Make sure you don't have a sigbus. Opening the core file with gdb will tell you which signal triggered the fault.

Re: [Pacemaker] [Openais] Linux HA on debian sparc

2011-05-31 Thread Steven Dake
Try running paceamaker using the MCP. The plugin mode of pacemaker never really worked very well because of complexities of posix mmap and fork. Not having sparc hardware personally, YMMV. We have recently with corosync 1.3.1 gone through an alignment fixing process for ARM arches - hope that so

Re: [Pacemaker] Group not started/stopped in correct order with -INF collocation

2011-05-31 Thread Kulovits Christian - OS ITSC
Sorry!! Yes, of course Corosync Cluster Engine, version '1.2.7' SVN revision '3008' CRM Version: 1.0.9 (da7075976b5ff0bee71074385f8fd02f296ec8a3) pacemaker 1.0.10-1.2.el5 - (none) x86_64 corosync 1.2.7-1.1.el5 - (none) x86_64 heartbeat 3.0.3-2.3.el5 - (none)

Re: [Pacemaker] Automating Pacemaker Setup

2011-05-31 Thread veghead
Dejan Muhamedagic writes: > On Fri, May 27, 2011 at 08:21:08PM +, veghead wrote: > > 1) Is there a way to force crm to accept my configuration request > > ~before~ starting the second node? > > No before the DC is elected. There are two settings: dc-deadtime > and startup-fencing which can r

Re: [Pacemaker] Group not started/stopped in correct order with -INF collocation

2011-05-31 Thread Florian Haas
On 2011-05-31 14:05, Kulovits Christian - OS ITSC wrote: > Hello, > > In a 2-node cluster two groups (prod, test) are defined with a > collocation score=“-INFINITY“. When the node running the group prod > failed, the test group on the other node was stopped and the prod group > was started. After

[Pacemaker] Group not started/stopped in correct order with -INF collocation

2011-05-31 Thread Kulovits Christian - OS ITSC
Hello, In a 2-node cluster two groups (prod, test) are defined with a collocation score="-INFINITY". When the node running the group prod failed, the test group on the other node was stopped and the prod group was started. After the failed node was online again, the prod group was moved to the o

Re: [Pacemaker] Node removal in corosync-based cluster

2011-05-31 Thread Vladislav Bogdanov
31.05.2011 12:32, Dejan Muhamedagic wrote: > On Mon, May 30, 2011 at 05:27:41PM +0300, Vladislav Bogdanov wrote: >> Hi, >> >> 30.05.2011 17:12, Dejan Muhamedagic wrote: >>> Hi, >>> >>> On Sun, May 29, 2011 at 11:58:17PM +0300, Vladislav Bogdanov wrote: Hi all. I've got a task to remo

Re: [Pacemaker] Automating Pacemaker Setup

2011-05-31 Thread Dejan Muhamedagic
On Mon, May 30, 2011 at 10:16:12PM +0200, Andrew Beekhof wrote: > On Mon, May 30, 2011 at 3:59 PM, Dejan Muhamedagic > wrote: > > Hi, > > > > On Fri, May 27, 2011 at 08:21:08PM +, veghead wrote: > >> veghead writes: > >> > Todd Nine writes: > >> > Wow. The example pacemaker config and the t

Re: [Pacemaker] Node removal in corosync-based cluster

2011-05-31 Thread Dejan Muhamedagic
On Mon, May 30, 2011 at 05:27:41PM +0300, Vladislav Bogdanov wrote: > Hi, > > 30.05.2011 17:12, Dejan Muhamedagic wrote: > > Hi, > > > > On Sun, May 29, 2011 at 11:58:17PM +0300, Vladislav Bogdanov wrote: > >> Hi all. > >> > >> I've got a task to remove some nodes from cluster to save some power

Re: [Pacemaker] Bug in compiling pacemaker-pygui: CRM_DAEMON_DIR not defined

2011-05-31 Thread Gao,Yan
On 05/31/11 04:13, Andrew Beekhof wrote: > On Mon, May 30, 2011 at 2:23 PM, Gao,Yan wrote: >> On 05/30/11 17:31, Andrew Beekhof wrote: >>> It used to be in crm_config.h but I had to remove it because it >>> interfered with multilib (not that I've ever seen anyone make use of >>> that particular fe