Index for Section 8

Alphabetical listing for C

Bottom of page

caad(8)
NAME
  caad - Cluster Application Availability (CAA) daemon

SYNOPSIS
  /usr/sbin/caad

DESCRIPTION
  The CAA daemon (caad) monitors CAA resources and keeps CAA-managed
  applications highly available by starting, stopping, relocating and
  restarting application resources when failure conditions occur.  The daemon
  is an asynchronous, event-driven process that is started automatically when
  the system transitions to boot level 3.  It works in conjunction with the
  CAA profiler and the CAA user interface.  Do not stop the CAA daemon or the
  monitoring and management of CAA-managed applications will be disrupted.
  This could jeopardize the availability of CAA-managed applications within
  the cluster.

  A resource profile describes a resource's failover criteria and relocation
  requirements.	 An administrator creates a resource profile for each
  resource to be monitored by the CAA daemon. The resource profile can be
  created for a network resource or an application resource. Resource
  profiles are stored in the /var/cluster/caa/profile directory.

  For CAA-managed applications, the resource profile specifies values that
  describe how the caad daemon manages the application. This includes, the
  placement policy, required resources, hosting members, and other
  properties. The profile also specifies the action script that is used to
  start, and stop the application.

  See caa_profile(8) and caa(4) for more information on resource profiles.

  Each cluster member runs an instance of the CAA daemon.  These instances
  run autonomously, but communicate to share cluster and resource state
  information.

  Upon startup of the cluster system each CAA daemon reads from the registry
  database file (/var/cluster/caa/registry/caa.reg). The CAA daemon
  determines after reading the registry database the last state of the
  cluster and all registered available resources when the node failed or was
  shut down.

  The CAA daemon determines the state of the cluster, its ready-state, and
  health for that cluster member.  If resources are or were previously
  registered, a booting CAA daemon will determine if each resource is
  currently available within the CAA subsystem.

  For all registered application resources not currently running, the CAA
  daemon attempts to start these resources and begins monitoring all other
  types of resources.  How an application resource is started is determined
  by the resource's startup script.

  Each application resource in the CAA subsystem is under the direct control
  of the cluster member currently running.  If under any circumstances, the
  resource is no longer available, all CAA daemons in the CAA subsystem
  arbitrate to take control of it.

  The caad daemon logs information into the EVM event management system. See
  EVM(5) for more information on viewing information in EVM.

EXIT VALUES
  The following exit values are returned:

  0   Successful completion

  non-zero
      A failure has occurred.

SEE ALSO
  Commands: caa_stat(1), caa_profile(8), caa_register(8), caa_relocate(8),
  caa_start(8),caa_stop(8), caa_unregister(8)

  File:	 caa(4)

  TruCluster Server Cluster Administration

Index for Section 8

Alphabetical listing for C

Top of page