On 09/28/10 01:25, Phil Armstrong wrote:
I'm running pacemaker-1.1.2-0.6.1 on sles11sp1. I was only able to
successfully login to the crm_gui from one of my nodes in spite of the
fact that the login parameters appeared to be identical. I traced the
problem to a zero length /etc/pam.d/hbmgmt
hi guys
I use command service openais force-stop to stop openais, It ofen waste a long
time to stop or maybe run this command and no end. sometimes I use command
service openais force-stop twice it will be ok, or I have to kill pocess. who
has a better way to stop service.
Thanks a lot:-)
On 9/28/2010 at 04:11 PM, Yan Gao y...@novell.com wrote:
On 09/28/10 01:25, Phil Armstrong wrote:
I'm running pacemaker-1.1.2-0.6.1 on sles11sp1. I was only able to
successfully login to the crm_gui from one of my nodes in spite of the
fact that the login parameters appeared to be
howdy!
I'm trying to configure a resource (xen-domU) that could start on 2
nodes (preferred on node server01):
primitive v01 ocf:heartbeat:Xen \
params xmfile=/etc/xen/conf.d/v01.cfg allow-migrate=true
location loc-v01p v01 200: server01
location loc-v01s v01 100: server02
That's
On Tue, Sep 28, 2010 at 6:05 AM, Mark Horton m...@nostromo.net wrote:
Hello,
I was wondering what side effects occur if you don't add all the
cluster nodes to the /etc/hosts file on each node?
I'd also be interested in hearing how others keep the hosts file in
sync. For example, lets say
On Mon, Sep 27, 2010 at 7:26 AM, renayama19661...@ybb.ne.jp wrote:
Hi,
When I investigated another problem, I discovered this phenomenon.
If attrd causes process trouble and does not restart, the problem does not
occur.
Step1) After start, it causes a monitor error in UmIPaddr twice.
On Mon, Sep 27, 2010 at 6:26 AM, Shravan Mishra
shravan.mis...@gmail.com wrote:
Thanks Raoul for the response.
Changing the permission to hacluster:haclient did stop that error.
Now I'm hitting another problem whereby cib is failing to start
Very strange logs.
Which distribution is this?
On 09/23/2010 09:28 AM, Andrew Beekhof wrote:
The good news is that 1.1.3 doesn't have that behavior.
Lets see how 1.0 goes once all the relevant patches have been backported.
thanks for your answer! will those patches make it into 1.0.10 or
do you have another eta for this?
this issue has
On Tue, Sep 28, 2010 at 11:48 AM, Raoul Bhatia [IPAX] r.bha...@ipax.at wrote:
On 09/23/2010 09:28 AM, Andrew Beekhof wrote:
The good news is that 1.1.3 doesn't have that behavior.
Lets see how 1.0 goes once all the relevant patches have been backported.
thanks for your answer! will those
Hi,
On Tue, Sep 28, 2010 at 11:37:02AM +0200, Andrew Beekhof wrote:
On Thu, Sep 23, 2010 at 8:49 PM, Phil Armstrong p...@sgi.com wrote:
I posted earlier asking for help because I had a primitive whose monitor
operation was not getting canceled at the time that a manual relocation was
On Tue, Sep 28, 2010 at 11:59:50AM +0200, Andrew Beekhof wrote:
On Tue, Sep 28, 2010 at 11:48 AM, Raoul Bhatia [IPAX] r.bha...@ipax.at
wrote:
On 09/23/2010 09:28 AM, Andrew Beekhof wrote:
The good news is that 1.1.3 doesn't have that behavior.
Lets see how 1.0 goes once all the relevant
Hi,
On Tue, Sep 28, 2010 at 11:00:18AM +0200, Sascha Reimann wrote:
howdy!
I'm trying to configure a resource (xen-domU) that could start on 2
nodes (preferred on node server01):
primitive v01 ocf:heartbeat:Xen \
params xmfile=/etc/xen/conf.d/v01.cfg allow-migrate=true
location
On 9/28/2010 at 07:29 PM, Andrew Beekhof and...@beekhof.net wrote:
On Tue, Sep 28, 2010 at 6:05 AM, Mark Horton m...@nostromo.net wrote:
Hello,
I was wondering what side effects occur if you don't add all the
cluster nodes to the /etc/hosts file on each node?
I'd also be
On 9/28/2010 at 04:11 PM, Yan Gao y...@novell.com wrote:
On 09/28/10 01:25, Phil Armstrong wrote:
I'm running pacemaker-1.1.2-0.6.1 on sles11sp1. I was only able to
successfully login to the crm_gui from one of my nodes in spite of the
fact that the login parameters appeared to be
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 colocation constraints.
I am pretty sure that I have that working before,
Hi,
Let's say that I have manually demote a ms resource and have the following
situation
crm(live)resource# demote ms-drbd_01
crm(live)resource# status
[..snip..]
Master/Slave Set: ms-drbd_01
Slaves: [ node-01 node-03 ]
How can I manually promote ms-drbd_01 on node-03?
The promote command
Sorry forgot to attach my corosync.conf.
=
totem {
version: 2
# token: 3000
# token_retransmits_before_loss_const: 10
# join: 60
# consensus: 1500
# vsftype: none
# max_messages: 20
# clear_node_high_bit: yes
secauth: off
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 stonith: l2network device OK.
Hi Andrew,
Pushed as:
http://hg.clusterlabs.org/pacemaker/1.1/rev/8433015faf18
Not sure about applying to 1.0 though, its a dramatic change in behavior.
The change of this link is not found.
Where did you update it?
Best Regards,
Hideo Yamauchi.
--- Andrew Beekhof and...@beekhof.net
Hi Andrew,
Thank you for comment.
The problem here is that attrd is supposed to be the authoritative
source for this sort of data.
Yes. I understand.
Additionally, you don't always want attrd reading from the status
section - like after the cluster restarts.
The problem seems to be able
Date: Tue, 28 Sep 2010 12:27:47 +0200
From: Andrew Beekhof and...@beekhof.net
To: The Pacemaker cluster resource manager
pacemaker@oss.clusterlabs.org
Subject: Re: [Pacemaker] pacemaker stop problem
Message-ID:
aanlktikoqp6bpecxchxrvqsashhbw=1ksv7shjxbs...@mail.gmail.com
Content-Type:
21 matches
Mail list logo
