Re: [Pacemaker] Master/Slave Confusion

On Tue, Feb 2, 2010 at 9:36 PM, Erich Weiler wrote: >> Thanks for the tip, I think I'm closer...  I set a preference and then >> tried to start the LDAP service, and the crm monitor shows testvm3 (my >> preferred master) trying to start LDAP as a master repeatedly but failing. >>  It does this lik

Re: [Pacemaker] Master/Slave Confusion

as i understand the documentation you need an ocf agent since u have to implement monitor, promote and demote methods which are not supported in lsb conform agents. Am 02.02.2010 um 21:36 schrieb Erich Weiler: >> Thanks for the tip, I think I'm closer... I set a preference and then tried >> to

Re: [Pacemaker] Master/Slave Confusion

Thanks for the tip, I think I'm closer... I set a preference and then tried to start the LDAP service, and the crm monitor shows testvm3 (my preferred master) trying to start LDAP as a master repeatedly but failing. It does this like 2 times per second. I think I'm very, very close to nailin

Re: [Pacemaker] Master/Slave Confusion

The script should set a preference for being promoted using crm_master. Have a look at LinBit's drbd script for a good example. Thanks for the tip, I think I'm closer... I set a preference and then tried to start the LDAP service, and the crm monitor shows testvm3 (my preferred master) trying

Re: [Pacemaker] Master/Slave Confusion

On Tue, Feb 2, 2010 at 5:10 AM, Erich Weiler wrote: > How does one promote a slave to master automatically? The script should set a preference for being promoted using crm_master. Have a look at LinBit's drbd script for a good example. ___ Pacemaker ma

Re: [Pacemaker] Master/Slave Confusion

OK - it seems I've achieved what I want via the following configuration: node testvm1 node testvm2 node testvm3 primitive LDAP lsb:ldap \ op monitor interval="40s" \ op monitor interval="41s" role="Master" primitive LDAP-IP ocf:heartbeat:IPaddr2 \ params ip="10.1.1.80" cid

Re: [Pacemaker] Master/Slave Confusion

if you make the LDAP daemon listen on all available interfaces, it will accept connections on the on-demand activated floating-ip. Well, I'm trying to get this to work and running into a wall... I've got 3 servers, I want LDAP to run on testvm2 and testvm3. I've configured LDAP on those 2 s

Re: [Pacemaker] Master/Slave Confusion

Thanks! This will be helpful... Rafał Kupka wrote: On Sun, Jan 31, 2010 at 06:39:28PM -0800, Erich Weiler wrote: Hi, However, it seems that when LDAP starts, the IP needs to be live on each node for the LDAP server to bind on that IP. Is that how the master/slave setup works in pacemaker?

Re: [Pacemaker] Master/Slave Confusion

On Sun, Jan 31, 2010 at 06:39:28PM -0800, Erich Weiler wrote: Hi, > However, it seems that when LDAP starts, the IP needs to be live on each > node for the LDAP server to bind on that IP. Is that how the > master/slave setup works in pacemaker? Does it use iptables or > something to block

Re: [Pacemaker] Master/Slave Confusion

Hi, if you make the LDAP daemon listen on all available interfaces, it will accept connections on the on-demand activated floating-ip. Or, if you really want to make the ldap daemon listen only on the floating-ip, you would have to write a resoure agent for ldap which will edit the ldap config