Login or Register to Ask a Question and Join Our Community


OS X Support RSS

Apple Qmaster: Sharing sometimes does not enable with custom shared cluster storage p

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Operating Systems OS X (Apple) OS X Support RSS Apple Qmaster: Sharing sometimes does not enable with custom shared cluster storage p
# 1  
Old 11-25-2008
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.

More from Apple OS X Support ...
Login or Register to Ask a Question

Previous Thread | Next Thread

6 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

Cluster a custom application

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)
Discussion started by: mhs
8 Replies

2. Red Hat

Storage Cluster ?

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)
Discussion started by: mnnn
2 Replies

3. Solaris

Sun Cluster query for enable/disable

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)
Discussion started by: tuxian
1 Replies

4. Red Hat

Custom HA agent - Red Hat Linux Cluster

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)
Discussion started by: pshaikh
4 Replies

5. UNIX for Advanced & Expert Users

Sharing storage, no network

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)
Discussion started by: tjlst15
7 Replies

6. UNIX for Advanced & Expert Users

mmap vs shared memory - which is best for sharing data between applications?

Between mmap and shared memory which is the best method of sharing data between multiple applications, interms of speed? (2 Replies)
Discussion started by: nmds
2 Replies
Login or Register to Ask a Question

LEARN ABOUT HPUX

cmruncl

cmruncl(1m)															       cmruncl(1m)

NAME

       cmruncl - run a high availability cluster

SYNOPSIS

       cmruncl [-f] [-v] [-n node_name...]  [-t | -w none]

DESCRIPTION

       cmruncl causes all nodes in a configured cluster or all nodes specified to start their cluster daemons and form a new cluster.

       To  start  a  cluster,  a user must either be superuser(UID=0), or have an access policy of FULL_ADMIN allowed in the cluster configuration
       file. See access policy in cmquerycl(1m).

       This command should only be run when the cluster is not active on any of the configured nodes.  This command verifies the network  configu-
       ration  before  causing	the nodes to start their cluster daemons.  If a cluster is already running on a subset of the nodes, the cmrunnode
       command should be used to start the remaining nodes and force them to join the existing cluster.

       If node_name is not specified, the cluster daemons will be started on all the nodes in the cluster.  All  nodes	in  the  cluster  must	be
       available for the cluster to start unless a subset of nodes is specified.

   Options
       cmruncl supports the following options:

	      -f	Force cluster startup without warning message and continuation prompt that are printed with the -n option.

	      -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.

	      -n  node_name...
			Start the cluster daemon on the specified subset of node(s).

	      -w none	By default network probing is performed to check that the network connectivity is the same as when the cluster was config-
			ured. 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
	      cmruncl returns the following value:

	       0   Successful completion.
	       1   Command failed.

EXAMPLES

       Run the cluster daemon:

	      cmruncl

       Run the cluster daemons on node1 and node2:

	      cmruncl -n node1 -n node2

AUTHOR

       cmruncl was developed by HP.

SEE ALSO

       cmquerycl(1m), cmhaltcl(1m), cmhaltnode(1m), cmrunnode(1m), cmviewcl(1m), cmeval(1m).

						      Requires Optional Serviceguard Software					       cmruncl(1m)