1 <?xml version="1.0" encoding="iso-8859-1"?>
3 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
4 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
6 <refentry id="ctdbd.1">
9 <refentrytitle>ctdbd</refentrytitle>
10 <manvolnum>1</manvolnum>
11 <refmiscinfo class="source">ctdb</refmiscinfo>
12 <refmiscinfo class="manual">CTDB - clustered TDB database</refmiscinfo>
16 <refname>ctdbd</refname>
17 <refpurpose>The CTDB cluster daemon</refpurpose>
22 <command>ctdbd</command>
23 <arg rep="repeat"><replaceable>OPTION</replaceable></arg>
28 <title>DESCRIPTION</title>
30 ctdbd is the main CTDB daemon.
34 Note that ctdbd is not usually invoked directly. It is invoked
35 via <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
36 <manvolnum>1</manvolnum></citerefentry> or via the initscript.
40 See <citerefentry><refentrytitle>ctdb</refentrytitle>
41 <manvolnum>7</manvolnum></citerefentry> for an overview of CTDB.
46 <title>GENERAL OPTIONS</title>
50 <term>-d, --debug=<parameter>DEBUGLEVEL</parameter></term>
53 This option sets the debug level to DEBUGLEVEL, which
54 controls what will be written by the logging
55 subsystem. The default is 0 which will only log important
56 events and errors. A larger number will provide additional
60 See the <citetitle>DEBUG LEVELS</citetitle> section in
61 <citerefentry><refentrytitle>ctdb</refentrytitle>
62 <manvolnum>7</manvolnum></citerefentry> for more
69 <term>--dbdir=<parameter>DIRECTORY</parameter></term>
72 DIRECTORY on local storage where ctdbd keeps a local copy of
73 TDB databases. This directory is local for each node and
74 should not be stored on the shared cluster filesystem.
77 This directory would usually be <filename>/var/lib/ctdb</filename>
83 <term>--dbdir-persistent=<parameter>DIRECTORY</parameter></term>
86 DIRECTORY on local storage where ctdbd keeps a local copy of
87 persistent TDB databases. This directory is local for each
88 node and should not be stored on the shared cluster
92 This directory would usually be
93 <filename>/var/lib/ctdb/persistent</filename>
99 <term>--dbdir-state=<parameter>DIRECTORY</parameter></term>
102 DIRECTORY on local storage where ctdbd keep internal state
103 TDB files. This directory is local for each node and
104 should not be stored on the shared cluster filesystem.
107 This directory would usually be
108 <filename>/var/lib/ctdb/state</filename>
114 <term>--event-script-dir=<parameter>DIRECTORY</parameter></term>
117 DIRECTORY where the CTDB event scripts are stored. See the
118 <citetitle>EVENT SCRIPTS</citetitle> section in
119 <citerefentry><refentrytitle>ctdb</refentrytitle>
120 <manvolnum>7</manvolnum></citerefentry> for more information.
123 Default is <envar>CTDB_BASE</envar>/events.d, so usually
124 <filename>/etc/ctdb/events.d</filename>, which is part of
125 the CTDB installation.
131 <term>--logging=<parameter>STRING</parameter></term>
134 STRING specifies where ctdbd will write its log. The
135 default is file:<filename>/var/log/log.ctdb</filename> or
136 similar - the prefix may differ depending on how CTDB was
144 <term>file:<parameter>FILENAME</parameter></term>
147 FILENAME where ctdbd will write its log. This is usually
148 <filename>/var/log/log.ctdb</filename>.
153 <term>syslog<optional>:<parameter>METHOD</parameter></optional></term>
156 CTDB will log to syslog. By default this will use
160 Under heavy loads syslog(3) can block if the syslog
161 daemon processes messages too slowly. This can
162 cause CTDB to block when logging.
165 If METHOD is specified then it specifies an
166 extension that causes logging to be done in a
167 non-blocking mode. Note that <emphasis>this may
168 cause messages to be dropped</emphasis>. METHOD
173 <term>nonblocking</term>
176 CTDB will log to syslog via
177 <filename>/dev/log</filename> in non-blocking
186 CTDB will log to syslog via UDP to
187 localhost:514. The syslog daemon must be
188 configured to listen on (at least)
189 localhost:514. Most syslog daemons will log
190 the messages with hostname "localhost" - this
191 is a limitation of the implementation, for
192 compatibility with more syslog daemons.
207 This option is used to activate the LVS capability on a CTDB
208 node. Please see the <citetitle>LVS</citetitle> section in
209 <citerefentry><refentrytitle>ctdb</refentrytitle>
210 <manvolnum>7</manvolnum></citerefentry> for more
217 <term>--max-persistent-check-errors=<parameter>NUM</parameter></term>
220 NUM specifies the maximum number of health check failures
221 allowed for persistent databases during startup.
224 The default value is 0. Setting this to non-zero allows a
225 node with unhealthy persistent databases to startup and
226 join the cluster as long as there is another node with
227 healthy persistent databases.
233 <term>--nlist=<parameter>FILENAME</parameter></term>
236 FILENAME containing a list of the private IP addresses, one
237 per line, for each node in the cluster. This file
238 <emphasis>must be the same on each node</emphasis> in the
242 Default is <envar>CTDB_BASE</envar>/nodes, so usually
243 <filename>/etc/ctdb/nodes</filename>.
249 <term>--no-lmaster</term>
252 This argument specifies that this node can NOT become an lmaster
253 for records in the database. This means that it will never show up
254 in the vnnmap. This feature is primarily used for making a cluster
255 span across a WAN link and use CTDB as a WAN-accelerator.
258 Please see the <citetitle>REMOTE CLUSTER NODES</citetitle>
259 section in <citerefentry><refentrytitle>ctdb</refentrytitle>
260 <manvolnum>7</manvolnum></citerefentry> for more
267 <term>--no-recmaster</term>
270 This argument specifies that this node can NOT become a recmaster
271 for the database. This feature is primarily used for making a cluster
272 span across a WAN link and use CTDB as a WAN-accelerator.
275 Please see the <citetitle>REMOTE CLUSTER NODES</citetitle>
276 section in <citerefentry><refentrytitle>ctdb</refentrytitle>
277 <manvolnum>7</manvolnum></citerefentry> for more
284 <term>--notification-script=<parameter>FILENAME</parameter></term>
287 FILENAME specifying a script to be invoked by ctdbd when
288 certain state changes occur.
292 <filename>/etc/ctdb/notify.sh</filename>.
295 Please see the <citetitle>NOTIFICATION SCRIPT</citetitle>
296 section in <citerefentry><refentrytitle>ctdb</refentrytitle>
297 <manvolnum>7</manvolnum></citerefentry> for more
304 <term>--pidfile=<parameter>FILENAME</parameter></term>
307 FILENAME for file containing process ID of main CTDB
308 daemon. This file is automatically created and removed by
312 The default is to not create a PID file.
318 <term>--public_addresses=<parameter>FILENAME</parameter></term>
321 FILENAME specifying a file containing the public IP
322 addresses to use on the cluster when CTDB should use IP
323 takeover. This file contains a list of IP addresses,
324 netmasks and interfaces. CTDB will distribute these public
325 IP addresses appropriately across the available nodes.
328 The IP addresses specified in this file can differ across
332 This is usually the file
333 <filename>/etc/ctdb/public_addresses</filename>
339 <term>--public-interface=<parameter>INTERFACE</parameter></term>
342 INTERFACE on which to attach public IP addresses or on which
343 to attach the single-public-ip when used.
346 When using public IP addresses, this is only required if
347 interfaces are not explicitly specified in the public
354 <term>--reclock=<parameter>FILENAME</parameter></term>
357 FILENAME is the name of the recovery lock file stored in
358 <emphasis>shared storage</emphasis> that ctdbd uses to
359 prevent split brains from occuring.
362 It is possible to run CTDB without a recovery lock file, but
363 then there will be no protection against split brain if the
364 cluster/network becomes partitioned. Using CTDB without a
365 reclock file is strongly discouraged.
371 <term>--single-public-ip=<parameter>IPADDR</parameter></term>
374 IPADDR specifies the single IP that CTDB will use in
378 Please see the <citetitle>LVS</citetitle> section in
379 <citerefentry><refentrytitle>ctdb</refentrytitle>
380 <manvolnum>7</manvolnum></citerefentry> for more
387 <term>--start-as-disabled</term>
390 This makes ctdbd start in the DISABLED state.
393 To allow the node to host public IP addresses and
394 services, it must be manually enabled using the
395 <command>ctdb enable</command> command.
398 Please see the <citetitle>NODE STATES</citetitle> section
399 in <citerefentry><refentrytitle>ctdb</refentrytitle>
400 <manvolnum>7</manvolnum></citerefentry> for more
401 information about the DISABLED state.
407 <term>--start-as-stopped</term>
410 This makes ctdbd start in the STOPPED state.
413 To allow the node to take part in the cluster it must be
414 manually continued with the the <command>ctdb
415 enable</command> command.
418 Please see the <citetitle>NODE STATES</citetitle> section
419 in <citerefentry><refentrytitle>ctdb</refentrytitle>
420 <manvolnum>7</manvolnum></citerefentry> for more
421 information about the STOPPED state.
427 <term>--syslog</term>
430 Send log messages to syslog instead of the CTDB logfile.
431 This option overrides --logfile. The default is to log to
438 <term>--transport=tcp|infiniband</term>
441 This option specifies which transport to use for ctdbd
442 internode communications. The default is "tcp".
445 The "infiniband" support is not regularly tested.
451 <term>-?, --help</term>
454 Display a summary of options.
463 <title>DEBUGGING OPTIONS</title>
468 <term>-i, --interactive</term>
471 Enable interactive mode. This will make ctdbd run in the
472 foreground and not detach from the terminal. By default
473 ctdbd will detach itself and run in the background as a
480 <term>--listen=<parameter>IPADDR</parameter></term>
483 This specifies which IP address that ctdbd will bind to.
486 By default ctdbd will bind to the first address it finds in
487 the <filename>/etc/ctdb/nodes</filename> file that is also
488 present on the local system.
491 This option is only required when you want to run multiple
492 ctdbd daemons/nodes on the same physical host in which case
493 there would be multiple entries in
494 <filename>/etc/ctdb/nodes</filename> that would match a
501 <term>--nopublicipcheck</term>
504 This option is used when testing with multiple local
505 daemons on a single machine. It disables checks related
506 to public IP addresses.
512 <term>--nosetsched</term>
515 This is a debugging option. This option is only used when
519 Normally ctdbd will change its scheduler to run as a
520 real-time process. This is the default mode for a normal
521 ctdbd operation to gurarantee that ctdbd always gets the CPU
522 cycles that it needs.
525 This option is used to tell ctdbd to
526 <emphasis>not</emphasis> run as a real-time process and
527 instead run ctdbd as a normal userspace process. This is
528 useful for debugging and when you want to run ctdbd under
529 valgrind or gdb. (You don't want to attach valgrind or gdb
530 to a real-time process.)
536 <term>--socket=<parameter>FILENAME</parameter></term>
539 FILENAME specifies the name of the Unix domain socket that
540 ctdbd will create. This socket is used by local clients to
541 communicate with ctdbd.
544 The default is <filename>/tmp/ctdb.socket</filename> . You
545 only need to use this option if you plan to run multiple
546 ctdbd daemons on the same physical host, usually for
553 <term>--script-log-level=<parameter>DEBUGLEVEL</parameter></term>
556 This option sets the debug level of event script output to
557 DEBUGLEVEL. The default is ERR (0).
560 See the <citetitle>DEBUG LEVELS</citetitle> section in
561 <citerefentry><refentrytitle>ctdb</refentrytitle>
562 <manvolnum>7</manvolnum></citerefentry> for more
569 <term>--sloppy-start</term>
572 This is debugging option. This speeds up the initial
573 recovery during startup at the expense of some consistency
574 checking. <emphasis>Don't use this option in
575 production</emphasis>.
581 <term>--torture</term>
584 This option is only used for development and testing of
585 CTDB. It adds artificial errors and failures to the
586 common codepaths in ctdbd to verify that ctdbd can recover
587 correctly from failures.
590 <emphasis>Do not use this option</emphasis> unless you are
591 developing and testing new functionality in CTDB.
597 <term>--valgrinding</term>
600 This is a debugging option. This option is only used when
601 debugging ctdbd. This enables additional debugging
602 capabilities and implies --nosetsched.
611 <title>SEE ALSO</title>
613 <citerefentry><refentrytitle>ctdb</refentrytitle>
614 <manvolnum>1</manvolnum></citerefentry>,
616 <citerefentry><refentrytitle>ctdbd_wrapper</refentrytitle>
617 <manvolnum>1</manvolnum></citerefentry>,
619 <citerefentry><refentrytitle>onnode</refentrytitle>
620 <manvolnum>1</manvolnum></citerefentry>,
622 <citerefentry><refentrytitle>ctdb</refentrytitle>
623 <manvolnum>7</manvolnum></citerefentry>,
625 <citerefentry><refentrytitle>ctdb-tunables</refentrytitle>
626 <manvolnum>7</manvolnum></citerefentry>,
628 <ulink url="http://ctdb.samba.org/"/>
635 This documentation was written by
644 <holder>Andrew Tridgell</holder>
645 <holder>Ronnie Sahlberg</holder>
649 This program is free software; you can redistribute it and/or
650 modify it under the terms of the GNU General Public License as
651 published by the Free Software Foundation; either version 3 of
652 the License, or (at your option) any later version.
655 This program is distributed in the hope that it will be
656 useful, but WITHOUT ANY WARRANTY; without even the implied
657 warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR
658 PURPOSE. See the GNU General Public License for more details.
661 You should have received a copy of the GNU General Public
662 License along with this program; if not, see
663 <ulink url="http://www.gnu.org/licenses"/>.