On May 27, 2010, at 7:21 AM, Andrew Beekhof wrote:
On Wed, May 26, 2010 at 9:07 PM, Vadym Chepkov vchep...@gmail.com wrote:
Hi,
What would be the proper way to shutdown members of two-node cluster in case
of a power outage?
I assume as soon I issue 'crm node standby node-1 reboot
On May 17, 2010, at 11:38 AM, Dejan Muhamedagic wrote:
You don't want to set it that low. PE input files are part of
your cluster history. Set it to a few thousand.
What could be the side-backs of having it too low?
How are these files being used?
And shouldn't be some reasonable default
On Wed, May 19, 2010 at 1:26 PM, Dejan Muhamedagic deja...@fastmail.fmwrote:
And shouldn't be some reasonable default be in place? I just
happened to notice 90% inode utilization on my /var, some could
be not so lucky.
Yes, that could be a problem. Perhaps that default could be
changed
On Tue, May 18, 2010 at 2:22 PM, Ruiyuan Jiang ruiyuan_ji...@liz.comwrote:
Hi, Vadym
I modified the configuration per your suggestion. Here is the current
configuration of the cluster:
[r...@usnbrl52 ~]# crm configure show
node usnbrl52
node usnbrl53
primitive ClusterIP
On Tue, May 18, 2010 at 3:58 PM, Ruiyuan Jiang ruiyuan_ji...@liz.comwrote:
Thanks, Vadym
This time it failed over to another node. For two nodes cluster, does the
cluster have to set to “no-quorum-policy=ignore” to failover or work
correctly?
I can't say it better myself:
On May 17, 2010, at 2:52 AM, Andrew Beekhof wrote:
On Sun, May 16, 2010 at 1:09 AM, Vadym Chepkov vchep...@gmail.com wrote:
Hi
I noticed pengine (pacemaker-1.0.8-6.el5) creates quite a lot of files in
/var/lib/pengine,
especially when cluster-recheck-interval is set to enable failure
On May 17, 2010, at 11:56 AM, Simon Lavigne-Giroux wrote:
Hi,
I have 2 servers running Pacemaker. When the router fails, both nodes become
primary. Is it possible for Pacemaker on the secondary server to detect that
the network connection is not available and not become primary.
On May 17, 2010, at 5:40 PM, Ruiyuan Jiang wrote:
Hi, Gianluca
I modified my configuration and deleted “crm configure property
no-quorum-policy=ignore” as you suggested but I have the same problem that
the IP address does not fail. Thanks.
[r...@usnbrl52 log]# crm configure show
Hi
I noticed pengine (pacemaker-1.0.8-6.el5) creates quite a lot of files in
/var/lib/pengine,
especially when cluster-recheck-interval is set to enable failure-timeout
checks.
/var/lib/heartbeat/crm/ seems also growing unattended.
Does pacemaker do any self-maintenance or it will cause system
You forgot to turn on monitor operation for ping (actual job)
On May 11, 2010, at 5:15 AM, Gianluca Cecchi wrote:
On Mon, May 10, 2010 at 4:39 PM, Vadym Chepkov vchep...@gmail.com wrote:
# crm ra meta ping
name (string, [undef]): Attribute name
The name of the attributes to set
:
On Tue, May 11, 2010 at 12:50 PM, Vadym Chepkov vchep...@gmail.com wrote:
You forgot to turn on monitor operation for ping (actual job)
I saw from the
[r...@ha1 ~]# crm ra meta ping
command
Operations' defaults (advisory minimum):
start timeout=60
stop timeout
wrote:
On Tue, May 11, 2010 at 12:50 PM, Vadym Chepkov vchep...@gmail.com wrote:
You forgot to turn on monitor operation for ping (actual job)
I saw from the
[r...@ha1 ~]# crm ra meta ping
command
Operations' defaults (advisory minimum):
start timeout=60
stop
property default-action-timeout=120s
On Tue, May 11, 2010 at 11:00 AM, Gianluca Cecchi gianluca.cec...@gmail.com
wrote:
On Tue, May 11, 2010 at 1:13 PM, Vadym Chepkov vchep...@gmail.com wrote:
First of all, none of the monitor operation is on by default in pacemaker,
this is something that you
The is no default unless it's set, that's why crm complains
On Tue, May 11, 2010 at 12:41 PM, Gianluca Cecchi gianluca.cec...@gmail.com
wrote:
On Tue, May 11, 2010 at 5:47 PM, Vadym Chepkov vchep...@gmail.com wrote:
pingd is a daemon with is running all the time and does it job
you still
You didn't have to do 'yum makecache'
Sometimes ago Andrew accidentally replaced some rpms without bumping up
revision number.
This made yum to complain.
'yum clean all' should have cured all that.
On Tue, May 11, 2010 at 2:09 PM, Simon Lavigne-Giroux simon...@gmail.comwrote:
I found the
# crm ra meta ping
name (string, [undef]): Attribute name
The name of the attributes to set. This is the name to be used in the
constraints.
By default is pingd, but you are checking against pinggw
I suggest you do not change name though, but adjust your location constraint
to use pingd
On Tue, May 4, 2010 at 3:41 AM, Andrew Beekhof and...@beekhof.net wrote:
Hmmm... I wonder if the RHEL5.5 kernel is new enough to run the dlm.
I suspect not.
Why not try the RHEL6 beta? It comes with compatible versions of
everything (including pacemaker).
On May 3, 2010, at 2:23 AM, Andrew Beekhof wrote:
I doubt openais conflicts with corosync, unless you have a very old
version of cman.
The repos include openais 1.0.x which is built against corosync.
Unless I am doing something terribly wrong, this is not the case.
Redhat 5.5 (the
asked at the very beginning:
On Sat, May 1, 2010 at 3:30 PM, Vadym Chepkov vchep...@gmail.com wrote:
Hi,
I found out I can't use gnbd if I use pacemaker rpm from clusterlabs
repository, because gnbd depends on cman which requires openais which
conflicts with corosync pacemaker depends
On May 3, 2010, at 6:03 PM, Vadym Chepkov wrote:
On May 3, 2010, at 5:39 PM, Andrew Beekhof wrote:
perhaps try the srpm from F-12
Would be nice, but the last one was in F-9, it seems:
http://koji.fedoraproject.org/koji/packageinfo?packageID=182
Oh, I found out it's part of cluster
else needs to be done?
Thank you,
Vadym Chepkov
___
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc
http://www.clusterlabs.org/doc/en-US/Pacemaker/1.1/html/Pacemaker_Explained/node-score-equal.html
On Apr 29, 2010, at 10:20 AM, Dan Frincu wrote:
Greetings all,
In the case of two servers in a cluster with OpenAIS, take the following
example:
location Failover_Alert_1 Failover_Alert
? Thank you.
Sincerely yours,
Vadym Chepkov
___
Pacemaker mailing list
Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
101 - 123 of 123 matches
Mail list logo
