7 More Discussions You Might Find Interesting
1. Red Hat
Hi Guys,
I am not much aware of clusters but i have few questions can someone provide the overview as it would be very helpful for me.
How can i perform cluster failover test to see all the services are failing back to other node ? If it is using veritas cluster then what kind of... (2 Replies)
Discussion started by: munna529
2 Replies
2. Shell Programming and Scripting
Hi all,
we have setup one cluster with two nodes.
-drbd
-corosync
-pacemaker
-mysql
-piranha
sometimes, we loose connection between the two nodes (node 1 and node 2). When this happens, the two nodes starts both the services as masters,because they don't see each other.
is there any way... (2 Replies)
Discussion started by: arrals_vl
2 Replies
3. Red Hat
Hi all experts,
I need your kind suggestions or feedback on choice of clustering software for red hat linux nodes running certain applications which I need to make highly available.
Minimum requirement is 2 nodes; all nodes shall be active-active running distinct applications e.g. node 1 runs... (1 Reply)
Discussion started by: pshaikh
1 Replies
4. High Performance Computing
Hi, I am not sure if the term "cluster" fits my situation or not. I have 5 Linux computers, each has different a host-name, and my users have to remember those the computer names to login and find out which computers have free CPUs, so they can run their jobs on those computers have free CPUs.
... (4 Replies)
Discussion started by: hiepng
4 Replies
5. High Performance Computing
Hi Guys,
I'm busy building a LVS-NAT cluster on Red-Hat server 5.1 and I need a kernel that has LVS capabilities for a red-hat server 5.1. Is the anyone who can advise me where I can get this kernel. I have already visited the following site Ultra Monkey: and this has old kernels e.g. 2.4.20... (2 Replies)
Discussion started by: Linux Duke
2 Replies
6. Linux
Hi,
Hi,
I work in NGO. They are migrating from windows to Linux. They can't spend so much money on servers. They have around 50 PCs. So I want to setup cluster on 2-3 PCs or more than that for setting up server. I am excepted to get their collective output. So that it will be compatible with... (5 Replies)
Discussion started by: neel.gurjar
5 Replies
7. UNIX for Dummies Questions & Answers
I have created a linux cluster using ROCKS. I have 4 comps hooked up now. front-end plus 3 nodes. Looking for way to test the system to see how effective it is (and if it actually works). Any help would be appreciated. (1 Reply)
Discussion started by: skatinsky
1 Replies
LEARN ABOUT DEBIAN
cl_status
CL_STATUS(1) User commands CL_STATUS(1)
NAME
cl_status - Check status of the High-Availability Linux (Linux-HA) subsystem
SYNOPSIS
cl_status sub-command options parameters
DESCRIPTION
cl_status is used to check the status of the High-Availability Linux subsystem.
SUPPORTED SUB-COMMANDS
hbstatus
Indicate if heartbeat is running on the local system.
listnodes
List the nodes in the cluster.
nodetype ping|normal
List the nodes of the given type.
Note
Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent.
listhblinks node
List the network interfaces used as heartbeat links. node should be specified as listed in the ha.cf(5) file for the cluster.
hblinkstatus node link
Show the status of a heartbeat link. node should be specified as listed in the ha.cf(5) file for the cluster. link should be as per
the output of the listhblinks subcommand.
clientstatus node client [timeout]
Show the status of heartbeat clients. node and client should be specified as listed in the ha.cf(5) file for the cluster. Timeout is
in milliseconds, the default is 100ms.
rscstatus
Show the status of cluster resources. Status will be one of: local, foreign, all or none.
Note
This option is deprecated, it is obsolete in Pacemaker clusters.
parameter -p parameter
Retrieve the value of cluster parameters. The parameters may be one of the following: apiauth, auto_failback, baud, debug, debugfile,
deadping, deadtime, hbversion, hopfudge, initdead, keepalive, logfacility, logfile, msgfmt, nice_failback, node, normalpoll, stonith,
udpport, warntime, watchdog.
Note
Some of these options are deprecated; see ha.cf(5)
OPTIONS
The following options are supported by heartbeat:
-m
Make the output more human readable. The default output should be easier for scripts to parse. Available with all commands.
-p
List only 'ping' nodes. Available with listnodes sub-command.
Note
Ping nodes are obsolete in Pacemaker cluster, having been replaced with the pingd resource agent.
-n
List only 'normal' nodes. Available with listnodes sub-command.
SEE ALSO
heartbeat(8), ha.cf(5), authkeys(5)
AUTHORS
Alan Robertson <alanr@unix.sh>
cl_status
Juan Pedro Paredes Caballero <juampe@retemail.es>
man page
Simon Horman <horms@verge.net.au>
man page
Florian Haas <florian.haas@linbit.com>
man page
Heartbeat 3.0.5 24 Nov 2009 CL_STATUS(1)