1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
|
<html><head><meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"><title>ctdb</title><meta name="generator" content="DocBook XSL Stylesheets V1.78.1"></head><body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF"><div class="refentry"><a name="ctdb.1"></a><div class="titlepage"></div><div class="refnamediv"><h2>Name</h2><p>ctdb — CTDB management utility</p></div><div class="refsynopsisdiv"><h2>Synopsis</h2><div class="cmdsynopsis"><p><code class="command">ctdb</code> [<em class="replaceable"><code>OPTION</code></em>...] {<em class="replaceable"><code>COMMAND</code></em>} [<em class="replaceable"><code>COMMAND-ARGS</code></em>]</p></div></div><div class="refsect1"><a name="idm139913067079344"></a><h2>DESCRIPTION</h2><p>
ctdb is a utility to view and manage a CTDB cluster.
</p><p>
The following terms are used when referring to nodes in a
cluster:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">PNN</span></dt><dd><p>
Physical Node Number. The physical node number is an
integer that describes the node in the cluster. The
first node has physical node number 0. in a cluster.
</p></dd><dt><span class="term">PNN-LIST</span></dt><dd><p>
This is either a single PNN, a comma-separate list of PNNs
or "all".
</p></dd></dl></div><p>
</p><p>
Commands that reference a database use the following terms:
</p><div class="variablelist"><dl class="variablelist"><dt><span class="term">DB</span></dt><dd><p>
This is either a database name, such as
<code class="filename">locking.tdb</code> or a database ID such
as "0x42fe72c5".
</p></dd><dt><span class="term">DB-LIST</span></dt><dd><p>
A space separated list of at least one
<em class="parameter"><code>DB</code></em>.
</p></dd></dl></div><p>
</p></div><div class="refsect1"><a name="idm139913065956016"></a><h2>OPTIONS</h2><div class="variablelist"><dl class="variablelist"><dt><span class="term">-n <em class="parameter"><code>PNN-LIST</code></em></span></dt><dd><p>
The nodes specified by PNN-LIST should be queried for the
requested information. Default is to query the daemon
running on the local host.
</p></dd><dt><span class="term">-Y</span></dt><dd><p>
Produce output in machine readable form for easier parsing
by scripts. Not all commands support this option.
</p></dd><dt><span class="term">-t <em class="parameter"><code>TIMEOUT</code></em></span></dt><dd><p>
Indicates that ctdb should wait up to TIMEOUT seconds for
a response to most commands sent to the CTDB daemon. The
default is 10 seconds.
</p></dd><dt><span class="term">-T <em class="parameter"><code>TIMELIMIT</code></em></span></dt><dd><p>
Indicates that TIMELIMIT is the maximum run time (in
seconds) for the ctdb command. When TIMELIMIT is exceeded
the ctdb command will terminate with an error. The default
is 120 seconds.
</p></dd><dt><span class="term">-? --help</span></dt><dd><p>
Print some help text to the screen.
</p></dd><dt><span class="term">--usage</span></dt><dd><p>
Print useage information to the screen.
</p></dd><dt><span class="term">-d --debug=<em class="parameter"><code>DEBUGLEVEL</code></em></span></dt><dd><p>
Change the debug level for the command. Default is ERR (0).
</p></dd><dt><span class="term">--socket=<em class="parameter"><code>FILENAME</code></em></span></dt><dd><p>
Specify that FILENAME is the name of the Unix domain
socket to use when connecting to the local CTDB
daemon. The default is
<code class="filename">/tmp/ctdb.socket</code>.
</p></dd></dl></div></div><div class="refsect1"><a name="idm139913070616816"></a><h2>ADMINISTRATIVE COMMANDS</h2><p>
These are commands used to monitor and administer a CTDB cluster.
</p><div class="refsect2"><a name="idm139913070615760"></a><h3>pnn</h3><p>
This command displays the PNN of the current node.
</p></div><div class="refsect2"><a name="idm139913070614560"></a><h3>xpnn</h3><p>
This command displays the PNN of the current node without
contacting the CTDB daemon. It parses the nodes file
directly, so can produce unexpected output if the nodes file
has been edited but has not been reloaded.
</p></div><div class="refsect2"><a name="idm139913070613136"></a><h3>status</h3><p>
This command shows the current status of all CTDB nodes based
on information from the queried node.
</p><p>
Note: If the the queried node is INACTIVE then the status
might not be current.
</p><div class="refsect3"><a name="idm139913070611456"></a><h4>Node status</h4><p>
This includes the number of physical nodes and the status of
each node. See <span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for information
about node states.
</p></div><div class="refsect3"><a name="idm139913070609296"></a><h4>Generation</h4><p>
The generation id is a number that indicates the current generation
of a cluster instance. Each time a cluster goes through a
reconfiguration or a recovery its generation id will be changed.
</p><p>
This number does not have any particular meaning other than
to keep track of when a cluster has gone through a
recovery. It is a random number that represents the current
instance of a ctdb cluster and its databases. The CTDB
daemon uses this number internally to be able to tell when
commands to operate on the cluster and the databases was
issued in a different generation of the cluster, to ensure
that commands that operate on the databases will not survive
across a cluster database recovery. After a recovery, all
old outstanding commands will automatically become invalid.
</p><p>
Sometimes this number will be shown as "INVALID". This only means that
the ctdbd daemon has started but it has not yet merged with the cluster through a recovery.
All nodes start with generation "INVALID" and are not assigned a real
generation id until they have successfully been merged with a cluster
through a recovery.
</p></div><div class="refsect3"><a name="idm139913070606144"></a><h4>Virtual Node Number (VNN) map</h4><p>
Consists of the number of virtual nodes and mapping from
virtual node numbers to physical node numbers. Virtual
nodes host CTDB databases. Only nodes that are
participating in the VNN map can become lmaster or dmaster
for database records.
</p></div><div class="refsect3"><a name="idm139913070604672"></a><h4>Recovery mode</h4><p>
This is the current recovery mode of the cluster. There are two possible modes:
</p><p>
NORMAL - The cluster is fully operational.
</p><p>
RECOVERY - The cluster databases have all been frozen, pausing all services while the cluster awaits a recovery process to complete. A recovery process should finish within seconds. If a cluster is stuck in the RECOVERY state this would indicate a cluster malfunction which needs to be investigated.
</p><p>
Once the recovery master detects an inconsistency, for example a node
becomes disconnected/connected, the recovery daemon will trigger a
cluster recovery process, where all databases are remerged across the
cluster. When this process starts, the recovery master will first
"freeze" all databases to prevent applications such as samba from
accessing the databases and it will also mark the recovery mode as
RECOVERY.
</p><p>
When the CTDB daemon starts up, it will start in RECOVERY
mode. Once the node has been merged into a cluster and all
databases have been recovered, the node mode will change into
NORMAL mode and the databases will be "thawed", allowing samba
to access the databases again.
</p></div><div class="refsect3"><a name="idm139913070593200"></a><h4>Recovery master</h4><p>
This is the cluster node that is currently designated as the recovery master. This node is responsible of monitoring the consistency of the cluster and to perform the actual recovery process when reqired.
</p><p>
Only one node at a time can be the designated recovery master. Which
node is designated the recovery master is decided by an election
process in the recovery daemons running on each node.
</p></div><div class="refsect3"><a name="idm139913070591200"></a><h4>Example</h4><pre class="screen">
# ctdb status
Number of nodes:4
pnn:0 192.168.2.200 OK (THIS NODE)
pnn:1 192.168.2.201 OK
pnn:2 192.168.2.202 OK
pnn:3 192.168.2.203 OK
Generation:1362079228
Size:4
hash:0 lmaster:0
hash:1 lmaster:1
hash:2 lmaster:2
hash:3 lmaster:3
Recovery mode:NORMAL (0)
Recovery master:0
</pre></div></div><div class="refsect2"><a name="idm139913070589296"></a><h3>nodestatus [<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]</h3><p>
This command is similar to the <span class="command"><strong>status</strong></span>
command. It displays the "node status" subset of output. The
main differences are:
</p><div class="itemizedlist"><ul class="itemizedlist" style="list-style-type: disc; "><li class="listitem"><p>
The exit code is the bitwise-OR of the flags for each
specified node, while <span class="command"><strong>ctdb status</strong></span> exits
with 0 if it was able to retrieve status for all nodes.
</p></li><li class="listitem"><p>
<span class="command"><strong>ctdb status</strong></span> provides status information
for all nodes. <span class="command"><strong>ctdb nodestatus</strong></span>
defaults to providing status for only the current node.
If PNN-LIST is provided then status is given for
the indicated node(s).
</p><p>
By default, <span class="command"><strong>ctdb nodestatus</strong></span> gathers
status from the local node. However, if invoked with "-n
all" (or similar) then status is gathered from the given
node(s). In particular <span class="command"><strong>ctdb nodestatus
all</strong></span> and <span class="command"><strong>ctdb nodestatus -n
all</strong></span> will produce different output. It is
possible to provide 2 different nodespecs (with and
without "-n") but the output is usually confusing!
</p></li></ul></div><p>
A common invocation in scripts is <span class="command"><strong>ctdb nodestatus
all</strong></span> to check whether all nodes in a cluster are
healthy.
</p><div class="refsect3"><a name="idm139913070578400"></a><h4>Example</h4><pre class="screen">
# ctdb nodestatus
pnn:0 10.0.0.30 OK (THIS NODE)
# ctdb nodestatus all
Number of nodes:2
pnn:0 10.0.0.30 OK (THIS NODE)
pnn:1 10.0.0.31 OK
</pre></div></div><div class="refsect2"><a name="idm139913070576640"></a><h3>recmaster</h3><p>
This command shows the pnn of the node which is currently the recmaster.
</p><p>
Note: If the the queried node is INACTIVE then the status
might not be current.
</p></div><div class="refsect2"><a name="idm139913070574864"></a><h3>uptime</h3><p>
This command shows the uptime for the ctdb daemon. When the last recovery or ip-failover completed and how long it took. If the "duration" is shown as a negative number, this indicates that there is a recovery/failover in progress and it started that many seconds ago.
</p><div class="refsect3"><a name="idm139913070573520"></a><h4>Example</h4><pre class="screen">
# ctdb uptime
Current time of node : Thu Oct 29 10:38:54 2009
Ctdbd start time : (000 16:54:28) Wed Oct 28 17:44:26 2009
Time of last recovery/failover: (000 16:53:31) Wed Oct 28 17:45:23 2009
Duration of last recovery/failover: 2.248552 seconds
</pre></div></div><div class="refsect2"><a name="idm139913070571632"></a><h3>listnodes</h3><p>
This command shows lists the ip addresses of all the nodes in the cluster.
</p><div class="refsect3"><a name="idm139913065124016"></a><h4>Example</h4><pre class="screen">
# ctdb listnodes
192.168.2.200
192.168.2.201
192.168.2.202
192.168.2.203
</pre></div></div><div class="refsect2"><a name="idm139913065122400"></a><h3>natgwlist</h3><p>
Show the current NAT gateway master and the status of all
nodes in the current NAT gateway group. See the
<em class="citetitle">NAT GATEWAY</em> section in
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more details.
</p><div class="refsect3"><a name="idm139913065119968"></a><h4>Example</h4><pre class="screen">
# ctdb natgwlist
0 192.168.2.200
Number of nodes:4
pnn:0 192.168.2.200 OK (THIS NODE)
pnn:1 192.168.2.201 OK
pnn:2 192.168.2.202 OK
pnn:3 192.168.2.203 OK
</pre></div></div><div class="refsect2"><a name="idm139913065118256"></a><h3>ping</h3><p>
This command will "ping" specified CTDB nodes in the cluster
to verify that they are running.
</p><div class="refsect3"><a name="idm139913065117120"></a><h4>Example</h4><pre class="screen">
# ctdb ping -n all
response from 0 time=0.000054 sec (3 clients)
response from 1 time=0.000144 sec (2 clients)
response from 2 time=0.000105 sec (2 clients)
response from 3 time=0.000114 sec (2 clients)
</pre></div></div><div class="refsect2"><a name="idm139913065115376"></a><h3>ifaces</h3><p>
This command will display the list of network interfaces, which could
host public addresses, along with their status.
</p><div class="refsect3"><a name="idm139913065114208"></a><h4>Example</h4><pre class="screen">
# ctdb ifaces
Interfaces on node 0
name:eth5 link:up references:2
name:eth4 link:down references:0
name:eth3 link:up references:1
name:eth2 link:up references:1
# ctdb ifaces -Y
:Name:LinkStatus:References:
:eth5:1:2
:eth4:0:0
:eth3:1:1
:eth2:1:1
</pre></div></div><div class="refsect2"><a name="idm139913065112416"></a><h3>ip</h3><p>
This command will display the list of public addresses that are provided by the cluster and which physical node is currently serving this ip. By default this command will ONLY show those public addresses that are known to the node itself. To see the full list of all public ips across the cluster you must use "ctdb ip -n all".
</p><div class="refsect3"><a name="idm139913065111040"></a><h4>Example</h4><pre class="screen">
# ctdb ip
Public IPs on node 0
172.31.91.82 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
172.31.91.83 node[0] active[eth3] available[eth2,eth3] configured[eth2,eth3]
172.31.91.84 node[1] active[] available[eth2,eth3] configured[eth2,eth3]
172.31.91.85 node[0] active[eth2] available[eth2,eth3] configured[eth2,eth3]
172.31.92.82 node[1] active[] available[eth5] configured[eth4,eth5]
172.31.92.83 node[0] active[eth5] available[eth5] configured[eth4,eth5]
172.31.92.84 node[1] active[] available[eth5] configured[eth4,eth5]
172.31.92.85 node[0] active[eth5] available[eth5] configured[eth4,eth5]
# ctdb ip -Y
:Public IP:Node:ActiveInterface:AvailableInterfaces:ConfiguredInterfaces:
:172.31.91.82:1::eth2,eth3:eth2,eth3:
:172.31.91.83:0:eth3:eth2,eth3:eth2,eth3:
:172.31.91.84:1::eth2,eth3:eth2,eth3:
:172.31.91.85:0:eth2:eth2,eth3:eth2,eth3:
:172.31.92.82:1::eth5:eth4,eth5:
:172.31.92.83:0:eth5:eth5:eth4,eth5:
:172.31.92.84:1::eth5:eth4,eth5:
:172.31.92.85:0:eth5:eth5:eth4,eth5:
</pre></div></div><div class="refsect2"><a name="idm139913065107504"></a><h3>ipinfo <em class="parameter"><code>IP</code></em></h3><p>
This command will display details about the specified public addresses.
</p><div class="refsect3"><a name="idm139913065105888"></a><h4>Example</h4><pre class="screen">
# ctdb ipinfo 172.31.92.85
Public IP[172.31.92.85] info on node 0
IP:172.31.92.85
CurrentNode:0
NumInterfaces:2
Interface[1]: Name:eth4 Link:down References:0
Interface[2]: Name:eth5 Link:up References:2 (active)
</pre></div></div><div class="refsect2"><a name="idm139913065104144"></a><h3>scriptstatus</h3><p>
This command displays which scripts where run in the previous monitoring cycle and the result of each script. If a script failed with an error, causing the node to become unhealthy, the output from that script is also shown.
</p><div class="refsect3"><a name="idm139913065102864"></a><h4>Example</h4><pre class="screen">
# ctdb scriptstatus
7 scripts were executed last monitoring cycle
00.ctdb Status:OK Duration:0.056 Tue Mar 24 18:56:57 2009
10.interface Status:OK Duration:0.077 Tue Mar 24 18:56:57 2009
11.natgw Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
20.multipathd Status:OK Duration:0.038 Tue Mar 24 18:56:57 2009
31.clamd Status:DISABLED
40.vsftpd Status:OK Duration:0.045 Tue Mar 24 18:56:57 2009
41.httpd Status:OK Duration:0.039 Tue Mar 24 18:56:57 2009
50.samba Status:ERROR Duration:0.082 Tue Mar 24 18:56:57 2009
OUTPUT:ERROR: Samba tcp port 445 is not responding
</pre></div></div><div class="refsect2"><a name="idm139913065100640"></a><h3>disablescript <em class="parameter"><code>SCRIPT</code></em></h3><p>
This command is used to disable an eventscript.
</p><p>
This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in 'scriptstatus'.
</p></div><div class="refsect2"><a name="idm139913065098432"></a><h3>enablescript <em class="parameter"><code>SCRIPT</code></em></h3><p>
This command is used to enable an eventscript.
</p><p>
This will take effect the next time the eventscripts are being executed so it can take a short while until this is reflected in 'scriptstatus'.
</p></div><div class="refsect2"><a name="idm139913065096224"></a><h3>listvars</h3><p>
List all tuneable variables, except the values of the obsolete tunables
like VacuumMinInterval. The obsolete tunables can be retrieved only
explicitly with the "ctdb getvar" command.
</p><div class="refsect3"><a name="idm139913065094992"></a><h4>Example</h4><pre class="screen">
# ctdb listvars
MaxRedirectCount = 3
SeqnumInterval = 1000
ControlTimeout = 60
TraverseTimeout = 20
KeepaliveInterval = 5
KeepaliveLimit = 5
RecoverTimeout = 20
RecoverInterval = 1
ElectionTimeout = 3
TakeoverTimeout = 9
MonitorInterval = 15
TickleUpdateInterval = 20
EventScriptTimeout = 30
EventScriptTimeoutCount = 1
RecoveryGracePeriod = 120
RecoveryBanPeriod = 300
DatabaseHashSize = 100001
DatabaseMaxDead = 5
RerecoveryTimeout = 10
EnableBans = 1
DeterministicIPs = 0
LCP2PublicIPs = 1
ReclockPingPeriod = 60
NoIPFailback = 0
DisableIPFailover = 0
VerboseMemoryNames = 0
RecdPingTimeout = 60
RecdFailCount = 10
LogLatencyMs = 0
RecLockLatencyMs = 1000
RecoveryDropAllIPs = 120
VerifyRecoveryLock = 1
VacuumInterval = 10
VacuumMaxRunTime = 30
RepackLimit = 10000
VacuumLimit = 5000
VacuumFastPathCount = 60
MaxQueueDropMsg = 1000000
UseStatusEvents = 0
AllowUnhealthyDBRead = 0
StatHistoryInterval = 1
DeferredAttachTO = 120
AllowClientDBAttach = 1
RecoverPDBBySeqNum = 0
</pre></div></div><div class="refsect2"><a name="idm139913065090864"></a><h3>getvar <em class="parameter"><code>NAME</code></em></h3><p>
Get the runtime value of a tuneable variable.
</p><div class="refsect3"><a name="idm139913065089344"></a><h4>Example</h4><pre class="screen">
# ctdb getvar MaxRedirectCount
MaxRedirectCount = 3
</pre></div></div><div class="refsect2"><a name="idm139913065087824"></a><h3>setvar <em class="parameter"><code>NAME</code></em> <em class="parameter"><code>VALUE</code></em></h3><p>
Set the runtime value of a tuneable variable.
</p><p>
Example: ctdb setvar MaxRedirectCount 5
</p></div><div class="refsect2"><a name="idm139913065085168"></a><h3>lvsmaster</h3><p>
This command shows which node is currently the LVSMASTER. The
LVSMASTER is the node in the cluster which drives the LVS system and
which receives all incoming traffic from clients.
</p><p>
LVS is the mode where the entire CTDB/Samba cluster uses a single
ip address for the entire cluster. In this mode all clients connect to
one specific node which will then multiplex/loadbalance the clients
evenly onto the other nodes in the cluster. This is an alternative to using
public ip addresses. See the manpage for ctdbd for more information
about LVS.
</p></div><div class="refsect2"><a name="idm139913065083040"></a><h3>lvs</h3><p>
This command shows which nodes in the cluster are currently active in the
LVS configuration. I.e. which nodes we are currently loadbalancing
the single ip address across.
</p><p>
LVS will by default only loadbalance across those nodes that are both
LVS capable and also HEALTHY. Except if all nodes are UNHEALTHY in which
case LVS will loadbalance across all UNHEALTHY nodes as well.
LVS will never use nodes that are DISCONNECTED, STOPPED, BANNED or
DISABLED.
</p><p>
Example output:
</p><pre class="screen">
2:10.0.0.13
3:10.0.0.14
</pre></div><div class="refsect2"><a name="idm139913065080000"></a><h3>getcapabilities</h3><p>
This command shows the capabilities of the current node. See
the <em class="citetitle">CAPABILITIES</em> section in
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span> for more details.
</p><p>
Example output:
</p><pre class="screen">
RECMASTER: YES
LMASTER: YES
LVS: NO
NATGW: YES
</pre></div><div class="refsect2"><a name="idm139913065076560"></a><h3>statistics</h3><p>
Collect statistics from the CTDB daemon about
how many calls it has served. Information about
various fields in statistics can be found in
<span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>.
</p><div class="refsect3"><a name="idm139913065074464"></a><h4>Example</h4><pre class="screen">
# ctdb statistics
CTDB version 1
num_clients 3
frozen 0
recovering 0
client_packets_sent 360489
client_packets_recv 360466
node_packets_sent 480931
node_packets_recv 240120
keepalive_packets_sent 4
keepalive_packets_recv 3
node
req_call 2
reply_call 2
req_dmaster 0
reply_dmaster 0
reply_error 0
req_message 42
req_control 120408
reply_control 360439
client
req_call 2
req_message 24
req_control 360440
timeouts
call 0
control 0
traverse 0
total_calls 2
pending_calls 0
lockwait_calls 0
pending_lockwait_calls 0
memory_used 5040
max_hop_count 0
max_call_latency 4.948321 sec
max_lockwait_latency 0.000000 sec
</pre></div></div><div class="refsect2"><a name="idm139913065070592"></a><h3>statisticsreset</h3><p>
This command is used to clear all statistics counters in a node.
</p><p>
Example: ctdb statisticsreset
</p></div><div class="refsect2"><a name="idm139913065068960"></a><h3>dbstatistics <em class="parameter"><code>DB</code></em></h3><p>
Display statistics about the database DB. Information
about various fields in dbstatistics can be found in
<span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>.
</p><div class="refsect3"><a name="idm139913065066416"></a><h4>Example</h4><pre class="screen">
# ctdb dbstatistics locking.tdb
DB Statistics: locking.tdb
ro_delegations 0
ro_revokes 0
locks
total 14356
failed 0
current 0
pending 0
hop_count_buckets: 28087 2 1 0 0 0 0 0 0 0 0 0 0 0 0 0
lock_buckets: 0 14188 38 76 32 19 3 0 0 0 0 0 0 0 0 0
locks_latency MIN/AVG/MAX 0.001066/0.012686/4.202292 sec out of 14356
Num Hot Keys: 1
Count:8 Key:ff5bd7cb3ee3822edc1f0000000000000000000000000000
</pre></div></div><div class="refsect2"><a name="idm139913065064304"></a><h3>getreclock</h3><p>
This command is used to show the filename of the reclock file that is used.
</p><p>
Example output:
</p><pre class="screen">
Reclock file:/gpfs/.ctdb/shared
</pre></div><div class="refsect2"><a name="idm139913065062048"></a><h3>setreclock [filename]</h3><p>
This command is used to modify, or clear, the file that is used as the reclock file at runtime. When this command is used, the reclock file checks are disabled. To re-enable the checks the administrator needs to activate the "VerifyRecoveryLock" tunable using "ctdb setvar".
</p><p>
If run with no parameter this will remove the reclock file completely. If run with a parameter the parameter specifies the new filename to use for the recovery lock.
</p><p>
This command only affects the runtime settings of a ctdb node and will be lost when ctdb is restarted. For persistent changes to the reclock file setting you must edit /etc/sysconfig/ctdb.
</p></div><div class="refsect2"><a name="idm139913065059424"></a><h3>getdebug</h3><p>
Get the current debug level for the node. the debug level controls what information is written to the log file.
</p><p>
The debug levels are mapped to the corresponding syslog levels.
When a debug level is set, only those messages at that level and higher
levels will be printed.
</p><p>
The list of debug levels from highest to lowest are :
</p><p>
EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
</p></div><div class="refsect2"><a name="idm139913065056784"></a><h3>setdebug <em class="parameter"><code>DEBUGLEVEL</code></em></h3><p>
Set the debug level of a node. This controls what information will be logged.
</p><p>
The debuglevel is one of EMERG ALERT CRIT ERR WARNING NOTICE INFO DEBUG
</p></div><div class="refsect2"><a name="idm139913065054560"></a><h3>getpid</h3><p>
This command will return the process id of the ctdb daemon.
</p></div><div class="refsect2"><a name="idm139913065053408"></a><h3>disable</h3><p>
This command is used to administratively disable a node in the cluster.
A disabled node will still participate in the cluster and host
clustered TDB records but its public ip address has been taken over by
a different node and it no longer hosts any services.
</p></div><div class="refsect2"><a name="idm139913065051968"></a><h3>enable</h3><p>
Re-enable a node that has been administratively disabled.
</p></div><div class="refsect2"><a name="idm139913065050736"></a><h3>stop</h3><p>
This command is used to administratively STOP a node in the cluster.
A STOPPED node is connected to the cluster but will not host any
public ip addresse, nor does it participate in the VNNMAP.
The difference between a DISABLED node and a STOPPED node is that
a STOPPED node does not host any parts of the database which means
that a recovery is required to stop/continue nodes.
</p></div><div class="refsect2"><a name="idm139913065049184"></a><h3>continue</h3><p>
Re-start a node that has been administratively stopped.
</p></div><div class="refsect2"><a name="idm139913065047952"></a><h3>addip <em class="parameter"><code>IPADDR</code></em>/<em class="parameter"><code>mask</code></em> <em class="parameter"><code>IFACE</code></em></h3><p>
This command is used to add a new public ip to a node during runtime.
This allows public addresses to be added to a cluster without having
to restart the ctdb daemons.
</p><p>
Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
If you want this change to be permanent you must also update the public addresses file manually.
</p></div><div class="refsect2"><a name="idm139913065044208"></a><h3>delip <em class="parameter"><code>IPADDR</code></em></h3><p>
This command is used to remove a public ip from a node during runtime.
If this public ip is currently hosted by the node it being removed from, the ip will first be failed over to another node, if possible, before it is removed.
</p><p>
Note that this only updates the runtime instance of ctdb. Any changes will be lost next time ctdb is restarted and the public addresses file is re-read.
If you want this change to be permanent you must also update the public addresses file manually.
</p></div><div class="refsect2"><a name="idm139913065041648"></a><h3>moveip <em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>PNN</code></em></h3><p>
This command can be used to manually fail a public ip address to a
specific node.
</p><p>
In order to manually override the "automatic" distribution of public
ip addresses that ctdb normally provides, this command only works
when you have changed the tunables for the daemon to:
</p><p>
DeterministicIPs = 0
</p><p>
NoIPFailback = 1
</p></div><div class="refsect2"><a name="idm139913065037888"></a><h3>shutdown</h3><p>
This command will shutdown a specific CTDB daemon.
</p></div><div class="refsect2"><a name="idm139913065036656"></a><h3>setlmasterrole on|off</h3><p>
This command is used ot enable/disable the LMASTER capability for a node at runtime. This capability determines whether or not a node can be used as an LMASTER for records in the database. A node that does not have the LMASTER capability will not show up in the vnnmap.
</p><p>
Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command.
</p><p>
Once this setting has been enabled/disabled, you need to perform a recovery for it to take effect.
</p><p>
See also "ctdb getcapabilities"
</p></div><div class="refsect2"><a name="idm139913065033776"></a><h3>setrecmasterrole on|off</h3><p>
This command is used ot enable/disable the RECMASTER capability for a node at runtime. This capability determines whether or not a node can be used as an RECMASTER for the cluster. A node that does not have the RECMASTER capability can not win a recmaster election. A node that already is the recmaster for the cluster when the capability is stripped off the node will remain the recmaster until the next cluster election.
</p><p>
Nodes will by default have this capability, but it can be stripped off nodes by the setting in the sysconfig file or by using this command.
</p><p>
See also "ctdb getcapabilities"
</p></div><div class="refsect2"><a name="idm139913065031248"></a><h3>reloadnodes</h3><p>
This command is used when adding new nodes, or removing existing nodes from an existing cluster.
</p><p>
Procedure to add a node:
</p><p>
1, To expand an existing cluster, first ensure with 'ctdb status' that
all nodes are up and running and that they are all healthy.
Do not try to expand a cluster unless it is completely healthy!
</p><p>
2, On all nodes, edit /etc/ctdb/nodes and add the new node as the last
entry to the file. The new node MUST be added to the end of this file!
</p><p>
3, Verify that all the nodes have identical /etc/ctdb/nodes files after you edited them and added the new node!
</p><p>
4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
</p><p>
5, Use 'ctdb status' on all nodes and verify that they now show the additional node.
</p><p>
6, Install and configure the new node and bring it online.
</p><p>
Procedure to remove a node:
</p><p>
1, To remove a node from an existing cluster, first ensure with 'ctdb status' that
all nodes, except the node to be deleted, are up and running and that they are all healthy.
Do not try to remove a node from a cluster unless the cluster is completely healthy!
</p><p>
2, Shutdown and poweroff the node to be removed.
</p><p>
3, On all other nodes, edit the /etc/ctdb/nodes file and comment out the node to be removed. Do not delete the line for that node, just comment it out by adding a '#' at the beginning of the line.
</p><p>
4, Run 'ctdb reloadnodes' to force all nodes to reload the nodesfile.
</p><p>
5, Use 'ctdb status' on all nodes and verify that the deleted node no longer shows up in the list..
</p><p>
</p></div><div class="refsect2"><a name="idm139913065022960"></a><h3>
reloadips
[<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]
</h3><p>
This command reloads the public addresses configuration file
on the specified nodes. When it completes addresses will be
reconfigured and reassigned across the cluster as necessary.
</p></div><div class="refsect2"><a name="idm139913065020848"></a><h3>getdbmap</h3><p>
This command lists all clustered TDB databases that the CTDB daemon has attached to. Some databases are flagged as PERSISTENT, this means that the database stores data persistently and the data will remain across reboots. One example of such a database is secrets.tdb where information about how the cluster was joined to the domain is stored.
</p><p>
If a PERSISTENT database is not in a healthy state the database is
flagged as UNHEALTHY. If there's at least one completely healthy node running in
the cluster, it's possible that the content is restored by a recovery
run automaticly. Otherwise an administrator needs to analyze the
problem.
</p><p>
See also "ctdb getdbstatus", "ctdb backupdb", "ctdb restoredb",
"ctdb dumpbackup", "ctdb wipedb", "ctdb setvar AllowUnhealthyDBRead 1"
and (if samba or tdb-utils are installed) "tdbtool check".
</p><p>
Most databases are not persistent and only store the state information that the currently running samba daemons need. These databases are always wiped when ctdb/samba starts and when a node is rebooted.
</p><div class="refsect3"><a name="idm139913065017536"></a><h4>Example</h4><pre class="screen">
# ctdb getdbmap
Number of databases:10
dbid:0x435d3410 name:notify.tdb path:/var/ctdb/notify.tdb.0
dbid:0x42fe72c5 name:locking.tdb path:/var/ctdb/locking.tdb.0
dbid:0x1421fb78 name:brlock.tdb path:/var/ctdb/brlock.tdb.0
dbid:0x17055d90 name:connections.tdb path:/var/ctdb/connections.tdb.0
dbid:0xc0bdde6a name:sessionid.tdb path:/var/ctdb/sessionid.tdb.0
dbid:0x122224da name:test.tdb path:/var/ctdb/test.tdb.0
dbid:0x2672a57f name:idmap2.tdb path:/var/ctdb/persistent/idmap2.tdb.0 PERSISTENT
dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT
dbid:0xe98e08b6 name:group_mapping.tdb path:/var/ctdb/persistent/group_mapping.tdb.0 PERSISTENT
dbid:0x7bbbd26c name:passdb.tdb path:/var/ctdb/persistent/passdb.tdb.0 PERSISTENT
# ctdb getdbmap # example for unhealthy database
Number of databases:1
dbid:0xb775fff6 name:secrets.tdb path:/var/ctdb/persistent/secrets.tdb.0 PERSISTENT UNHEALTHY
# ctdb -Y getdbmap
:ID:Name:Path:Persistent:Unhealthy:
:0x7bbbd26c:passdb.tdb:/var/ctdb/persistent/passdb.tdb.0:1:0:
</pre></div></div><div class="refsect2"><a name="idm139913065013904"></a><h3>
backupdb
<em class="parameter"><code>DB</code></em>
<em class="parameter"><code>FILE</code></em>
</h3><p>
Copy the contents of database DB to FILE. FILE can later be
read back using <span class="command"><strong>restoredb</strong></span>. This is mainly
useful for backing up persistent databases such as
<code class="filename">secrets.tdb</code> and similar.
</p></div><div class="refsect2"><a name="idm139913065010080"></a><h3>
restoredb
<em class="parameter"><code>FILE</code></em>
[<span class="optional"><em class="parameter"><code>DB</code></em></span>]
</h3><p>
This command restores a persistent database that was
previously backed up using backupdb. By default the data will
be restored back into the same database as it was created
from. By specifying dbname you can restore the data into a
different database.
</p></div><div class="refsect2"><a name="idm139913065007264"></a><h3>getlog [<em class="parameter"><code>LEVEL</code></em>] [recoverd]</h3><p>
In addition to the normal logging to a log file, CTDB also
keeps a in-memory ringbuffer containing the most recent log
entries for all log levels (except DEBUG).
</p><p>
This is useful since it allows for keeping continuous logs to a file
at a reasonable non-verbose level, but shortly after an incident has
occured, a much more detailed log can be pulled from memory. This
can allow you to avoid having to reproduce an issue due to the
on-disk logs being of insufficient detail.
</p><p>
This command extracts all messages of level or lower log level
from memory and prints it to the screen. The level is not
specified it defaults to NOTICE.
</p><p>
By default, logs are extracted from the main CTDB daemon. If
the recoverd option is given then logs are extracted from the
recovery daemon.
</p></div><div class="refsect2"><a name="idm139913065003472"></a><h3>clearlog [recoverd]</h3><p>
This command clears the in-memory logging ringbuffer.
</p><p>
By default, logs are cleared in the main CTDB daemon. If the
recoverd option is given then logs are cleared in the recovery
daemon.
</p></div><div class="refsect2"><a name="idm139913065001696"></a><h3>setdbreadonly <em class="parameter"><code>DB</code></em></h3><p>
This command will enable the read-only record support for a
database. This is an experimental feature to improve
performance for contended records primarily in locking.tdb and
brlock.tdb. When enabling this feature you must set it on all
nodes in the cluster.
</p></div><div class="refsect2"><a name="idm139913064999760"></a><h3>setdbsticky <em class="parameter"><code>DB</code></em></h3><p>
This command will enable the sticky record support for the
specified database. This is an experimental feature to
improve performance for contended records primarily in
locking.tdb and brlock.tdb. When enabling this feature you
must set it on all nodes in the cluster.
</p></div></div><div class="refsect1"><a name="idm139913064997680"></a><h2>INTERNAL COMMANDS</h2><p>
Internal commands are used by CTDB's scripts and are not
required for managing a CTDB cluster. Their parameters and
behaviour are subject to change.
</p><div class="refsect2"><a name="idm139913064996464"></a><h3>gettickles <em class="parameter"><code>IPADDR</code></em></h3><p>
Show TCP connections that are registered with CTDB to be
"tickled" if there is a failover.
</p></div><div class="refsect2"><a name="idm139913064994704"></a><h3>gratiousarp <em class="parameter"><code>IPADDR</code></em> <em class="parameter"><code>INTERFACE</code></em></h3><p>
Send out a gratious ARP for the specified interface through
the specified interface. This command is mainly used by the
ctdb eventscripts.
</p></div><div class="refsect2"><a name="idm139913064992272"></a><h3>killtcp</h3><p>
Read a list of TCP connections, one per line, from standard
input and terminate each connection. A connection is
specified as:
</p><pre class="synopsis">
<em class="parameter"><code>SRC-IPADDR</code></em>:<em class="parameter"><code>SRC-PORT</code></em> <em class="parameter"><code>DST-IPADDR</code></em>:<em class="parameter"><code>DST-PORT</code></em>
</pre><p>
Each connection is terminated by issuing a TCP RST to the
SRC-IPADDR:SRC-PORT endpoint.
</p><p>
A single connection can be specified on the command-line
rather than on standard input.
</p></div><div class="refsect2"><a name="idm139913064986848"></a><h3>
pdelete <em class="parameter"><code>DB</code></em> <em class="parameter"><code>KEY</code></em>
</h3><p>
Delete KEY from DB.
</p></div><div class="refsect2"><a name="idm139913064984448"></a><h3>
pfetch <em class="parameter"><code>DB</code></em> <em class="parameter"><code>KEY</code></em>
</h3><p>
Print the value associated with KEY in DB.
</p></div><div class="refsect2"><a name="idm139913064982048"></a><h3>
pstore
<em class="parameter"><code>DB</code></em>
<em class="parameter"><code>KEY</code></em>
<em class="parameter"><code>FILE</code></em>
</h3><p>
Store KEY in DB with contents of FILE as the associated value.
</p></div><div class="refsect2"><a name="idm139913064978944"></a><h3>
ptrans
<em class="parameter"><code>DB</code></em>
[<span class="optional"><em class="parameter"><code>FILE</code></em></span>]
</h3><p>
Read a list of key-value pairs, one per line from FILE, and
store them in DB using a single transaction. An empty value
is equivalent to deleting the given key.
</p><p>
The key and value should be separated by spaces or tabs. Each
key/value should be a printable string enclosed in
double-quotes.
</p></div><div class="refsect2"><a name="idm139913064975680"></a><h3>runstate [setup|first_recovery|startup|running]</h3><p>
Print the runstate of the specified node. Runstates are used
to serialise important state transitions in CTDB, particularly
during startup.
</p><p>
If one or more optional runstate arguments are specified then
the node must be in one of these runstates for the command to
succeed.
</p><div class="refsect3"><a name="idm139913064973952"></a><h4>Example</h4><pre class="screen">
# ctdb runstate
RUNNING
</pre></div></div><div class="refsect2"><a name="idm139913064972432"></a><h3>setifacelink <em class="parameter"><code>IFACE</code></em> up|down</h3><p>
Set the internal state of network interface IFACE. This is
typically used in the <code class="filename">10.interface</code> script
in the "monitor" event.
</p><p>
Example: ctdb setifacelink eth0 up
</p></div><div class="refsect2"><a name="idm139913064969552"></a><h3>setnatgwstate on|off</h3><p>
Enable or disable the NAT gateway master capability on a node.
</p></div><div class="refsect2"><a name="idm139913064968320"></a><h3>tickle <em class="parameter"><code>SRC-IPADDR</code></em>:<em class="parameter"><code>SRC-PORT</code></em> <em class="parameter"><code>DST-IPADDR</code></em>:<em class="parameter"><code>DST-PORT</code></em></h3><p>
Send a TCP tickle to the source host for the specified TCP
connection. A TCP tickle is a TCP ACK packet with an invalid
sequence and acknowledge number and will when received by the
source host result in it sending an immediate correct ACK back
to the other end.
</p><p>
TCP tickles are useful to "tickle" clients after a IP failover has
occured since this will make the client immediately recognize the
TCP connection has been disrupted and that the client will need
to reestablish. This greatly speeds up the time it takes for a client
to detect and reestablish after an IP failover in the ctdb cluster.
</p></div><div class="refsect2"><a name="idm139913064963760"></a><h3>version</h3><p>
Display the CTDB version.
</p></div></div><div class="refsect1"><a name="idm139913064962480"></a><h2>DEBUGGING COMMANDS</h2><p>
These commands are primarily used for CTDB development and testing and
should not be used for normal administration.
</p><div class="refsect2"><a name="idm139913064961312"></a><h3>OPTIONS</h3><div class="variablelist"><dl class="variablelist"><dt><span class="term">--print-emptyrecords</span></dt><dd><p>
This enables printing of empty records when dumping databases
with the catdb, cattbd and dumpdbbackup commands. Records with
empty data segment are considered deleted by ctdb and cleaned
by the vacuuming mechanism, so this switch can come in handy for
debugging the vacuuming behaviour.
</p></dd><dt><span class="term">--print-datasize</span></dt><dd><p>
This lets database dumps (catdb, cattdb, dumpdbbackup) print the
size of the record data instead of dumping the data contents.
</p></dd><dt><span class="term">--print-lmaster</span></dt><dd><p>
This lets catdb print the lmaster for each record.
</p></dd><dt><span class="term">--print-hash</span></dt><dd><p>
This lets database dumps (catdb, cattdb, dumpdbbackup) print the
hash for each record.
</p></dd><dt><span class="term">--print-recordflags</span></dt><dd><p>
This lets catdb and dumpdbbackup print the
record flags for each record. Note that cattdb always
prints the flags.
</p></dd></dl></div></div><div class="refsect2"><a name="idm139913064952288"></a><h3>process-exists <em class="parameter"><code>PID</code></em></h3><p>
This command checks if a specific process exists on the CTDB host. This is mainly used by Samba to check if remote instances of samba are still running or not.
</p></div><div class="refsect2"><a name="idm139913064950448"></a><h3>getdbstatus <em class="parameter"><code>DB</code></em></h3><p>
This command displays more details about a database.
</p><div class="refsect3"><a name="idm139913064948848"></a><h4>Example</h4><pre class="screen">
# ctdb getdbstatus test.tdb.0
dbid: 0x122224da
name: test.tdb
path: /var/ctdb/test.tdb.0
PERSISTENT: no
HEALTH: OK
# ctdb getdbstatus registry.tdb # with a corrupted TDB
dbid: 0xf2a58948
name: registry.tdb
path: /var/ctdb/persistent/registry.tdb.0
PERSISTENT: yes
HEALTH: NO-HEALTHY-NODES - ERROR - Backup of corrupted TDB in '/var/ctdb/persistent/registry.tdb.0.corrupted.20091208091949.0Z'
</pre></div></div><div class="refsect2"><a name="idm139913064946912"></a><h3>catdb <em class="parameter"><code>DB</code></em></h3><p>
Print a dump of the clustered TDB database DB.
</p></div><div class="refsect2"><a name="idm139913064945264"></a><h3>cattdb <em class="parameter"><code>DB</code></em></h3><p>
Print a dump of the contents of the local TDB database DB.
</p></div><div class="refsect2"><a name="idm139913064943536"></a><h3>dumpdbbackup <em class="parameter"><code>FILE</code></em></h3><p>
Print a dump of the contents from database backup FILE,
similar to <span class="command"><strong>catdb</strong></span>.
</p></div><div class="refsect2"><a name="idm139913064941184"></a><h3>wipedb <em class="parameter"><code>DB</code></em></h3><p>
Remove all contents of database DB.
</p></div><div class="refsect2"><a name="idm139913064939536"></a><h3>recover</h3><p>
This command will trigger the recovery daemon to do a cluster
recovery.
</p></div><div class="refsect2"><a name="idm139913064938288"></a><h3>ipreallocate, sync</h3><p>
This command will force the recovery master to perform a full ip reallocation process and redistribute all ip addresses. This is useful to "reset" the allocations back to its default state if they have been changed using the "moveip" command. While a "recover" will also perform this reallocation, a recovery is much more hevyweight since it will also rebuild all the databases.
</p></div><div class="refsect2"><a name="idm139913064936352"></a><h3>getmonmode</h3><p>
This command returns the monutoring mode of a node. The monitoring mode is either ACTIVE or DISABLED. Normally a node will continuously monitor that all other nodes that are expected are in fact connected and that they respond to commands.
</p><p>
ACTIVE - This is the normal mode. The node is actively monitoring all other nodes, both that the transport is connected and also that the node responds to commands. If a node becomes unavailable, it will be marked as DISCONNECTED and a recovery is initiated to restore the cluster.
</p><p>
DISABLED - This node is not monitoring that other nodes are available. In this mode a node failure will not be detected and no recovery will be performed. This mode is useful when for debugging purposes one wants to attach GDB to a ctdb process but wants to prevent the rest of the cluster from marking this node as DISCONNECTED and do a recovery.
</p></div><div class="refsect2"><a name="idm139913064933488"></a><h3>setmonmode 0|1</h3><p>
This command can be used to explicitly disable/enable monitoring mode on a node. The main purpose is if one wants to attach GDB to a running ctdb daemon but wants to prevent the other nodes from marking it as DISCONNECTED and issuing a recovery. To do this, set monitoring mode to 0 on all nodes before attaching with GDB. Remember to set monitoring mode back to 1 afterwards.
</p></div><div class="refsect2"><a name="idm139913064931936"></a><h3>attach <em class="parameter"><code>DBNAME</code></em> [persistent]</h3><p>
Create a new CTDB database called DBNAME and attach to it on
all nodes.
</p></div><div class="refsect2"><a name="idm139913064930064"></a><h3>detach <em class="parameter"><code>DB-LIST</code></em></h3><p>
Detach specified non-persistent database(s) from the cluster. This
command will disconnect specified database(s) on all nodes in
the cluster. This command should only be used when none of the
specified database(s) are in use.
</p><p>
All nodes should be active and tunable AllowClientDBAccess should
be disabled on all nodes before detaching databases.
</p></div><div class="refsect2"><a name="idm139913064927632"></a><h3>dumpmemory</h3><p>
This is a debugging command. This command will make the ctdb
daemon to write a fill memory allocation map to standard output.
</p></div><div class="refsect2"><a name="idm139913064926336"></a><h3>rddumpmemory</h3><p>
This is a debugging command. This command will dump the talloc memory
allocation tree for the recovery daemon to standard output.
</p></div><div class="refsect2"><a name="idm139913064925024"></a><h3>thaw</h3><p>
Thaw a previously frozen node.
</p></div><div class="refsect2"><a name="idm139913064923872"></a><h3>eventscript <em class="parameter"><code>ARGUMENTS</code></em></h3><p>
This is a debugging command. This command can be used to manually
invoke and run the eventscritps with arbitrary arguments.
</p></div><div class="refsect2"><a name="idm139913064922080"></a><h3>ban <em class="parameter"><code>BANTIME</code></em></h3><p>
Administratively ban a node for BANTIME seconds. The node
will be unbanned after BANTIME seconds have elapsed.
</p><p>
A banned node does not participate in the cluster. It does
not host any records for the clustered TDB and does not host
any public IP addresses.
</p><p>
Nodes are automatically banned if they misbehave. For
example, a node may be banned if it causes too many cluster
recoveries.
</p><p>
To administratively exclude a node from a cluster use the
<span class="command"><strong>stop</strong></span> command.
</p></div><div class="refsect2"><a name="idm139913064918096"></a><h3>unban</h3><p>
This command is used to unban a node that has either been
administratively banned using the ban command or has been
automatically banned.
</p></div><div class="refsect2"><a name="idm139913064916784"></a><h3>
rebalancenode
[<span class="optional"><em class="parameter"><code>PNN-LIST</code></em></span>]
</h3><p>
This command marks the given nodes as rebalance targets in the
LCP2 IP allocation algorithm. The
<span class="command"><strong>reloadips</strong></span> command will do this as necessary
so this command should not be needed.
</p></div><div class="refsect2"><a name="idm139913064914048"></a><h3>check_srvids <em class="parameter"><code>SRVID</code></em> ...</h3><p>
This command checks whether a set of srvid message ports are
registered on the node or not. The command takes a list of
values to check.
</p><div class="refsect3"><a name="idm139913064912240"></a><h4>Example</h4><pre class="screen">
# ctdb check_srvids 1 2 3 14765
Server id 0:1 does not exist
Server id 0:2 does not exist
Server id 0:3 does not exist
Server id 0:14765 exists
</pre></div></div></div><div class="refsect1"><a name="idm139913064910304"></a><h2>SEE ALSO</h2><p>
<span class="citerefentry"><span class="refentrytitle">ctdbd</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">onnode</span>(1)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdb</span>(7)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdb-statistics</span>(7)</span>,
<span class="citerefentry"><span class="refentrytitle">ctdb-tunables</span>(7)</span>,
<a class="ulink" href="http://ctdb.samba.org/" target="_top">http://ctdb.samba.org/</a>
</p></div></div></body></html>
|
