1CTDBD(1) CTDB - clustered TDB database CTDBD(1)
2
6 ctdbd - The CTDB cluster daemon
7
9 ctdbd [OPTION...]
10
12 ctdbd is the main CTDB daemon.
13 Note that ctdbd is not usually invoked directly. It is invoked via
15 ctdbd_wrapper(1) or via the initscript.
16 See ctdb(7) for an overview of CTDB.
18
20 -d, --debug=DEBUGLEVEL
21 This option sets the debug level to DEBUGLEVEL, which controls what
22 will be written to the logfile. The default is 0 which will only
23 log important events and errors. A larger number will provide
24 additional logging.
25 See the DEBUG LEVELS section in ctdb(7) for more information.
27 --dbdir=DIRECTORY
29 DIRECTORY on local storage where ctdbd keeps a local copy of TDB
30 databases. This directory is local for each node and should not be
31 stored on the shared cluster filesystem.
32 This directory would usually be /var/ctdb
34 --dbdir-persistent=DIRECTORY
36 DIRECTORY on local storage where ctdbd keeps a local copy of
37 persistent TDB databases. This directory is local for each node and
38 should not be stored on the shared cluster filesystem.
39 This directory would usually be /etc/ctdb/persistent
41 --dbdir-state=DIRECTORY
43 DIRECTORY on local storage where ctdbd keep internal state TDB
44 files. This directory is local for each node and should not be
45 stored on the shared cluster filesystem.
46 This directory would usually be /var/ctdb/state
48 --event-script-dir=DIRECTORY
50 DIRECTORY where the CTDB event scripts are stored. See the EVENT
51 SCRIPTS section in ctdb(7) for more information.
52 Default is CTDB_BASE/events.d, so usually /etc/ctdb/events.d, which
54 is part of the CTDB installation.
55 --logfile=FILENAME
57 FILENAME where ctdbd will write its log. This is usually
58 /var/log/log.ctdb.
59 --log-ringbuf-size=NUM
61 Set the size of the log ringbuffer to NUM entries.
62 CTDB uses an in-memory ringbuffer containing NUM most recent log
64 entries for all log levels (except DEBUG). The ringbugger can be
65 useful for extracting detailed logs even if some entries are not
66 logged to the regular logs.
67 Use the ctdb getlog command to retrieve log entries from the
69 ringbuffer.
70 --lvs
72 This option is used to activate the LVS capability on a CTDB node.
73 Please see the LVS section in ctdb(7) for more information.
74 --max-persistent-check-errors=NUM
76 NUM specifies the maximum number of health check failures allowed
77 for persistent databases during startup.
78 The default value is 0. Setting this to non-zero allows a node with
80 unhealthy persistent databases to startup and join the cluster as
81 long as there is another node with healthy persistent databases.
82 --nlist=FILENAME
84 FILENAME containing a list of the private IP addresses, one per
85 line, for each node in the cluster. This file must be the same on
86 each node in the cluster.
87 Default is CTDB_BASE/nodes, so usually /etc/ctdb/nodes.
89 --no-lmaster
91 This argument specifies that this node can NOT become an lmaster
92 for records in the database. This means that it will never show up
93 in the vnnmap. This feature is primarily used for making a cluster
94 span across a WAN link and use CTDB as a WAN-accelerator.
95 Please see the REMOTE CLUSTER NODES section in ctdb(7) for more
97 information.
98 --no-recmaster
100 This argument specifies that this node can NOT become a recmaster
101 for the database. This feature is primarily used for making a
102 cluster span across a WAN link and use CTDB as a WAN-accelerator.
103 Please see the REMOTE CLUSTER NODES section in ctdb(7) for more
105 information.
106 --notification-script=FILENAME
108 FILENAME specifying a script to be invoked by ctdbd when certain
109 state changes occur.
110 This file is usually /etc/ctdb/notify.sh.
112 Please see the NOTIFICATION SCRIPT section in ctdb(7) for more
114 information.
115 --pidfile=FILENAME
117 FILENAME for file containing process ID of main CTDB daemon. This
118 file is automatically created and removed by CTDB.
119 The default is to not create a PID file.
121 --public_addresses=FILENAME
123 FILENAME specifying a file containing the public IP addresses to
124 use on the cluster when CTDB should use IP takeover. This file
125 contains a list of IP addresses, netmasks and interfaces. CTDB will
126 distribute these public IP addresses appropriately across the
127 available nodes.
128 The IP addresses specified in this file can differ across nodes.
130 This is usually the file /etc/ctdb/public_addresses
132 --public-interface=INTERFACE
134 INTERFACE on which to attach public IP addresses or on which to
135 attach the single-public-ip when used.
136 When using public IP addresses, this is only required if interfaces
138 are not explicitly specified in the public addresses file.
139 --reclock=FILENAME
141 FILENAME is the name of the recovery lock file stored in shared
142 storage that ctdbd uses to prevent split brains from occuring.
143 It is possible to run CTDB without a recovery lock file, but then
145 there will be no protection against split brain if the
146 cluster/network becomes partitioned. Using CTDB without a reclock
147 file is strongly discouraged.
148 --single-public-ip=IPADDR
150 IPADDR specifies the single IP that CTDB will use in conjuction
151 with LVS.
152 Please see the LVS section in ctdb(7) for more information.
154 --start-as-disabled
156 This makes ctdbd start in the DISABLED state.
157 To allow the node to host public IP addresses and services, it must
159 be manually enabled using the ctdb enable command.
160 Please see the NODE STATES section in ctdb(7) for more information
162 about the DISABLED state.
163 --start-as-stopped
165 This makes ctdbd start in the STOPPED state.
166 To allow the node to take part in the cluster it must be manually
168 continued with the the ctdb enable command.
169 Please see the NODE STATES section in ctdb(7) for more information
171 about the STOPPED state.
172 --syslog
174 Send log messages to syslog instead of the CTDB logfile. This
175 option overrides --logfile. The default is to log to a file.
176 --transport=tcp|infiniband
178 This option specifies which transport to use for ctdbd internode
179 communications. The default is "tcp".
180 The "infiniband" support is not regularly tested.
182 -?, --help
184 Display a summary of options.
185
187 -i, --interactive
188 Enable interactive mode. This will make ctdbd run in the foreground
189 and not detach from the terminal. By default ctdbd will detach
190 itself and run in the background as a daemon.
191 --listen=IPADDR
193 This specifies which IP address that ctdbd will bind to.
194 By default ctdbd will bind to the first address it finds in the
196 /etc/ctdb/nodes file that is also present on the local system.
197 This option is only required when you want to run multiple ctdbd
199 daemons/nodes on the same physical host in which case there would
200 be multiple entries in /etc/ctdb/nodes that would match a local
201 interface.
202 --nopublicipcheck
204 This option is used when testing with multiple local daemons on a
205 single machine. It disables checks related to public IP addresses.
206 --nosetsched
208 This is a debugging option. This option is only used when debugging
209 ctdbd.
210 Normally ctdbd will change its scheduler to run as a real-time
212 process. This is the default mode for a normal ctdbd operation to
213 gurarantee that ctdbd always gets the CPU cycles that it needs.
214 This option is used to tell ctdbd to not run as a real-time process
216 and instead run ctdbd as a normal userspace process. This is useful
217 for debugging and when you want to run ctdbd under valgrind or gdb.
218 (You don't want to attach valgrind or gdb to a real-time process.)
219 --socket=FILENAME
221 FILENAME specifies the name of the Unix domain socket that ctdbd
222 will create. This socket is used by local clients to communicate
223 with ctdbd.
224 The default is /tmp/ctdb.socket . You only need to use this option
226 if you plan to run multiple ctdbd daemons on the same physical
227 host, usually for testing.
228 --script-log-level=DEBUGLEVEL
230 This option sets the debug level of event script output to
231 DEBUGLEVEL. The default is ERR (0).
232 See the DEBUG LEVELS section in ctdb(7) for more information.
234 --sloppy-start
236 This is debugging option. This speeds up the initial recovery
237 during startup at the expense of some consistency checking. Don't
238 use this option in production.
239 --torture
241 This option is only used for development and testing of CTDB. It
242 adds artificial errors and failures to the common codepaths in
243 ctdbd to verify that ctdbd can recover correctly from failures.
244 Do not use this option unless you are developing and testing new
246 functionality in CTDB.
247 --valgrinding
249 This is a debugging option. This option is only used when debugging
250 ctdbd. This enables additional debugging capabilities and implies
251 --nosetsched.
252
254 ctdb(1), ctdbd_wrapper(1), onnode(1), ctdb(7), ctdb-tunables(7),
255 http://ctdb.samba.org/
256
258 This documentation was written by Ronnie Sahlberg, Amitay Isaacs,
259 Martin Schwenke
260
262 Copyright © 2007 Andrew Tridgell, Ronnie Sahlberg
263 This program is free software; you can redistribute it and/or modify it
265 under the terms of the GNU General Public License as published by the
266 Free Software Foundation; either version 3 of the License, or (at your
267 option) any later version.
268 This program is distributed in the hope that it will be useful, but
270 WITHOUT ANY WARRANTY; without even the implied warranty of
271 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
272 General Public License for more details.
273 You should have received a copy of the GNU General Public License along
275 with this program; if not, see http://www.gnu.org/licenses.
276ctdb 11/27/2013 CTDBD(1)