1CTDBD.CONF(5) CTDB - clustered TDB database CTDBD.CONF(5)
2
6 ctdbd.conf - CTDB daemon configuration file
7
9 This file contains CTDB configuration variables that are affect the
10 operation of CTDB. The default location of this file is
11 /etc/ctdb/ctdbd.conf.
12 This file is a shell script (see sh(1)) but is usually limited to
14 simple variable assignments and shell-style comments.
15 CTDB configuration variables are grouped into several categories below.
17 Variables defined in this document can also be set in a
19 distribution-specific configuration file such as /etc/sysconfig/ctdb
20 (Red Hat) or /etc/default/ctdb (Debian). However, these files should be
21 reserved for variables used by the initscript. A historical alternative
22 is /etc/ctdb/sysconfig/ctdb - this is deprecated.
23
25 Some options must be available to the initscript so they need to be set
26 in the distribution-specific initscript configuration, such as
27 /etc/sysconfig/ctdb or /etc/default/ctdb.
28 CTDB_PIDFILE=FILENAME
30 FILENAME is the name of the file used to contain the process ID
31 (PID) of the main CTDB daemon when it is running. This is passed
32 from the initscript to ctdbd_wrapper(1).
33 Default is /var/run/ctdb/ctdbd.pid. Corresponds to --pidfile.
35
37 These options may be used in the initscripts, daemon and scripts.
38 CTDB_BASE=DIRECTORY
40 DIRECTORY containing CTDB scripts and configuration files.
41
43 Variables in this section are processed by ctdbd_wrapper(1) and are
44 converted into command-line arguments to ctdbd(1). Correspondence with
45 ctdbd(1) options is shown for each variable. The the documentation for
46 the relevant options for more details.
47 Many of these variables are also used by event scripts.
49 CTDB_CAPABILITY_LMASTER=yes|no
51 Defaults to yes. Corresponds to --no-lmaster.
52 CTDB_CAPABILITY_RECMASTER=yes|no
54 Defaults to yes. Corresponds to --no-recmaster.
55 CTDB_DBDIR=DIRECTORY
57 Defaults to /var/lib/ctdb.
58 Apart from a DIRECTORY, this can take a special value of the form
60 tmpfs[:OPTIONS]. OPTIONS is a comma-separated list of any
61 permissible options to the tmpfs filesystem. The only pre-specified
62 default is mode=700, which can overridden by specifying mode in
63 OPTIONS. It probably makes sense to specify a maximum size.
64 Corresponds to --dbdir.
66 CTDB_DBDIR_PERSISTENT=DIRECTORY
68 Defaults to /var/lib/ctdb/persistent.
69 Corresponds to --dbdir-persistent.
71 CTDB_DBDIR_STATE=DIRECTORY
73 Defaults to /var/lib/ctdb/state.
74 Corresponds to --dbdir-state.
76 CTDB_DEBUGLEVEL=DEBUGLEVEL
78 Default is NOTICE. Corresponds to -d or --debug.
79 CTDB_EVENT_SCRIPT_DIR=DIRECTORY
81 Default is CTDB_BASE/events.d, so usually /etc/ctdb/events.d.
82 Corresponds to --event-script-dir.
83 CTDB_LOGGING=STRING
85 STRING specifies where ctdbd will write its log. The default is
86 file:/var/log/log.ctdb. Corresponds to --logging.
87 Valid values are:
89 file:FILENAME
91 FILENAME where ctdbd will write its log. This is usually
92 /var/log/log.ctdb.
93 syslog[:METHOD]
95 CTDB will log to syslog. By default this will use the syslog(3)
96 API.
97 If METHOD is specified then it specifies an extension that
99 causes logging to be done in a non-blocking fashion. This can
100 be useful under heavy loads that might cause the syslog daemon
101 to dequeue messages too slowly, which would otherwise cause
102 CTDB to block when logging. METHOD must be one of:
103 nonblocking
105 CTDB will log to syslog via /dev/log in non-blocking mode.
106 udp
108 CTDB will log to syslog via UDP to localhost:514. The
109 syslog daemon must be configured to listen on (at least)
110 localhost:514. Most implementations will log the messages
111 against hostname "localhost" - this is a limit of the
112 implementation for compatibility with more syslog daemon
113 implementations.
114 udp-rfc5424
116 As with "udp" but messages are sent in RFC5424 format. This
117 method will log the correct hostname but is not as widely
118 implemented in syslog daemons.
119 CTDB_NODES=FILENAME
121 Default is CTDB_BASE/nodes, so usually /etc/ctdb/nodes. Corresponds
122 to --nlist.
123 CTDB_NOSETSCHED=yes|no
125 Defaults to no. Corresponds to --nosetsched.
126 Usually CTDB runs with real-time priority. If you are running CTDB
128 on a platform that does not support real-time priority, you can set
129 this.
130 CTDB_NOTIFY_SCRIPT=FILENAME
132 No default, usually /etc/ctdb/notify.sh. Corresponds to
133 --notification-script.
134 CTDB_MAX_PERSISTENT_CHECK_ERRORS=NUM
136 Default 0. Corresponds to --max-persistent-check-errors.
137 CTDB_NODE_ADDRESS=IPADDR
139 IPADDR is the private IP address that ctdbd will bind to.
140 Corresponds to --listen.
141 By default ctdbd will select the first address from the nodes list
143 that in can bind to. See also CTDB_NODES.
144 This option is only required when automatic address detection can
146 not be used. This can be the case when running multiple ctdbd
147 daemons/nodes on the same physical host (usually for testing),
148 using InfiniBand for the private network or on Linux when sysctl
149 net.ipv4.ip_nonlocal_bind=1.
150 CTDB_PUBLIC_ADDRESSES=FILENAME
152 No default, usually /etc/ctdb/public_addresses. Corresponds to
153 --public-addresses.
154 CTDB_PUBLIC_INTERFACE=INTERFACE
156 No default. Corresponds to --public-interface.
157 CTDB_RECOVERY_LOCK=LOCK
159 LOCK specifies the cluster-wide mutex used to detect and prevent a
160 partitioned cluster (or "split brain").
161 No default, but the default configuration file specifies
163 /some/place/on/shared/storage, which should be change to a useful
164 value. Corresponds to --reclock.
165 For information about the recovery lock please see the RECOVERY
167 LOCK section in ctdb(7).
168 CTDB_SCRIPT_LOG_LEVEL=DEBUGLEVEL
170 Defaults to ERR. Corresponds to --script-log-level.
171 CTDB_SOCKET=FILENAME
173 Defaults to /var/run/ctdb/ctdbd.socket. Corresponds to --socket.
174 If you change this then you probably want to set this in root's
176 environment (perhaps in a file in /etc/profile.d) so that you can
177 use the ctdb(1) command in a straightforward manner.
178 CTDB_START_AS_DISABLED=yes|no
180 Default is no. Corresponds to --start-as-disabled.
181 CTDB_START_AS_STOPPED=yes|no
183 Default is no. Corresponds to --start-as-stopped.
184 CTDB_TRANSPORT=tcp|infiniband
186 Defaults to tcp. Corresponds to --transport.
187 While the following variables do not translate into daemon options they
189 are used by ctdbd_wrapper(1) when starting and stopping ctdbd(1).
190 CTDB_SHUTDOWN_TIMEOUT=NUM
192 NUM is the number of seconds to wait for ctdbd(1) to shut down
193 gracefully before giving up and killing it.
194 Defaults is 30.
196 CTDB_STARTUP_TIMEOUT=NUM
198 NUM is the number of seconds to wait for ctdbd(1) complete early
199 initialisation up to a point where it is unlikely to abort. If
200 ctdbd doesn't complete the "setup" event before this timeout then
201 it is killed.
202 Defaults is 10.
204
206 NAT GATEWAY
207 NAT gateway is used to configure fallback routing for nodes when they
208 do not host any public IP addresses. For example, it allows unhealthy
209 nodes to reliably communicate with external infrastructure. One node in
210 a NAT gateway group will be designated as the NAT gateway master node
211 and other (slave) nodes will be configured with fallback routes via the
212 NAT gateway master node. For more information, see the NAT GATEWAY
213 section in ctdb(7).
214 CTDB_NATGW_DEFAULT_GATEWAY=IPADDR
216 IPADDR is an alternate network gateway to use on the NAT gateway
217 master node. If set, a fallback default route is added via this
218 network gateway.
219 No default. Setting this variable is optional - if not set that no
221 route is created on the NAT gateway master node.
222 CTDB_NATGW_NODES=FILENAME
224 FILENAME contains the list of nodes that belong to the same NAT
225 gateway group.
226 File format:
228 IPADDR [slave-only]
230 IPADDR is the private IP address of each node in the NAT gateway
233 group.
234 If "slave-only" is specified then the corresponding node can not be
236 the NAT gateway master node. In this case CTDB_NATGW_PUBLIC_IFACE
237 and CTDB_NATGW_PUBLIC_IP are optional and unused.
238 No default, usually /etc/ctdb/natgw_nodes when enabled.
240 CTDB_NATGW_PRIVATE_NETWORK=IPADDR/MASK
242 IPADDR/MASK is the private sub-network that is internally routed
243 via the NAT gateway master node. This is usually the private
244 network that is used for node addresses.
245 No default.
247 CTDB_NATGW_PUBLIC_IFACE=IFACE
249 IFACE is the network interface on which the CTDB_NATGW_PUBLIC_IP
250 will be configured.
251 No default.
253 CTDB_NATGW_PUBLIC_IP=IPADDR/MASK
255 IPADDR/MASK indicates the IP address that is used for outgoing
256 traffic (originating from CTDB_NATGW_PRIVATE_NETWORK) on the NAT
257 gateway master node. This must not be a configured public IP
258 address.
259 No default.
261 CTDB_NATGW_STATIC_ROUTES=IPADDR/MASK[@GATEWAY] ...
263 Each IPADDR/MASK identifies a network or host to which NATGW should
264 create a fallback route, instead of creating a single default
265 route. This can be used when there is already a default route, via
266 an interface that can not reach required infrastructure, that
267 overrides the NAT gateway default route.
268 If GATEWAY is specified then the corresponding route on the NATGW
270 master node will be via GATEWAY. Such routes are created even if
271 CTDB_NATGW_DEFAULT_GATEWAY is not specified. If GATEWAY is not
272 specified for some networks then routes are only created on the
273 NATGW master node for those networks if CTDB_NATGW_DEFAULT_GATEWAY
274 is specified.
275 This should be used with care to avoid causing traffic to
277 unnecessarily double-hop through the NAT gateway master, even when
278 a node is hosting public IP addresses. Each specified network or
279 host should probably have a corresponding automatically created
280 link route or static route to avoid this.
281 No default.
283 Example
285 CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
286 CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
287 CTDB_NATGW_DEFAULT_GATEWAY=10.0.0.1
288 CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
289 CTDB_NATGW_PUBLIC_IFACE=eth0
290 A variation that ensures that infrastructure (ADS, DNS, ...)
293 directly attached to the public network (10.0.0.0/24) is always
294 reachable would look like this:
295 CTDB_NATGW_NODES=/etc/ctdb/natgw_nodes
297 CTDB_NATGW_PRIVATE_NETWORK=192.168.1.0/24
298 CTDB_NATGW_PUBLIC_IP=10.0.0.227/24
299 CTDB_NATGW_PUBLIC_IFACE=eth0
300 CTDB_NATGW_STATIC_ROUTES=10.0.0.0/24
301 Note that CTDB_NATGW_DEFAULT_GATEWAY is not specified.
304 POLICY ROUTING
306 A node running CTDB may be a component of a complex network topology.
307 In particular, public addresses may be spread across several different
308 networks (or VLANs) and it may not be possible to route packets from
309 these public addresses via the system's default route. Therefore, CTDB
310 has support for policy routing via the 13.per_ip_routing eventscript.
311 This allows routing to be specified for packets sourced from each
312 public address. The routes are added and removed as CTDB moves public
313 addresses between nodes.
314 For more information, see the POLICY ROUTING section in ctdb(7).
316 CTDB_PER_IP_ROUTING_CONF=FILENAME
318 FILENAME contains elements for constructing the desired routes for
319 each source address.
320 The special FILENAME value __auto_link_local__ indicates that no
322 configuration file is provided and that CTDB should generate
323 reasonable link-local routes for each public IP address.
324 File format:
326 IPADDR DEST-IPADDR/MASK [GATEWAY-IPADDR]
328 No default, usually /etc/ctdb/policy_routing when enabled.
331 CTDB_PER_IP_ROUTING_RULE_PREF=NUM
333 NUM sets the priority (or preference) for the routing rules that
334 are added by CTDB.
335 This should be (strictly) greater than 0 and (strictly) less than
337 32766. A priority of 100 is recommended, unless this conflicts with
338 a priority already in use on the system. See ip(8), for more
339 details.
340 CTDB_PER_IP_ROUTING_TABLE_ID_LOW=LOW-NUM,
342 CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=HIGH-NUM
343 CTDB determines a unique routing table number to use for the
344 routing related to each public address. LOW-NUM and HIGH-NUM
345 indicate the minimum and maximum routing table numbers that are
346 used.
347 ip(8) uses some reserved routing table numbers below 255.
349 Therefore, CTDB_PER_IP_ROUTING_TABLE_ID_LOW should be (strictly)
350 greater than 255.
351 CTDB uses the standard file /etc/iproute2/rt_tables to maintain a
353 mapping between the routing table numbers and labels. The label for
354 a public address ADDR will look like ctdb.addr. This means that the
355 associated rules and routes are easy to read (and manipulate).
356 No default, usually 1000 and 9000.
358 Example
360 CTDB_PER_IP_ROUTING_CONF=/etc/ctdb/policy_routing
361 CTDB_PER_IP_ROUTING_RULE_PREF=100
362 CTDB_PER_IP_ROUTING_TABLE_ID_LOW=1000
363 CTDB_PER_IP_ROUTING_TABLE_ID_HIGH=9000
364 LVS
367 For a general description see the LVS section in ctdb(7).
368 Eventscript
370 91.lvs
371 CTDB_LVS_NODES=FILENAME
373 FILENAME contains the list of nodes that belong to the same LVS
374 group.
375 File format:
377 IPADDR [slave-only]
379 IPADDR is the private IP address of each node in the LVS group.
382 If "slave-only" is specified then the corresponding node can not be
384 the LVS master node. In this case CTDB_LVS_PUBLIC_IFACE and
385 CTDB_LVS_PUBLIC_IP are optional and unused.
386 No default, usually /etc/ctdb/lvs_nodes when enabled.
388 CTDB_LVS_PUBLIC_IFACE=INTERFACE
390 INTERFACE is the network interface that clients will use to
391 connection to CTDB_LVS_PUBLIC_IP. This is optional for slave-only
392 nodes. No default.
393 CTDB_LVS_PUBLIC_IP=IPADDR
395 CTDB_LVS_PUBLIC_IP is the LVS public address. No default.
396 MISCELLANEOUS NETWORK CONFIGURATION
398 CTDB_PARTIALLY_ONLINE_INTERFACES=yes|no
399 Whether one or more offline interfaces should cause a monitor event
400 to fail if there are other interfaces that are up. If this is "yes"
401 and a node has some interfaces that are down then ctdb status will
402 display the node as "PARTIALLYONLINE".
403 Note that CTDB_PARTIALLY_ONLINE_INTERFACES=yes is incompatible with
405 NAT gateway, since NAT gateway relies on the interface configured
406 by CTDB_NATGW_PUBLIC_IFACE to be up.
407 Default is "no".
409
411 CTDB can be configured to manage and/or monitor various NAS (and other)
412 services via its eventscripts.
413 In the simplest case CTDB will manage a service. This means the service
415 will be started and stopped along with CTDB, CTDB will monitor the
416 service and CTDB will do any required reconfiguration of the service
417 when public IP addresses are failed over.
418 SAMBA
420 Eventscripts
421 49.winbind
422 50.samba
423 CTDB_MANAGES_SAMBA=yes|no
425 Should CTDB manage Samba?
426 Default is no.
428 CTDB_MANAGES_WINBIND=yes|no
430 Should CTDB manage Winbind?
431 Default is no.
433 CTDB_SAMBA_CHECK_PORTS=PORT-LIST
435 When monitoring Samba, check TCP ports in space-separated
436 PORT-LIST.
437 Default is to monitor ports that Samba is configured to listen on.
439 CTDB_SAMBA_SKIP_SHARE_CHECK=yes|no
441 As part of monitoring, should CTDB skip the check for the existence
442 of each directory configured as share in Samba. This may be
443 desirable if there is a large number of shares.
444 Default is no.
446 CTDB_SERVICE_NMB=SERVICE
448 Distribution specific SERVICE for managing nmbd.
449 Default is distribution-dependant.
451 CTDB_SERVICE_SMB=SERVICE
453 Distribution specific SERVICE for managing smbd.
454 Default is distribution-dependant.
456 CTDB_SERVICE_WINBIND=SERVICE
458 Distribution specific SERVICE for managing winbindd.
459 Default is "winbind".
461 NFS
463 This includes parameters for the kernel NFS server. Alternative NFS
464 subsystems (such as NFS-Ganesha[1]) can be integrated using
465 CTDB_NFS_CALLOUT.
466 Eventscript
468 60.nfs
469 CTDB_MANAGES_NFS=yes|no
471 Should CTDB manage NFS?
472 Default is no.
474 CTDB_NFS_CALLOUT=COMMAND
476 COMMAND specifies the path to a callout to handle interactions with
477 the configured NFS system, including startup, shutdown, monitoring.
478 Default is the included nfs-linux-kernel-callout.
480 CTDB_NFS_CHECKS_DIR=DIRECTORY
482 Specifies the path to a DIRECTORY containing files that describe
483 how to monitor the responsiveness of NFS RPC services. See the
484 README file for this directory for an explanation of the contents
485 of these "check" files.
486 CTDB_NFS_CHECKS_DIR can be used to point to different sets of
488 checks for different NFS servers.
489 One way of using this is to have it point to, say,
491 /etc/ctdb/nfs-checks-enabled.d and populate it with symbolic links
492 to the desired check files. This avoids duplication and is
493 upgrade-safe.
494 Default is /etc/ctdb/nfs-checks.d, which contains NFS RPC checks
496 suitable for Linux kernel NFS.
497 CTDB_NFS_SKIP_SHARE_CHECK=yes|no
499 As part of monitoring, should CTDB skip the check for the existence
500 of each directory exported via NFS. This may be desirable if there
501 is a large number of exports.
502 Default is no.
504 CTDB_RPCINFO_LOCALHOST=IPADDR|HOSTNAME
506 IPADDR or HOSTNAME indicates the address that rpcinfo should
507 connect to when doing rpcinfo check on IPv4 RPC service during
508 monitoring. Optimally this would be "localhost". However, this can
509 add some performance overheads.
510 Default is "127.0.0.1".
512 CTDB_RPCINFO_LOCALHOST6=IPADDR|HOSTNAME
514 IPADDR or HOSTNAME indicates the address that rpcinfo should
515 connect to when doing rpcinfo check on IPv6 RPC service during
516 monitoring. Optimally this would be "localhost6" (or similar).
517 However, this can add some performance overheads.
518 Default is "::1".
520 CTDB_NFS_STATE_FS_TYPE=TYPE
522 The type of filesystem used for a clustered NFS' shared state. No
523 default.
524 CTDB_NFS_STATE_MNT=DIR
526 The directory where a clustered NFS' shared state will be located.
527 No default.
528 APACHE HTTPD
530 CTDB can manage the Apache web server.
531 Eventscript
533 41.httpd
534 CTDB_MANAGES_HTTPD=yes|no
536 Should CTDB manage the Apache web server?
537 Default is no.
539 CLAMAV
541 CTDB has support to manage the popular anti-virus daemon ClamAV.
542 Eventscript
544 31.clamd
545 This eventscript is not enabled by default. Use ctdb enablescript
547 to enable it.
548 CTDB_MANAGES_CLAMD=yes|no
550 Should CTDB manage ClamAV?
551 Default is no.
553 CTDB_CLAMD_SOCKET=FILENAME
555 FILENAME is the socket to monitor ClamAV.
556 No default.
558 ISCSI
560 CTDB has support for managing the Linux iSCSI tgtd service.
561 Eventscript
563 70.iscsi
564 CTDB_MANAGES_ISCSI=yes|no
566 Should CTDB manage iSCSI tgtd?
567 Default is no.
569 CTDB_START_ISCSI_SCRIPTS=DIRECTORY
571 DIRECTORY on shared storage containing scripts to start tgtd for
572 each public IP address.
573 No default.
575 MULTIPATHD
577 CTDB can monitor multipath devices to ensure that active paths are
578 available.
579 Eventscript
581 20.multipathd
582 This eventscript is not enabled by default. Use ctdb enablescript
584 to enable it.
585 CTDB_MONITOR_MPDEVICES=MP-DEVICE-LIST
587 MP-DEVICE-LIST is a list of multipath devices for CTDB to monitor?
588 No default.
590 VSFTPD
592 CTDB can manage the vsftpd FTP server.
593 Eventscript
595 40.vsftpd
596 CTDB_MANAGES_VSFTPD=yes|no
598 Should CTDB manage the vsftpd FTP server?
599 Default is no.
601 SYSTEM RESOURCE MONITORING CONFIGURATION
603 CTDB can experience seemingly random (performance and other) issues if
604 system resources become too constrained. Options in this section can be
605 enabled to allow certain system resources to be checked. They allows
606 warnings to be logged and nodes to be marked unhealthy when system
607 resource usage reaches the configured thresholds.
608 Some checks are enabled by default. It is recommended that these checks
610 remain enabled or are augmented by extra checks. There is no supported
611 way of completely disabling the checks.
612 Eventscripts
614 05.system
615 Filesystem and memory usage monitoring is in 05.system.
617 CTDB_MONITOR_FILESYSTEM_USAGE=FS-LIMIT-LIST
619 FS-LIMIT-LIST is a space-separated list of
620 FILESYSTEM:WARN_LIMIT[:UNHEALTHY_LIMIT] triples indicating that
621 warnings should be logged if the space used on FILESYSTEM reaches
622 WARN_LIMIT%. If usage reaches UNHEALTHY_LIMIT then the node should
623 be flagged unhealthy. Either WARN_LIMIT or UNHEALTHY_LIMIT may be
624 left blank, meaning that check will be omitted.
625 Default is to warn for each filesystem containing a database
627 directory (CTDB_DBDIR, CTDB_DBDIR_PERSISTENT, CTDB_DBDIR_STATE)
628 with a threshold of 90%.
629 CTDB_MONITOR_MEMORY_USAGE=MEM-LIMITS
631 MEM-LIMITS takes the form WARN_LIMIT[:UNHEALTHY_LIMIT] indicating
632 that warnings should be logged if memory usage reaches WARN_LIMIT%.
633 If usage reaches UNHEALTHY_LIMIT then the node should be flagged
634 unhealthy. Either WARN_LIMIT or UNHEALTHY_LIMIT may be left blank,
635 meaning that check will be omitted.
636 Default is 80, so warnings will be logged when memory usage reaches
638 80%.
639 CTDB_MONITOR_SWAP_USAGE=SWAP-LIMITS
641 SWAP-LIMITS takes the form WARN_LIMIT[:UNHEALTHY_LIMIT] indicating
642 that warnings should be logged if swap usage reaches WARN_LIMIT%.
643 If usage reaches UNHEALTHY_LIMIT then the node should be flagged
644 unhealthy. Either WARN_LIMIT or UNHEALTHY_LIMIT may be left blank,
645 meaning that check will be omitted.
646 Default is 25, so warnings will be logged when swap usage reaches
648 25%.
649 MISCELLANEOUS SERVICE-RELATED CONFIGURATION
651 CTDB_MANAGED_SERVICES=SERVICE-LIST
652 SERVICE-LIST is a space-separated list of SERVICEs that CTDB should
653 manage. This can be used as an alternative to the
654 CTDB_MANAGES_SERVICE variables.
655 No default.
657
659 CTDB tunables (see ctdbd-tunables(7)) can be set from the configuration
660 file. They are set as follows:
661 CTDB_SET_TUNABLE=VALUE
663 For example:
666 CTDB_SET_MonitorInterval=20
668
672 Variable in this section are for debugging and testing CTDB. They
673 should not generally be needed.
674 CTDB_DEBUG_HUNG_SCRIPT=FILENAME
676 FILENAME is a script to run to log debug information when an event
677 script times out.
678 Default is CTDB_BASE/debug-hung-script.sh.
680 CTDB_DEBUG_HUNG_SCRIPT_LOGFILE=FILENAME
682 FILENAME specifies where log messages should go when debugging hung
683 eventscripts. This is a testing option. See also
684 CTDB_DEBUG_HUNG_SCRIPT.
685 No default. Messages go to stdout/stderr and are logged to the same
687 place as other CTDB log messages.
688 CTDB_DEBUG_HUNG_SCRIPT_STACKPAT=REGEXP
690 REGEXP specifies interesting processes for which stack traces
691 should be logged when debugging hung eventscripts and those
692 processes are matched in pstree output. REGEXP is an extended
693 regexp so choices are separated by pipes ('|'). However, REGEXP
694 should not contain parentheses. See also CTDB_DEBUG_HUNG_SCRIPT.
695 Default is "exportfs|rpcinfo".
697 CTDB_DEBUG_LOCKS=FILENAME
699 FILENAME is a script to run to log debug information when an CTDB
700 fails to freeze databases during recovery.
701 No default, usually CTDB_BASE/debug_locks.sh.
703 CTDB_SYS_ETCDIR=DIRECTORY
705 DIRECTORY containing system configuration files. This is used to
706 provide alternate configuration when testing and should not need to
707 be changed from the default.
708 Default is /etc.
710 CTDB_INIT_STYLE=debian|redhat|suse
712 This is the init style used by the Linux distribution (or other
713 operating system) being used. This is usually determined
714 dynamically by checking the system. This variable is used by the
715 initscript to determine which init system primitives to use. It is
716 also used by some eventscripts to choose the name of initscripts
717 for certain services, since these can vary between distributions.
718 No fixed default.
720 If this option needs to be changed from the calculated default for
722 the initscript to function properly, then it must be set in the
723 distribution-specific initscript configuration, such as
724 /etc/sysconfig/ctdb
725 CTDB_MAX_CORRUPT_DB_BACKUPS=NUM
727 NUM is the maximum number of volatile TDB database backups to be
728 kept (for each database) when a corrupt database is found during
729 startup. Volatile TDBs are zeroed during startup so backups are
730 needed to debug any corruption that occurs before a restart.
731 Default is 10.
733 CTDB_MAX_OPEN_FILES=NUM
735 NUM is the maximum number of open files.
736 There is no default.
738 CTDB_RC_LOCAL=FILENAME
740 FILENAME is a script fragment to be sourced by the functions that
741 is sourced by scripts. On example use would be to override function
742 definitions in unit tests. As a sanity check, this file must be
743 executable for it to be used.
744 No default.
746 CTDB_RUN_TIMEOUT_MONITOR=yes|no
748 Whether CTDB should simulate timing out monitor events. This uses
749 the 99.timeout eventscript.
750 Default is no.
752 CTDB_SUPPRESS_COREFILE=yes|no
754 Whether CTDB core files should be suppressed.
755 Default is no.
757 CTDB_VALGRIND=yes|no|COMMAND
759 If "yes", this causes ctdbd(1) to be run under valgrind(1) with
760 logs going to /var/log/ctdb_valgrind. If neither "yes" nor "no"
761 then the value is assumed to be a COMMAND (e.g. a valgrind
762 variation, a gdb(1) command) that is used in place of the default
763 valgrind command. In either case, the --valgrind option is passed
764 to ctdbd.
765 Default is no.
767 CTDB_VARDIR=DIRECTORY
769 DIRECTORY containing CTDB files that are modified at runtime.
770 Defaults to /var/lib/ctdb.
772
774 /etc/ctdb/ctdbd.conf
775 /etc/sysconfig/ctdb
776 /etc/default/ctdb
777 /etc/ctdb/sysconfig/ctdb
778
780 ctdbd(1), ctdbd_wrapper(1), onnode(1), ctdb(7), ctdb-tunables(7),
781 http://ctdb.samba.org/
782
784 This documentation was written by Amitay Isaacs, Martin Schwenke
785
787 Copyright © 2007 Andrew Tridgell, Ronnie Sahlberg
788 This program is free software; you can redistribute it and/or modify it
790 under the terms of the GNU General Public License as published by the
791 Free Software Foundation; either version 3 of the License, or (at your
792 option) any later version.
793 This program is distributed in the hope that it will be useful, but
795 WITHOUT ANY WARRANTY; without even the implied warranty of
796 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
797 General Public License for more details.
798 You should have received a copy of the GNU General Public License along
800 with this program; if not, see http://www.gnu.org/licenses.
801
804 1. NFS-Ganesha
805 https://github.com/nfs-ganesha/nfs-ganesha/wiki
806ctdb 10/30/2018 CTDBD.CONF(5)