Setting up HACMP 6.1 on a two node cluster. The other node works fine and can start properly on STABLE state (VGs varied, FS mounted, Service IP aliased). However, the other node is always stuck on ST_JOINING state. Its taking forever and you can't stop the cluster as well or recover from script failure. I can't see any error from hacmp.out.
Here's the latest error I see from clstrmgr.debug (This is from console so I just type it here
---------- Post updated at 03:52 AM ---------- Previous update was at 03:47 AM ----------
Also one thing to add is that, I can start the cluster on any node as long as I have not started any other node. Meaning I can start the cluster and RG on either node1 and node2 but If I start it on node1, node2 won't bring up by clstart and shows as ST_JOINING forever. Thus, I cannot do a failover to other node unless the other node is in stable state.
Last edited by Scrutinizer; 06-08-2013 at 06:22 AM..
Reason: code tags
Hello,
Under ksh I have to run a script on one of the nodes of a Solaris 8 cluster which at some time must execute a command on the alternate node:
# rsh <name> "command"
I have to implement this script on all the clusters of my company (a lot of...).
Fortunately, the names of the two nodes... (11 Replies)
Hi,
Please advise me whereas I have two node cluster server configured with MC/SG. Application and DB are running on Node 1, while Node 2 is standby.
All the volume group devices are part of cluster environment. There is only one package running at node 1.
Node 2 is having the problem to... (1 Reply)
hi,
i am trying to setup a 2 node cluster environment. following is what i have;
1. 2 x sun ultra60 - 450MHz procs, 1GB RAM, 9GB HDD, solaris 10
2. 2 x HBA cards
3. 2 x Connection leads to connect ultra60 with D1000
4. 1 x D1000 storage box.
5. 3 x 9GB HDD + 2 x 36GB HDD
first of all,... (1 Reply)
Hi Gurus,
For learning purpose, I have installed a single node cluster 3.2 on Solaris 10 for practice. Now I am welling to create two non-global zone and create them as a fail over. Will appreciate your help and assistance.
Thanks (3 Replies)
Hi Gurus,
I am very new to clustering and for test i have created a single node cluster, now i want to remove the system from cluster. Did some googling however as a newbee in cluster unable to co related the info.
Please help
Thanks (1 Reply)
How can we add a shared zfs dataset between 2 zones on a same host. I have sun cluster 3.2 installed in a server which has 2 zones. I want to share a zfs data set between these 2 zones how can we do that ? (7 Replies)
Hi,
Is it possible to have a Solaris cluster of 2 nodes at SITE-A using SVM and creating metaset using say 2 LUNs (on SAN). Then replicating these 2 LUNs to remote site SITE-B via storage based replication and then using these LUNs by importing them as a metaset on a server at SITE-B which is... (0 Replies)
Discussion started by: dn2011
0 Replies
LEARN ABOUT SUSE
crm_standby
CRM_STANDBY(8) [FIXME: manual] CRM_STANDBY(8)NAME
crm_standby - manipulate a node's standby attribute to determine whether resources can be run on this node
SYNOPSIS
crm_standby [-?|-V] -D -u|-U node -r resource
crm_standby [-?|-V] -G -u|-U node -r resource
crm_standby [-?|-V] -v string -u|-U node -r resource [-l string]
DESCRIPTION
The crm_standby command manipulates a node's standby attribute. Any node in standby mode is no longer eligible to host resources and any
resources that are there must be moved. Standby mode can be useful for performing maintenance tasks, such as kernel updates. Remove the
standby attribute from the node when it should become a fully active member of the cluster again.
By assigning a lifetime to the standby attribute, determine whether the standby setting should survive a reboot of the node (set lifetime
to forever) or should be reset with reboot (set lifetime to reboot). Alternatively, remove the standby attribute and bring the node back
from standby manually.
OPTIONS --help, -?
Print a help message.
--verbose, -V
Turn on debug information.
Note
Increase the level of verbosity by providing additional instances.
--quiet, -Q
When doing an attribute query using -G, print just the value to stdout. Use this option with -G.
--get-value, -G
Retrieve rather than set the preference.
--delete-attr, -D
Specify the attribute to delete.
--attr-value string, -v string
Specify the value to use. This option is ignored when used with -G.
--node-uuid node_uuid, -u node_uuid
Specify the UUID of the node to change.
--node-uname node_uname, -U node_uname
Specify the uname of the node to change.
--lifetime string, -l string
Determine how long this preference lasts. Possible values are reboot or forever.
Note
If a forever value exists, it is always used by the CRM instead of any reboot value.
EXAMPLES
Have a local node go to standby:
crm_standby -v true
Have a node (node1) go to standby:
crm_standby -v true -U node1
Query the standby status of a node:
crm_standby -G -U node1
Remove the standby property from a node:
crm_standby -D -U node1
Have a node go to standby for an indefinite period of time:
crm_standby -v true -l forever -U node1
Have a node go to standby until the next reboot of this node:
crm_standby -v true -l reboot -U node1
FILES
/var/lib/heartbeat/crm/cib.xml--the CIB (minus status section) on disk. Editing this file directly is strongly discouraged.
SEE ALSO
???, ???
AUTHOR
crm_standby was written by Andrew Beekhof.
[FIXME: source] 07/05/2010 CRM_STANDBY(8)