1CLUSTER.CONF(5) cluster CLUSTER.CONF(5)
2
3
4
6 cluster.conf - configuration file for cman and related daemons
7
8
10 /etc/cluster/cluster.conf
11
12
14 When cman_tool(8) starts the corosync(8) daemon, the cluster.conf data
15 is read into the corosync in-memory database (confdb). The configura‐
16 tion is used by corosync, cman and other related cluster daemons and
17 programs. When cman configures corosync with cluster.conf, the
18 corosync.conf(5) file is not used.
19
20 A basic cluster configuration is described below. Configuration
21 options for other daemons/programs are described in their own man
22 pages. ccs_tool(8) can be used to do some basic cluster.conf editing.
23
24 The cluster.rng schema is used to validate cluster.conf. Unrecognized
25 items will produce a warning during cluster startup, and invalid xml
26 structure will cause the cluster startup to fail. See ccs_config_vali‐
27 date(8) and ccs_config_dump(8).
28
29
30 Cluster
31 The top level cluster section contains all other sections and has two
32 required attributes:
33
34 name The name of the cluster can be up to 15 characters long (16
35 including terminating null). It is important that this name be
36 unique among clusters on the same network.
37
38 config_version
39 The config_version specifies the revision level of the file and
40 should be increased each time the file is updated.
41
42 <cluster name="alpha" config_version="1">
43 </cluster>
44
45
46 Cluster Nodes
47 The set of nodes that make up the cluster are defined in the clustern‐
48 odes section which contains multiple clusternode sections. A clustern‐
49 ode has two required attributes:
50
51 name The node name should correspond to the hostname on the network
52 interface to be used for cluster communication.
53
54 nodeid The node id must be greater than zero and unique.
55
56 <cluster name="alpha" config_version="1">
57 <clusternodes>
58 <clusternode name="node-01" nodeid="1">
59 </clusternode>
60
61 <clusternode name="node-02" nodeid="2">
62 </clusternode>
63
64 <clusternode name="node-03" nodeid="3">
65 </clusternode>
66 </clusternodes>
67 </cluster>
68
69
70 Logging
71 Cluster daemons use a common logging section to configure their
72 loggging behavior.
73
74 <cluster name="alpha" config_version="1">
75 <logging/>
76 </cluster>
77
78 Global settings apply to all:
79
80 <logging debug="on"/>
81
82 Per-daemon logging_daemon subsections override the global settings.
83 Daemon names that can be configured include: corosync, qdiskd, groupd,
84 fenced, dlm_controld, gfs_controld, rgmanager.
85
86 <logging>
87 <logging_daemon name="qdiskd" debug="on"/>
88 <logging_daemon name="fenced" debug="on"/>
89 </logging>
90
91 Corosync daemon settings apply to all corosync subsystems by default,
92 but subsystems can also be configured individually. These include CLM,
93 CPG, MAIN, SERV, CMAN, TOTEM, QUORUM, CONFDB, CKPT, EVT.
94
95 <logging>
96 <logging_daemon name="corosync" subsys="QUORUM" debug="on"/>
97 <logging_daemon name="corosync" subsys="CONFDB" debug="on"/>
98 </logging>
99
100 The attributes available at global, daemon and subsystem levels are:
101
102
103 to_syslog
104 enable/disable messages to syslog (yes/no), default "yes"
105
106
107 to_logfile
108 enable/disable messages to log file (yes/no), default "yes"
109
110
111 syslog_facility
112 facility used for syslog messages, default "daemon"
113
114
115 syslog_priority
116 messages at this level and up will be sent to syslog, default
117 "info"
118
119
120 logfile_priority
121 messages at this level and up will be written to log file,
122 default "info"
123
124
125 logfile
126 the log file name, default /var/log/cluster/<daemon>.log
127
128
129 debug="on"
130 a shortcut for logfile_priority="debug"
131
132
134 An explicit configuration for the default settings would be:
135
136 <logging to_syslog="yes" to_logfile="yes" syslog_facility="daemon"
137 syslog_priority="info" logfile_priority="info">
138 <logging_daemon name="qdiskd"
139 logfile="/var/log/cluster/qdiskd.log"/>
140 <logging_daemon name="fenced"
141 logfile="/var/log/cluster/fenced.log"/>
142 <logging_daemon name="dlm_controld"
143 logfile="/var/log/cluster/dlm_controld.log"/>
144 <logging_daemon name="gfs_controld"
145 logfile="/var/log/cluster/gfs_controld.log"/>
146 <logging_daemon name="rgmanager"
147 logfile="/var/log/cluster/rgmanager.log"/>
148 <logging_daemon name="corosync"
149 logfile="/var/log/cluster/corosync.log"/>
150 </logging>
151
152 To include debug messages (and above) from all daemons in their default
153 log files, either of the following which are equivalent:
154
155 <logging debug="on"/>
156 <logging logfile_priority="debug"/>
157
158 To exclude all log messages from syslog:
159
160 <logging to_syslog="no"/>
161
162 To disable logging to all log files:
163
164 <logging to_file="no"/>
165
166 To include debug messages (and above) from all daemons in syslog:
167
168 <logging syslog_priority="debug"/>
169
170 To limit syslog messages to error (and above), keeping info (and above)
171 in log files (this logfile_priority setting is the default so could be
172 omitted):
173
174 <logging syslog_priority="error" logfile_priority="info"/>
175
177 /etc/cluster/cluster.conf
178 standard location of cluster configuration file
179
180 /usr/share/cluster/cluster.rng
181 standard location of cluster.conf schema
182
183
185 ccs_tool(8), ccs_config_dump(8), ccs_config_validate(8), cman_tool(8),
186 cman(5), qdisk(5), fenced(8), fence_node(8), dlm_controld(8), gfs_con‐
187 trold(8), rgmanager(8)
188
189
190
191
192cluster 2010-01-12 CLUSTER.CONF(5)