[Pacemaker] error in the pacemaker log

2009-10-28 Thread gilberto migliavacca
Hi my first purpose is to manage an apache service on a specific machine with IP 172.16.20.63 this is my configuration node custdevc03.funambol.com node custdevc04.funambol.com node custdevc05.funambol.com primitive res.ip.m63 ocf:heartbeat:IPsrcaddr \ params ip=172.16.20.63 \

Re: [Pacemaker] strange behaviour for ssh and eth0

2009-10-28 Thread gilberto migliavacca
Hi Dominik How can I configure the node's ips as cluster resources? sorry for the silly question but I'm a newbye in this field thanks in advance gilberto Dominik Klein wrote: gilberto migliavacca wrote: Hi I have 2 nodes and 1 node that I'm using just to manage the cluster. I started

[Pacemaker] virtual IP or real IP address

2009-10-28 Thread gilberto migliavacca
Hi I have a question. I've seen in the mailing list a lot of example with the IPAddr/IPAddr2 resource agent this resource agent manages the Virtual IP. Could anybody explain me why I have to create a virtual IP istead of using the real IP? for instance I have a cluster with 2 nodes and 1

Re: [Pacemaker] virtual IP or real IP address

2009-10-28 Thread Tim Serong
On 10/28/2009 at 07:26 PM, gilberto migliavacca gbmig...@yahoo.it wrote: Hi I have a question. I've seen in the mailing list a lot of example with the IPAddr/IPAddr2 resource agent this resource agent manages the Virtual IP. Could anybody explain me why I have to create a

Re: [Pacemaker] virtual IP or real IP address

2009-10-28 Thread gilberto migliavacca
Hi Tim thanks for for your help. Now there's less fog in my brain I'm trying gilberto Tim Serong wrote: On 10/28/2009 at 07:26 PM, gilberto migliavacca gbmig...@yahoo.it wrote: Hi I have a question. I've seen in the mailing list a lot of example with the IPAddr/IPAddr2 resource agent

Re: [Pacemaker] strange behaviour for ssh and eth0

2009-10-28 Thread Dominik Klein
gilberto migliavacca wrote: Hi Dominik How can I configure the node's ips as cluster resources? sorry for the silly question but I'm a newbye in this field thanks in advance gilberto Dominik Klein wrote: gilberto migliavacca wrote: Hi I have 2 nodes and 1 node that I'm using

Re: [Pacemaker] server lockup failures

2009-10-28 Thread Bernd Schubert
On Wednesday 28 October 2009, Andrew Beekhof wrote: On Wed, Oct 28, 2009 at 1:05 PM, Bernd Schubert bs_li...@aakef.fastmail.fm wrote: Hello, I think there is a severe server failure pacemaker doesn't detect. Over night a Lustre server failed in shrink_icache_memory() and probably it

Re: [Pacemaker] server lockup failures

2009-10-28 Thread Andrew Beekhof
On Wed, Oct 28, 2009 at 2:44 PM, Bernd Schubert bs_li...@aakef.fastmail.fm wrote: On Wednesday 28 October 2009, Andrew Beekhof wrote: On Wed, Oct 28, 2009 at 1:05 PM, Bernd Schubert bs_li...@aakef.fastmail.fm wrote: Hello, I think there is a severe server failure pacemaker doesn't

Re: [Pacemaker] Cluster Test Suite: Bad News

2009-10-28 Thread Andrew Beekhof
On Wed, Oct 28, 2009 at 4:33 PM, Schmidt, Torsten torsten.schm...@tecdoc.net wrote: Hi list, after manually (positive) testing of my new cluster i've initiated one round of the cluster test suite with the following command: ./CTSlab.py --at-boot 1 --nodes 'mysqlha1 mysqlha2' --stack ais

Re: [Pacemaker] Follow and then push off

2009-10-28 Thread Lars Marowsky-Bree
On 2009-10-28T12:42:38, Andrew Beekhof and...@beekhof.net wrote: I sort of like the approach, and wonder if we can do something similar? Its interesting, but sounds like a nightmare to configure. Configuring this is not that difficult, I think, once one grokked the rule - in theory, the two

Re: [Pacemaker] cannot start/stop apache from the manager node

2009-10-28 Thread Andrew Beekhof
On Tue, Oct 27, 2009 at 3:55 PM, gilberto migliavacca gbmig...@yahoo.it wrote: Hi I have 2 nodes and 1 node that I'm using just to manage the cluster. I started up the nodes and created the following configuration : node custdevc03.funambol.com node custdevc04.funambol.com node

Re: [Pacemaker] Pacemaker OCFS2 Fedora 10 RA and kernel 2.6.31.5

2009-10-28 Thread Andrew Beekhof
On Tue, Oct 27, 2009 at 4:08 AM, E-Blokos in...@e-blokos.com wrote: Just found a (crap) way to make it work again. Added in o2cb RA these lines at the top Or try the F-11 document. http://www.clusterlabs.org/wiki/Image:Clusters_from_Scratch_-_Apache_on_Fedora11.pdf There are a couple of

Re: [Pacemaker] how to run a remote script

2009-10-28 Thread Andrew Beekhof
On Mon, Oct 26, 2009 at 12:11 PM, gilberto migliavacca gbmig...@yahoo.it wrote: Hi Dejan unfortunately I cannot find a solution about my problem in the docs. My concern is about the steps I have to take, maybe it's not completly clear to me the entore process, sorry but this is the first

Re: [Pacemaker] Does Pacemaker use different OCF_CHECK_LEVELs

2009-10-28 Thread Andrew Beekhof
On Mon, Oct 26, 2009 at 8:27 AM, Luke Bigum lbi...@iseek.com.au wrote: Hi, The OCF RA spec describes multiple OCF_CHECK_LEVELs for different grades of monitoring and suggests time frames for each level (every couple seconds for level 0, maybe once a minute for level 10, etc). Does

Re: [Pacemaker] server lockup failures

2009-10-28 Thread Bernd Schubert
On Wednesday 28 October 2009, Andrew Beekhof wrote: On Wed, Oct 28, 2009 at 2:44 PM, Bernd Schubert bs_li...@aakef.fastmail.fm wrote: On Wednesday 28 October 2009, Andrew Beekhof wrote: On Wed, Oct 28, 2009 at 1:05 PM, Bernd Schubert bs_li...@aakef.fastmail.fm wrote: Hello, I

Re: [Pacemaker] resource's start/stop not getting called

2009-10-28 Thread Shravan Mishra
Hi Luke, I had tried a variation of what you have suggested which was: monitor_() { touch /monitor return $OCF_NOT_RUNNING } just to see if start is getting called at all, but to no avail. I just did exactly what you suggested but I still only see /monitor file. One interesting

Re: [Pacemaker] resource's start/stop not getting called

2009-10-28 Thread Shravan Mishra
Regards Shravan On Wed, Oct 28, 2009 at 8:14 PM, Luke Bigum lbi...@iseek.com.au wrote: Hi Shravan, Your monitor operation is always returning OCF_SUCCESS, which will tell Pacemaker it's always running, always. Try something like this in your RA: monitor_() {      touch /monitor