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)
PACEMAKER(8) System Administration Utilities PACEMAKER(8)NAME
Pacemaker - Part of the Pacemaker cluster resource manager
SYNOPSIS
crm_node command [options]
DESCRIPTION
crm_node - Tool for displaying low-level node information
OPTIONS
-?, --help
This text
-$, --version
Version information
-V, --verbose
Increase debug output
-Q, --quiet
Essential output only
Stack:
-A, --openais
Only try connecting to an OpenAIS-based cluster
-H, --heartbeat
Only try connecting to a Heartbeat-based cluster
Commands:
-n, --name
Display the name used by the cluster for this node
-N, --name-for-id=value
Display the name used by the cluster for the node with the specified id
-e, --epoch
Display the epoch during which this node joined the cluster
-q, --quorum
Display a 1 if our partition has quorum, 0 if not
-l, --list
Display all known members (past and present) of this cluster (Not available for heartbeat clusters)
-p, --partition
Display the members of this partition
-i, --cluster-id
Display this node's cluster id
-R, --remove=value
(Advanced) Remove the (stopped) node with the specified name from Pacemaker's configuration and caches
In the case of Heartbeat, CMAN and Corosync 2.0, requires that the node has already been removed from the underlying cluster
Additional Options:
-f, --force
AUTHOR
Written by Andrew Beekhof
REPORTING BUGS
Report bugs to pacemaker@oss.clusterlabs.org
Pacemaker 1.1.10-29.el7 June 2014 PACEMAKER(8)