Hi Dejan,
it's working fine with the amount of free ram as the score and a bigger
default-resource-stickiness:
primitive v01 ocf:heartbeat:Xen \
params xmfile="/etc/xen/conf.d/v01.cfg" \
op monitor interval="30s" timeout="30s" \
op start interval="0" timeout="60s" \
On Wed, Sep 29, 2010 at 11:57 PM, Andrew Daugherity
wrote:
> Ron Kerry writes:
>> I am seeing the following sequence of messages with every monitor interval
>> for
> my stonith resource.
>>
>> Sep 28 10:44:01 genesis stonith-ng: [9493]: ERROR: run_stonith_agent: No
> timeout set for stonith
>> o
On Tue, Sep 28, 2010 at 2:55 PM, Phil Armstrong wrote:
>> From Andrew Beekof
>> 1.1.3 came out the other day.
>> which distro are you using?
>
> I'm not sure if this answers your question:
>
> novell/sles/updates/SLE11-HAE-SP1-Updates/sle-11-ia64
hmm, that doesn't tell me much about whats in that
Thanks for the help. We have a limited range of IP addresses. What
I've decided to do is just add our range of IPs in the hosts file on
each machine. And then name each host based on its IP. Then as we
dynamically add nodes they will already be in the hosts file.
Mark
On Tue, Sep 28, 2010 a
Hi Andrew,
> Sorry, it probably got rebased before I pushed it.
>
> http://hg.clusterlabs.org/pacemaker/1.1/rev/dd8e37df3e96 should be the
> right link
Thanks!!
Hideo Yamuachi.
--- Andrew Beekhof wrote:
> Sorry, it probably got rebased before I pushed it.
>
> http://hg.clusterlabs.org/pacem
Is it ok to stop/start a resource during a promote?
I'm setting up a master/slave set of resources. When a slave is
promoted to master, I need to stop the resource, change a config file,
then start it up in master mode.
Mark
___
Pacemaker mailing list
Ron Kerry writes:
> I am seeing the following sequence of messages with every monitor interval for
my stonith resource.
>
> Sep 28 10:44:01 genesis stonith-ng: [9493]: ERROR: run_stonith_agent: No
timeout set for stonith
> operation monitor with device fence_legacy
> Sep 28 10:44:01 genesis ston
On 29 September 2010 21:01, Andreas Hofmeister wrote:
> On 29.09.2010 19:59, Mike A Meyer wrote:
>
> We have two nodes that we have the IP address assigned to a bond0 network
> interface instead of the usual eth0 network interface. We are wondering if
> there are issues with trying to configure
On 29.09.2010 19:59, Mike A Meyer wrote:
We have two nodes that we have the IP address assigned to a bond0
network interface instead of the usual eth0 network interface. We are
wondering if there are issues with trying to configure
corosync/pacemaker with an IP assigned to a bond0 network inte
Here you go.
# Please read the corosync.conf.5 manual
page
compatibility: whitetank
totem {
version:
2
secauth:
off
threads:
0
interface
{
ringnumber: 0
bindnetaddr: 172.26.2.167
mcastaddr: 226.94.1.1
Please paste the conf of corosync, without suppling the conf is quite difficult
to help you
Cheers,
Pavlos
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterl
We have two nodes that we have the IP address
assigned to a bond0 network interface instead of the usual eth0 network
interface. We are wondering if there are issues with trying to configure
corosync/pacemaker with an IP assigned to a bond0 network interface. We
are seeing that corosync/pacemaker
Some more info:
root 14170 14166 0 12:23 ?00:00:00 /usr/lib64/heartbeat/stonithd
nobody 14172 14166 0 12:23 ?00:00:00 /usr/lib64/heartbeat/lrmd
82 14173 14166 0 12:23 ?00:00:00 /usr/lib64/heartbeat/attrd
82 14174 14166 0 12:23 ?00:00:00 /usr/l
On Wed, Sep 29, 2010 at 3:58 PM, Vladislav Bogdanov
wrote:
> Hi!
>
> This patch breaks rpm build and seems to be unneeded (at least on F13)
> Italian docs are generated without it.
oh, is that why it keeps breaking.
Thanks for investigating! :-)
>
> http://hg.clusterlabs.org/pacemaker/1.1/diff/a
Hi,
I did a bt on the core, this is what I found:
==
Core was generated by `/usr/lib64/heartbeat/cib'.
Program terminated with signal 11, Segmentation fault.
[New process 12340]
#0 0x7f23acc553fa in strncmp () from /lib64/libc.so.6
(gdb) bt
#0 0x7f23acc553fa in strncmp () fro
Hi!
This patch breaks rpm build and seems to be unneeded (at least on F13)
Italian docs are generated without it.
http://hg.clusterlabs.org/pacemaker/1.1/diff/ac25a4ecdbcb/doc/Clusters_from_Scratch/publican.cfg.in
Symptoms:
$ make Clusters_from_Scratch.txt
Building Clusters_from_Scratch
rm -rf C
Sorry, it probably got rebased before I pushed it.
http://hg.clusterlabs.org/pacemaker/1.1/rev/dd8e37df3e96 should be the
right link
On Wed, Sep 29, 2010 at 2:51 AM, wrote:
> Hi Andrew,
>
>> Pushed as:
>> http://hg.clusterlabs.org/pacemaker/1.1/rev/8433015faf18
>>
>> Not sure about applying
Hi,
We examined the trouble outbreak of a resource during cluster division and the
recovery of the
cluster.
However, at the time of cluster recovery, the phenomenon that fail-count
disappeared occurred.
Failed-Actions did not disappear then.
In the next procedure, it occurred.
Step1)We start
On 28 September 2010 15:09, Pavlos Parissis wrote:
> Hi,
>
>
> When I issue "crm resource move pbx_service_01 node-0N" it moves this
> resource group but the fs_01 resource is not started because drbd_01 is
> still running on other node and it is not moved as well tonode-0N, even I
> have colocati
Date: Tue, 28 Sep 2010 12:27:47 +0200
From: Andrew Beekhof
To: The Pacemaker cluster resource manager
Subject: Re: [Pacemaker] pacemaker stop problem
Message-ID:
Content-Type: text/plain; charset="iso-8859-1"
On Tue, Sep 28, 2010 at 10:00 AM, jiaju liu wrote:
> hi guys
> I use comman
20 matches
Mail list logo