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 by the logging subsystem. The default is 2.
23 See the DEBUG LEVELS section in ctdb(7) for more information.
25 --dbdir=DIRECTORY
27 DIRECTORY on local storage where ctdbd keeps a local copy of TDB
28 databases. This directory is local for each node and should not be
29 stored on the shared cluster filesystem.
30 Defaults to /var/lib/ctdb.
32 --dbdir-persistent=DIRECTORY
34 DIRECTORY on local storage where ctdbd keeps a local copy of
35 persistent TDB databases. This directory is local for each node and
36 should not be stored on the shared cluster filesystem.
37 Defaults to /var/lib/ctdb/persistent.
39 --dbdir-state=DIRECTORY
41 DIRECTORY on local storage where ctdbd keep internal state TDB
42 files. This directory is local for each node and should not be
43 stored on the shared cluster filesystem.
44 Defaults to /var/lib/ctdb/state.
46 --event-script-dir=DIRECTORY
48 DIRECTORY where the CTDB event scripts are stored. See the EVENT
49 SCRIPTS section in ctdb(7) for more information.
50 Default is CTDB_BASE/events.d, so usually /etc/ctdb/events.d, which
52 is part of the CTDB installation.
53 --listen=IPADDR
55 IPADDR is the private IP address that ctdbd will bind to.
56 By default ctdbd will select the first address from the nodes list
58 that in can bind to. See also --nlist.
59 This option is only required when automatic address detection can
61 not be used. This can be the case when running multiple ctdbd
62 daemons/nodes on the same physical host (usually for testing),
63 using InfiniBand for the private network or on Linux when sysctl
64 net.ipv4.ip_nonlocal_bind=1.
65 --logging=STRING
67 STRING specifies where ctdbd will write its log. The default is
68 file:/var/log/log.ctdb.
69 Valid values are:
71 file:FILENAME
73 FILENAME where ctdbd will write its log. This is usually
74 /var/log/log.ctdb.
75 syslog[:METHOD]
77 CTDB will log to syslog. By default this will use the syslog(3)
78 API.
79 Under heavy loads syslog(3) can block if the syslog daemon
81 processes messages too slowly. This can cause CTDB to block
82 when logging.
83 If METHOD is specified then it specifies an extension that
85 causes logging to be done in a non-blocking mode. Note that
86 this may cause messages to be dropped. METHOD must be one of:
87 nonblocking
89 CTDB will log to syslog via /dev/log in non-blocking mode.
90 udp
92 CTDB will log to syslog via UDP to localhost:514. The
93 syslog daemon must be configured to listen on (at least)
94 localhost:514. Most syslog daemons will log the messages
95 with hostname "localhost" - this is a limitation of the
96 implementation, for compatibility with more syslog daemons.
97 udp-rfc5424
99 As with "udp" but messages are sent in RFC5424 format. This
100 method will log the correct hostname but is not as widely
101 implemented in syslog daemons.
102 --max-persistent-check-errors=NUM
104 NUM specifies the maximum number of health check failures allowed
105 for persistent databases during startup.
106 The default value is 0. Setting this to non-zero allows a node with
108 unhealthy persistent databases to startup and join the cluster as
109 long as there is another node with healthy persistent databases.
110 --nlist=FILENAME
112 FILENAME containing a list of the private IP addresses, one per
113 line, for each node in the cluster. This file must be the same on
114 each node in the cluster.
115 Default is CTDB_BASE/nodes, so usually /etc/ctdb/nodes.
117 --no-lmaster
119 This argument specifies that this node can NOT become an lmaster
120 for records in the database. This means that it will never show up
121 in the vnnmap. This feature is primarily used for making a cluster
122 span across a WAN link and use CTDB as a WAN-accelerator.
123 Please see the REMOTE CLUSTER NODES section in ctdb(7) for more
125 information.
126 --no-recmaster
128 This argument specifies that this node can NOT become a recmaster
129 for the database. This feature is primarily used for making a
130 cluster span across a WAN link and use CTDB as a WAN-accelerator.
131 Please see the REMOTE CLUSTER NODES section in ctdb(7) for more
133 information.
134 --notification-script=FILENAME
136 FILENAME specifying a script to be invoked by ctdbd when certain
137 state changes occur.
138 This file is usually /etc/ctdb/notify.sh.
140 Please see the NOTIFICATION SCRIPT section in ctdb(7) for more
142 information.
143 --pidfile=FILENAME
145 FILENAME for file containing process ID of main CTDB daemon. This
146 file is automatically created and removed by CTDB.
147 The default is to not create a PID file.
149 --public_addresses=FILENAME
151 FILENAME specifying a file containing the public IP addresses to
152 use on the cluster when CTDB should use IP takeover. This file
153 contains a list of IP addresses, netmasks and interfaces. CTDB will
154 distribute these public IP addresses appropriately across the
155 available nodes.
156 The IP addresses specified in this file can differ across nodes.
158 This is usually the file /etc/ctdb/public_addresses
160 --public-interface=INTERFACE
162 Default INTERFACE on which to attach public IP addresses.
163 When using public IP addresses, this is only required if interfaces
165 are not explicitly specified in the public addresses file.
166 --reclock=LOCK
168 LOCK specifies the cluster-wide mutex used to detect and prevent a
169 partitioned cluster (or "split brain").
170 For information about the recovery lock please see the RECOVERY
172 LOCK section in ctdb(7).
173 --start-as-disabled
175 This makes ctdbd start in the DISABLED state.
176 To allow the node to host public IP addresses and services, it must
178 be manually enabled using the ctdb enable command.
179 Please see the NODE STATES section in ctdb(7) for more information
181 about the DISABLED state.
182 --start-as-stopped
184 This makes ctdbd start in the STOPPED state.
185 To allow the node to take part in the cluster it must be manually
187 continued with the the ctdb enable command.
188 Please see the NODE STATES section in ctdb(7) for more information
190 about the STOPPED state.
191 --transport=tcp|infiniband
193 This option specifies which transport to use for ctdbd internode
194 communications. The default is "tcp".
195 The "infiniband" support is not regularly tested.
197 -?, --help
199 Display a summary of options.
200
202 -i, --interactive
203 Enable interactive mode. This will make ctdbd run in the foreground
204 and not detach from the terminal. By default ctdbd will detach
205 itself and run in the background as a daemon.
206 --nopublicipcheck
208 This option is used when testing with multiple local daemons on a
209 single machine. It disables checks related to public IP addresses.
210 --nosetsched
212 This is a debugging option. This option is only used when debugging
213 ctdbd.
214 Normally ctdbd will change its scheduler to run as a real-time
216 process. This is the default mode for a normal ctdbd operation to
217 gurarantee that ctdbd always gets the CPU cycles that it needs.
218 This option is used to tell ctdbd to not run as a real-time process
220 and instead run ctdbd as a normal userspace process. This is useful
221 for debugging and when you want to run ctdbd under valgrind or gdb.
222 (You don't want to attach valgrind or gdb to a real-time process.)
223 --socket=FILENAME
225 FILENAME specifies the name of the Unix domain socket that ctdbd
226 will create. This socket is used by local clients to communicate
227 with ctdbd.
228 The default is /var/run/ctdb/ctdbd.socket. You only need to use
230 this option if you plan to run multiple ctdbd daemons on the same
231 physical host, usually for testing.
232 --script-log-level=DEBUGLEVEL
234 This option sets the debug level of event script output to
235 DEBUGLEVEL. The default is ERR.
236 See the DEBUG LEVELS section in ctdb(7) for more information.
238 --sloppy-start
240 This is debugging option. This speeds up the initial recovery
241 during startup at the expense of some consistency checking. Don't
242 use this option in production.
243 --torture
245 This option is only used for development and testing of CTDB. It
246 adds artificial errors and failures to the common codepaths in
247 ctdbd to verify that ctdbd can recover correctly from failures.
248 Do not use this option unless you are developing and testing new
250 functionality in CTDB.
251 --valgrinding
253 This is a debugging option. This option is only used when debugging
254 ctdbd. This enables additional debugging capabilities and implies
255 --nosetsched.
256
258 ctdb(1), ctdbd_wrapper(1), onnode(1), ctdb(7), ctdb-tunables(7),
259 http://ctdb.samba.org/
260
262 This documentation was written by Ronnie Sahlberg, Amitay Isaacs,
263 Martin Schwenke
264
266 Copyright © 2007 Andrew Tridgell, Ronnie Sahlberg
267 This program is free software; you can redistribute it and/or modify it
269 under the terms of the GNU General Public License as published by the
270 Free Software Foundation; either version 3 of the License, or (at your
271 option) any later version.
272 This program is distributed in the hope that it will be useful, but
274 WITHOUT ANY WARRANTY; without even the implied warranty of
275 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
276 General Public License for more details.
277 You should have received a copy of the GNU General Public License along
279 with this program; if not, see http://www.gnu.org/licenses.
280ctdb 10/30/2018 CTDBD(1)