Yasuhiro Fujii wrote:
Hi.
I'm testing 3nodes CentOS5.3 cluster.
When 3 nodes joined and one node leaved from cluster,but expected votes
did not reduce.
So when 2 nodes leaved(cman_tool leave),only one node status chaneged to
activity blocked.
Eek! You're right.
I've raised a
ESGLinux wrote:
Hello,
Looking the configuration of my 2 nodes cluster I have seen that when I
run the command cman_tool with diferent commands I get diferent ips for
my nodes.
here is the example:
cman_tool -af nodes
Node Sts Inc Joined Name
1 M 1624
Lon Hohberger wrote:
On Wed, 2009-05-20 at 08:08 +0100, Chrissie Caulfield wrote:
- if a quorum device exists and it is being reregistered with the same
name, just change the votes and recalculate quorum
cman doesn't allow the votes to be changed without deregistering and
reregistering
Elias, Michael wrote:
I am trying to understand how these timers interact with each other.
In a RHEL4 cluster the heartbeat defaults are;
hello_timer:5
max_retries:5
deadnode_timeout:21
Meaning a heartbeat message is sent every 5 seconds, if it fails to
receive a
Miguel Sanchez wrote:
Hi. I have a CentOS 5.3 cluster with two nodes. If I execute service
cman restart within a node, or stop + start after few seconds, another
node doesn´t recognize this membership return and its fellow stay
forever offline.
For example:
* Before cman restart:
Adam Hough wrote:
On Wed, May 6, 2009 at 7:01 AM, Chrissie Caulfield ccaul...@redhat.com
wrote:
Miguel Sanchez wrote:
Hi. I have a CentOS 5.3 cluster with two nodes. If I execute service
cman restart within a node, or stop + start after few seconds, another
node doesn´t recognize
Chen Ming wrote:
I install a new two nodes cluster, one node can start successfully.
while the other node can not start cman.
There is the logs. Any comment is appreciated.
Apr 23 12:37:22 err AS-2 groupd[8319]: found uncontrolled kernel object
rgmanager in /sys/kernel/dlm
Apr 23
OlegG wrote:
Hello!
I have 2-node CMAN cluster with 1 vote for each node
Also I have Quorum disk - it has 1 vote (on 1 less then number of nodes).
I added then 1 node - and update configuration so that Expected votes=3
But Quorum votes didnot change - it 's equal to 1, but in config i
Christopher Chen wrote:
If the machines choose to use local time instead of UTC for cluster
management, I'd say that's a bug.
Indeed it would be a bug.
I don't think its ever been explicitly tested but it really should be
fine, and if it isn't we want to know about it.
On Tue, Apr 7, 2009
Gianluca Cecchi wrote:
Conversely, how is it dangerous to have two two-node-clusters with
different names sharing the intra-cluster network?
In particular if one is in production and the other is for testing?
And what about relative multicast-adresses for these two clusters? Can
I safely use
Vu Pham wrote:
Chen Ming wrote:
Hi,
I setup two cluster in same subnet, using the same name, it seems the
later cluster can not startup. I try to start cman but failed. My
environment is RHEL 5.3.
My question: Is it possible to use the same cluster name in same subnet?
From the man
Chaitanya Kulkarni wrote:
Hi All,
What happens if in the same network, we try to create two clusters with
the same name?
Does it cause any problem?
YES LOTS!
At best the two clusters will merge into one, at worst you will get node
evictions because of clashes between node IDs
Actually
would I work it out?! Cluster names are chosen by the
administrators ... those people are not easily predictable ;-)
Chrissie
On Mon, Mar 16, 2009 at 1:28 PM, Chrissie Caulfield ccaul...@redhat.com
mailto:ccaul...@redhat.com wrote:
Chaitanya Kulkarni wrote:
Hi All,
What
Alain.Moulle wrote:
Hi ,
it seems that the CS5 supports up to 128 nodes ...
(whereas it was 8 with CS3 and CS4 ? )
did some of you have tested at least the CS5 with more than 10 nodes ?
does it reveal any big problem or restriction to have big clusters with
CS5 ?
I have tested Red Hat
Gordan Bobic wrote:
I have a two-node cluster and ever since I updated the kernel and
cluster components I cannot get more than one node running with GFS.
Here are the package versions I have:
kernel-2.6.18-92.1.22.el5
cman-2.0.98-1
kmod-gfs-0.1.23-5.el5_2.4
gfs-utils-0.1.17-1.el5
Doug Bunger wrote:
I'm having trouble making the cluster aware of changes in Fedora 10
(x86_64). The setup has three VMs accessing a shared, attached
partition, formatted as GFS.When modifying the cluster.conf and
incrementing version number, I have to boot the nodes. I've found some
enormously too.
It's possible that the workaround program I posted in the BZ might
mitigate the problem a little, but without knowing much more about what
is happening I can't honestly be sure.
Chrissie
-Mark
On Wednesday 11 February 2009 10:17:30 Chrissie Caulfield wrote:
thijn wrote:
Hi
Alain.Moulle wrote:
Hi,
I'm facing again this problem of Node evicted and Node is undead ...
And I really don't know what to do ... below are the traces in syslog.
My version is :RHEL5.3 / cman-2.0.98-1.el5
Feb 25 14:33:33 s_...@xn3 qdiskd[27582]: notice Writing eviction
notice for node
thijn wrote:
Hi,
I have the following problem.
CMAN: removing node [server1] from the cluster : Missed too many
heartbeats
When the server comes back up:
Feb 10 14:43:58 server1 kernel: CMAN: sending membership request
after which it will try to join until the end of times.
In the
Alain.Moulle wrote:
Hi ,
About this problem, I wonder if it is a definitive behavior considered
as normal ?
or if this will work differently in a next release of cman or openais ?
(in previous versions with cman-2.0.73, we did not had this problem)
Thanks if someone could give an answer...
Vivek Purohit wrote:
Hi Steve,
Thanks for the previous reply.
I was able to run the checkpointing tests in the tarball Openais
on RHEL 5.
I explored and came to know that the CMAN service of RHEL 5's
clustersuite runs as aisexec; thus the tests could be run directly.
Can you please
On Wed, Jan 14, 2009 at 4:02 PM, Chrissie Caulfield ccaul...@redhat.com
mailto:ccaul...@redhat.com wrote:
Chaitanya Kulkarni wrote:
Hi,
Following is output of my cman_tool status -
Protocol version: 5.0.1
Config version: 40
Cluster name: cluster1
Chaitanya Kulkarni wrote:
Hi,
Following is output of my cman_tool status -
Protocol version: 5.0.1
Config version: 40
Cluster name: cluster1
Cluster ID: 39377
Cluster Member: Yes
Membership state: Cluster-Member
Nodes: 2
Expected_votes: 1
Total_votes: 2
Quorum: 1
Active
Jeff Sturm wrote:
What might cause a message like:
Jan 12 08:41:24 t0core-mqc02 openais[1716]: [CMAN ] Node 8 conflict,
remote cluster name='t0core-inner-rhcxvm', local='t0core-inner-rhc'
I've double- and triple-checked that /etc/cluster/cluster.conf is
identical on every node. It
Stewart Walters wrote:
Hello List Members,
I've just joined, so please forgive me in advance if I break some list
etiquette :-)
I have a two node cluster (RHEL5) whereby running cman_tool nodes on
each node net's the following results:
[r...@node01 ~]# cman_tool nodes
Node Sts Inc
victory.xu wrote:
when i run service cman start
the error in the /var/log/messages
kernel: ioctl32(cman_tool:5382): Unknown cmd fd(3) cmd(2000780b){' '}
arg(42000422) on socket:[17147]
At a very quick guess that looks like the tools have been built as 32bit
and the kernel is 64
Sven Carstens wrote:
Hi all,
this is a ubuntu-8.10 dual node cluster.
Starting the cluster by rebooting both nodes works ok.
But when I update the cluster.conf with ccs_tool update the
update won't be noticed by cman until the next reboot.
[node1/2]cman_tool status:
27 matches
Mail list logo
