| Linux FailSafe™ Administrator's Guide | ||
|---|---|---|
| Prev | Chapter 3. Installing Linux FailSafe Software and Preparing the System | Next |
When you install the Linux FailSafe Software, there are some system file considerations you must take into account. This section describes the required and optional changes you make to the following files for every node in the pool:
/etc/services
/etc/failsafe/config/cad.options
/etc/failsafe/config/cdbd.options
/etc/failsafe/config/cmond.options
The /etc/services file must contain entries for sgi-cmsd, sgi-crsd, sgi-gcd, and sgi-cad on each node before starting HA services in the node. The port numbers assigned for these processes must be the same in all nodes in the cluster. Note that sgi-cad requires a TCP port.
The following shows an example of /etc/services entries for sgi-cmsd, sgi-crsd, sgi-gcd and sgi-cad:
sgi-cmsd 7000/udp # SGI Cluster Membership Daemon sgi-crsd 17001/udp # Cluster reset services daemon sgi-gcd 17002/udp # SGI Group Communication Daemon sgi-cad 17003/tcp # Cluster Admin daemon |
The /etc/failsafe/config/cad.options file contains the list of parameters that the cluster administration daemon (CAD) reads when the process is started. The CAD provides cluster information to the Linux FailSafe Cluster Manager GUI.
The following options can be set in the cad.options file:
Append CAD logging information to the CAD log file instead of overwriting it.
CAD log file name. Alternately, this can be specified as -lf filename.
Verbosity level. The number of “v”s indicates the level of logging. Setting -v logs the fewest messages. Setting -vvvv logs the highest number of messages.
The following example shows an /etc/failsafe/config/cad.options file:
-vv -lf /var/log/failsafe/cad_nodename --append_log |
When you change the cad.options file, you must restart the CAD processes with the /etc/rc.d/init.d/fs_cluster restart command for those changes to take affect.
The /etc/failsafe/config/cdbd.options file contains the list of parameters that the cdbd daemon reads when the process is started. The cdbd daemon is the configuration database daemon that manages the distribution of cluster configuration database (CDB) across the nodes in the pool.
The following options can be set in the cdbd.options file:
Log selected events. These event names may be used: all, internal, args, attach, chandle, node, tree, lock, datacon, trap, notify, access, storage.
The default value for this option is all.
Set log destination. These log destinations may be used: all, stdout, stderr, syslog, logfile. If multiple destinations are specified, the log messages are written to all of them. If logfile is specified, it has no effect unless the -logfile option is also specified. If the log destination is stderr or stdout, logging is then disabled if cdbd runs as a daemon, because stdout and stderr are closed when cdbd is running as a daemon.
The default value for this option is logfile.
Set log file name.
The default value is /var/log/failsafe/cdbd_log
Set log file maximum size (in bytes). If the file exceeds the maximum size, any preexisting filename.old will be deleted, the current file will be renamed to filename.old, and a new file will be created. A single message will not be split across files.
If -logfile is set, the default value for this option is 10000000.
Set log level. These log levels may be used: always, critical, error, warning, info, moreinfo, freq, morefreq, trace, busy.
The default value for this option is info.
Trace selected events. These trace classes may be used: all, rpcs, updates, transactions, monitor. No tracing is done, even if it is requested for one or more classes of events, unless either or both of -tracefile or -tracelog is specified.
The default value for this option is transactions.
Set trace file name.
Set trace file maximum size (in bytes). If the file exceeds the maximum size, any preexisting filename.old will be deleted, the current file will be renamed to filename.old.
[Do not] trace to log destination. When this option is set, tracing messages are directed to the log destination or destinations. If there is also a trace file, the tracing messages are written there as well.
[Do not] exit when parent exits.
The default value for this option is -noparent_timer.
[Do not] run as a daemon.
The default value for this option is -daemonize.
Do not run as a daemon.
Print usage message.
Print usage message.
Note that if you use the default values for these options, the system will be configured so that all log messages of level info or less, and all trace messages for transaction events to file /var/log/failsafe/cdbd_log. When the file size reaches 10MB, this file will be moved to its namesake with the .old extension, and logging will roll over to a new file of the same name. A single message will not be split across files.
The following example shows an /etc/failsafe/config/cdbd.options file that directs all cdbd logging information to /var/log/messages, and all cdbd tracing information to /var/log/failsafe/cdbd_ops1. All log events are being logged, and the following trace events are being logged: RPCs, updates and transactions. When the size of the tracefile /var/log/failsafe/cdbd_ops1 exceeds 100000000, this file is renamed to /var/log/failsafe/cdbd_ops1.old and a new file /var/log/failsafe/cdbd_ops1 is created. A single message is not split across files.
-logevents all -loglevel trace -logdest syslog -trace rpcs -trace updates -trace transactions -tracefile /var/log/failsafe/cdbd_ops1 -tracefilemax 100000000 |
The following example shows an /etc/failsafe/config/cdbd.options file that directs all log and trace messages into one file, /var/log/failsafe/cdbd_chaos6, for which a maximum size of 100000000 is specified. -tracelog directs the tracing to the log file.
-logevents all -loglevel trace -trace rpcs -trace updates -trace transactions -tracelog -logfile /var/log/failsafe/cdbd_chaos6 -logfilemax 100000000 -logdest logfile. |
When you change the cdbd.options file, you must restart the cdbd processes with the /etc/rc.d/init.d/fs_cluster restart command for those changes to take affect.
The/etc/failsafe/config/cmond.options file contains the list of parameters that the cluster monitor daemon (cmond) reads when the process is started. It also specifies the name of the file that logs cmond events. The cluster monitor daemon provides a framework for starting, stopping, and monitoring process groups. See the cmond man page for information on the cluster monitor daemon.
The following options can be set in the cmond.options file:
Set log level to loglevel
Run in debug mode
Lazy mode, where cmond does not validate its connection to the cluster database
The time interval in milliseconds after which cmond checks for liveliness of process groups it is monitoring
Log messages to stderr
A default cmond.options file is shipped with the following options. This default options file logs cmond events to the /var/log/failsafe/cmond_log file.
-L info -f /var/log/failsafe/cmond_log |