Apple Qmaster: Sharing sometimes does not enable with custom shared cluster storage p
Sharing sometimes does not successfully start when you have set a custom shared cluster storage path. When you click Start Sharing in the Apple Qmaster System Preferences pane, the button dims and may not switch to Stop Sharing. If you quit System Preferences and reopen it, the Stop Sharing button may appear to be active, but the Quickcluster may not be available in Compressor.
Hi guys.
I have a custom application which is written by java. I want to know is it possible to cluster this application by pacemaker. For example copy this application in two different nodes and setup a cluster by pacemaker. In one time only one application work and when primary node goes... (8 Replies)
Hi
I want the Sync file server together (at the moment)
All server to a web server
What can I do to update Joomla or WordPress files even when taken together are equal
Databases together are replicated
What is the solutions ?
Thanks (2 Replies)
Hi,
I perform clrs enable/disable resource-group to start/shutown sybase db.
If I do it through through scsetup , it asks for Do you require to change the state of resource "sybaseapp-rs" on individual nodes or zones that can master the resource (yes/no) ?.
I am bit confused of above... (1 Reply)
Hi experts, I have some custom application which I need to make Highly Available using red hat cluster service. How do I do it? i know in /usr/share/cluster i shall find HA agents for well known services like Apache or Sybase but I want to write HA agent for my own. I tried looking up on... (4 Replies)
Does anyone know of any way to share storage between 2 machines without networking?
I have a server that is constantly connected to a VPN that cuts off network access to every non-VPN network. This presents a problem when I have to transfer big files off of that server on to my internal... (7 Replies)
cmrunnode(1m)cmrunnode(1m)NAME
cmrunnode - run a node in a high availability cluster
SYNOPSIS
cmrunnode [-v] [node_name...] [-t | -w none]
DESCRIPTION
cmrunnode causes a node to start its cluster daemon to join the existing cluster. This command verifies the network configuration before
causing the node to start its cluster daemon.
To start a cluster on one of its nodes, a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the clus-
ter configuration file. See access policy in cmquerycl(1m).
Starting a node will not cause any active packages to be moved to the new node. However, if a package is DOWN, has its switching enabled,
and is able to run on the new node, that package will automatically run there.
If node_name is not specified, the cluster daemon will be started on the local node and will join the existing cluster.
Options
cmrunnode supports the following options:
-v Verbose output will be displayed.
-t Test only. Provide an assessment of the package placement without affecting the current state of the nodes or packages. The -w
option is not required with the -t option as -t does not validate network connectivity, but assumes that all the nodes can meet
any external dependencies such as EMS resources, package subnets, and storage.
node_name...
Start the cluster daemon on the specified node(s).
-w none
By default network probing is performed to check that the network connectivity is the same as when the cluster was configured.
Any anomalies are reported before the cluster daemons are started. The -w none option disables this probing. The option should
only be used if this network configuration is known to be correct from a recent check.
RETURN VALUE
cmrunnode returns the following value:
0 Successful completion.
1 Command failed.
EXAMPLES
Run the cluster daemon on the current node:
cmrunnode
Run the cluster daemons on node1 and node2:
cmrunnode node1 node2
AUTHOR
cmrunnode was developed by HP.
SEE ALSO cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmruncl(1m), cmviewcl(1m), cmeval(1m).
Requires Optional Serviceguard Software cmrunnode(1m)