2. Host-Local Configuration
Note
Directory and file paths below may differ on your system depending on your Pacemaker build settings. Check your Pacemaker configuration file to find the correct paths.
Pacemaker supports several host-local configuration options. These options can
be configured on each node in the main Pacemaker configuration file
(/etc/sysconfig/pacemaker
) in the format <NAME>="<VALUE>"
. They work by setting
environment variables when Pacemaker daemons start up.
Name |
Type |
Default |
Description |
---|---|---|---|
PCMK_logfacility |
daemon |
Enable logging via the system log or journal, using the specified log
facility. Messages sent here are of value to all Pacemaker
administrators. This can be disabled using
|
|
PCMK_logpriority |
notice |
Unless system logging is disabled using
|
|
PCMK_logfile |
/var/log/pacemaker/pacemaker.log |
Unless set to |
|
PCMK_logfile_mode |
0660 |
Pacemaker will set the permissions on the detail log to this value (see
|
|
PCMK_debug |
no |
Whether to send debug severity messages to the detail log. This may be
set for all subsystems (
Example: |
|
PCMK_stderr |
no |
Advanced Use Only: Whether to send daemon log messages to stderr. This would be useful only during troubleshooting, when starting Pacemaker manually on the command line. Setting this option in the configuration file is pointless, since the file is not read when starting Pacemaker manually. However, it can be set directly as an environment variable on the command line. |
|
PCMK_trace_functions |
Advanced Use Only: Send debug and trace severity messages from these (comma-separated) source code functions to the detail log. Example:
|
||
PCMK_trace_files |
Advanced Use Only: Send debug and trace severity messages from all functions in these (comma-separated) source file names to the detail log. Example: |
||
PCMK_trace_formats |
Advanced Use Only: Send trace severity messages that are generated by these (comma-separated) format strings in the source code to the detail log. Example: |
||
PCMK_trace_tags |
Advanced Use Only: Send debug and trace severity messages related to these (comma-separated) resource IDs to the detail log. Example: |
||
PCMK_blackbox |
no |
Advanced Use Only: Enable blackbox logging globally ( The blackbox recorder can be enabled at start using this variable, or at
runtime by sending a Pacemaker subsystem daemon process a See PCMK_debug for allowed subsystems. Example:
|
|
PCMK_trace_blackbox |
Advanced Use Only: Write a blackbox whenever the message at the specified function and line is logged. Multiple entries may be comma- separated. Example: |
||
PCMK_node_start_state |
default |
By default, the local host will join the cluster in an online or standby
state when Pacemaker first starts depending on whether it was previously
put into standby mode. If this variable is set to |
|
PCMK_node_action_limit |
Specify the maximum number of jobs that can be scheduled on this node. If
set, this overrides the |
||
PCMK_shutdown_delay |
Specify a delay before shutting down |
||
PCMK_fail_fast |
no |
By default, if a Pacemaker subsystem crashes, the main |
|
PCMK_panic_action |
reboot |
Pacemaker will panic the local host under certain conditions. By default,
this means rebooting the host. This variable can change that behavior: if
|
|
PCMK_authkey_location |
/etc/pacemaker/authkey |
Use the contents of this file as the authorization key to use with
Pacemaker Remote connections. This file must be readable by Pacemaker
daemons (that is, it must allow read permissions to either the
|
|
PCMK_remote_address |
By default, if the Pacemaker Remote service is run on the local node, it will listen for connections on all IP addresses. This may be set to one address to listen on instead, as a resolvable hostname or as a numeric IPv4 or IPv6 address. When resolving names or listening on all addresses, IPv6 will be preferred if available. When listening on an IPv6 address, IPv4 clients will be supported via IPv4-mapped IPv6 addresses. Example: |
||
PCMK_remote_port |
3121 |
Use this TCP port number for Pacemaker Remote node connections. This value must be the same on all nodes. |
|
PCMK_remote_pid1 |
default |
Advanced Use Only: When a bundle resource’s This option controls whether those actions are performed when Pacemaker
Remote is not running as PID 1. It is intended primarily for developer
testing but can be useful when
If Pacemaker Remote is running as PID 1, this option is ignored, and the
behavior is the same as for |
|
PCMK_tls_priorities |
NORMAL |
Advanced Use Only: These GnuTLS cipher priorities will be used for TLS connections (whether for Pacemaker Remote connections or remote CIB access, when enabled). See: Pacemaker will append Example:
|
|
PCMK_dh_min_bits |
0 (no minimum) |
Advanced Use Only: Set a lower bound on the bit length of the prime number generated for Diffie-Hellman parameters needed by TLS connections. The default is no minimum. The server (Pacemaker Remote daemon, or CIB manager configured to accept remote clients) will use this value to provide a floor for the value recommended by the GnuTLS library. The library will only accept a limited number of specific values, which vary by library version, so setting these is recommended only when required for compatibility with specific client versions. Clients (connecting cluster nodes or remote CIB commands) will require that the server use a prime of at least this size. This is recommended only when the value must be lowered in order for the client’s GnuTLS library to accept a connection to an older server. |
|
PCMK_dh_max_bits |
0 (no maximum) |
Advanced Use Only: Set an upper bound on the bit length of the prime number generated for Diffie-Hellman parameters needed by TLS connections. The default is no maximum. The server (Pacemaker Remote daemon, or CIB manager configured to accept remote clients) will use this value to provide a ceiling for the value recommended by the GnuTLS library. The library will only accept a limited number of specific values, which vary by library version, so setting these is recommended only when required for compatibility with specific client versions. Clients do not use |
|
PCMK_ipc_type |
shared-mem |
Advanced Use Only: Force use of a particular IPC method. Allowed values:
|
|
PCMK_ipc_buffer |
131072 |
Advanced Use Only: Specify an IPC buffer size in bytes. This can be useful when connecting to large clusters that result in messages exceeding the default size (which will also result in log messages referencing this variable). |
|
PCMK_cluster_type |
corosync |
Advanced Use Only: Specify the cluster layer to be used. If unset,
Pacemaker will detect and use a supported cluster layer, if available.
Currently, |
|
PCMK_schema_directory |
/usr/share/pacemaker |
Advanced Use Only: Specify an alternate location for RNG schemas and XSL transforms. |
|
PCMK_valgrind_enabled |
no |
Advanced Use Only: Whether subsystem daemons should be run under
|
|
PCMK_callgrind_enabled |
no |
Advanced Use Only: Whether subsystem daemons should be run under
|
|
VALGRIND_OPTS |
Advanced Use Only: Pass these options to valgrind, when enabled (see
|