1 %define initdir %{_sysconfdir}/init.d
5 Packager: Samba Team <samba@samba.org>
9 License: GNU GPL version 3
10 Group: System Environment/Daemons
11 URL: http://ctdb.samba.org/
13 Source: ctdb-%{version}.tar.gz
16 Requires: coreutils, sed, gawk, iptables, iproute, procps, ethtool, sudo
17 # Commands - package name might vary
18 Requires: /usr/bin/killall, /bin/kill, /bin/netstat
22 Provides: ctdb = %{version}
25 BuildRoot: %{_tmppath}/%{name}-%{version}-root
27 # Allow build with system libraries
28 # To enable, run rpmbuild with,
29 # "--with system_talloc"
31 # "--with system_tevent"
32 %define with_included_talloc %{?_with_system_talloc: 0} %{?!_with_system_talloc: 1}
33 %define with_included_tdb %{?_with_system_tdb: 0} %{?!_with_system_tdb: 1}
34 %define with_included_tevent %{?_with_system_tevent: 0} %{?!_with_system_tevent: 1}
36 # Required minimum library versions when building with system libraries
37 %define libtalloc_version 2.0.8
38 %define libtdb_version 1.2.11
39 %define libtevent_version 0.9.18
41 %if ! %with_included_talloc
42 BuildRequires: libtalloc-devel >= %{libtalloc_version}
43 Requires: libtalloc >= %{libtalloc_version}
45 %if ! %with_included_tdb
46 BuildRequires: libtdb-devel >= %{libtdb_version}
47 Requires: libtdb >= %{libtdb_version}
49 %if ! %with_included_tevent
50 BuildRequires: libtevent-devel >= %{libtevent_version}
51 Requires: libtevent >= %{libtevent_version}
54 # To build the ctdb-pcp-pmda package, run rpmbuild with "--with pmda"
55 %define with_pcp_pmda %{?_with_pmda: 1} %{?!_with_pmda: 0}
57 BuildRequires: pcp-libs-devel
61 ctdb is the clustered database used by samba
63 #######################################################################
69 # setup the init script and sysconfig file
70 %setup -T -D -n ctdb-%{version} -q
75 if ccache -h >/dev/null 2>&1 ; then
83 ## always run autogen.sh
86 CFLAGS="$RPM_OPT_FLAGS $EXTRA -D_GNU_SOURCE" ./configure \
87 %if %with_included_talloc
88 --with-included-talloc \
90 %if %with_included_tdb
93 %if %with_included_tevent
94 --with-included-tevent \
100 --sysconfdir=%{_sysconfdir} \
101 --mandir=%{_mandir} \
102 --localstatedir="/var"
104 make docdir=%{_docdir} showflags
105 make docdir=%{_docdir}
108 # Clean up in case there is trash left from a previous build
109 rm -rf $RPM_BUILD_ROOT
111 # Create the target build directory hierarchy
112 mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/sysconfig
113 mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/init.d
114 mkdir -p $RPM_BUILD_ROOT%{_sysconfdir}/sudoers.d
116 make DESTDIR=$RPM_BUILD_ROOT docdir=%{_docdir} install install_tests
118 install -m644 config/ctdb.sysconfig $RPM_BUILD_ROOT%{_sysconfdir}/sysconfig/ctdb
119 install -m755 config/ctdb.init $RPM_BUILD_ROOT%{initdir}/ctdb
121 cp config/events.d/README README.eventscripts
122 cp config/notify.d.README README.notify.d
124 # Remove "*.old" files
125 find $RPM_BUILD_ROOT -name "*.old" -exec rm -f {} \;
128 rm -rf $RPM_BUILD_ROOT
131 #######################################################################
133 #######################################################################
136 %defattr(-,root,root)
138 %config(noreplace) %{_sysconfdir}/sysconfig/ctdb
139 %config(noreplace) %{_sysconfdir}/ctdb/notify.sh
140 %config(noreplace) %{_sysconfdir}/ctdb/debug-hung-script.sh
141 %config(noreplace) %{_sysconfdir}/ctdb/ctdb-crash-cleanup.sh
142 %config(noreplace) %{_sysconfdir}/ctdb/gcore_trace.sh
143 %attr(755,root,root) %{initdir}/ctdb
144 %attr(755,root,root) %{_sysconfdir}/ctdb/notify.d
146 %doc README COPYING NEWS
147 %doc README.eventscripts README.notify.d
148 %doc doc/recovery-process.txt
150 %{_sysconfdir}/sudoers.d/ctdb
151 %{_sysconfdir}/ctdb/functions
152 %{_sysconfdir}/ctdb/events.d/00.ctdb
153 %{_sysconfdir}/ctdb/events.d/01.reclock
154 %{_sysconfdir}/ctdb/events.d/10.interface
155 %{_sysconfdir}/ctdb/events.d/13.per_ip_routing
156 %{_sysconfdir}/ctdb/events.d/11.natgw
157 %{_sysconfdir}/ctdb/events.d/11.routing
158 %{_sysconfdir}/ctdb/events.d/20.multipathd
159 %{_sysconfdir}/ctdb/events.d/31.clamd
160 %{_sysconfdir}/ctdb/events.d/40.fs_use
161 %{_sysconfdir}/ctdb/events.d/40.vsftpd
162 %{_sysconfdir}/ctdb/events.d/41.httpd
163 %{_sysconfdir}/ctdb/events.d/49.winbind
164 %{_sysconfdir}/ctdb/events.d/50.samba
165 %{_sysconfdir}/ctdb/events.d/60.nfs
166 %{_sysconfdir}/ctdb/events.d/60.ganesha
167 %{_sysconfdir}/ctdb/events.d/62.cnfs
168 %{_sysconfdir}/ctdb/events.d/70.iscsi
169 %{_sysconfdir}/ctdb/events.d/91.lvs
170 %config(noreplace) %{_sysconfdir}/ctdb/nfs-rpc-checks.d/10.statd.check
171 %config(noreplace) %{_sysconfdir}/ctdb/nfs-rpc-checks.d/20.nfsd.check
172 %config(noreplace) %{_sysconfdir}/ctdb/nfs-rpc-checks.d/30.lockd.check
173 %config(noreplace) %{_sysconfdir}/ctdb/nfs-rpc-checks.d/40.mountd.check
174 %config(noreplace) %{_sysconfdir}/ctdb/nfs-rpc-checks.d/50.rquotad.check
175 %{_sysconfdir}/ctdb/statd-callout
178 %{_bindir}/ctdb_lock_helper
182 %{_bindir}/ctdb_diagnostics
184 %{_mandir}/man1/ctdb.1.gz
185 %{_mandir}/man1/ctdbd.1.gz
186 %{_mandir}/man1/onnode.1.gz
187 %{_mandir}/man1/ltdbtool.1.gz
188 %{_mandir}/man1/ping_pong.1.gz
189 %{_libdir}/pkgconfig/ctdb.pc
193 Summary: CTDB development libraries
194 Group: Development/Libraries
197 development libraries for ctdb
200 %defattr(-,root,root)
201 %{_includedir}/ctdb.h
202 %{_includedir}/ctdb_client.h
203 %{_includedir}/ctdb_protocol.h
204 %{_includedir}/ctdb_private.h
205 %{_includedir}/ctdb_typesafe_cb.h
209 Summary: CTDB test suite
210 Group: Development/Tools
211 Requires: ctdb = %{version}
218 %defattr(-,root,root)
219 %dir %{_datadir}/%{name}-tests
220 %{_datadir}/%{name}-tests/*
221 %dir %{_libdir}/%{name}-tests
222 %{_libdir}/%{name}-tests/*
223 %{_bindir}/ctdb_run_tests
224 %{_bindir}/ctdb_run_cluster_tests
230 Summary: CTDB PCP pmda support
231 Group: Development/Tools
232 Requires: ctdb = %{version}
235 %description pcp-pmda
236 Performance Co-Pilot (PCP) support for CTDB
239 %dir /var/lib/pcp/pmdas/ctdb
240 /var/lib/pcp/pmdas/ctdb/*
247 * Thu Mar 1 2012 : Version 1.13
248 - This is the new stable branch for modern features for ctdb.
249 Main new features are performance/scaling improvements for
250 concurrnet fetch and fetch_lock operations.
251 * Tue Nov 8 2011 : Version 1.12
252 - Add new tunable : AllowClientDBAttach that can be used to stop
253 client db access during maintenance operations
254 - Updated logging for interfaces that are missing or dont exist but are
255 configured to be used.
256 - Add timeout argument to ctdb_cmdline_client
258 - Initial support for 'readonly' delegations for ctdb databases
259 This will when finished greatly improve performance for contended hot
260 records that are used for just read-access.
261 - New 'ctdb cattdb' command
262 - Massive updates to tests and eventscripts
263 - LCP2 ip allocation algorithm
264 - Record Fetch collapse. Collapse multiple fetch-lock requests from cients
265 to a single network fetch and defer other concurrent requests until the
266 initial fetch completes, and then service the deferred calls locally.
267 This will greatly improve performance for contended hot records
268 where clients request write-locks.
269 * Thu Sep 1 2011 : Version 1.11
271 * Tue May 25 2010 : Version 1.10
273 * Tue May 25 2010 : Version 1.9
275 * Wed Mar 25 2010 : Version 1.0.114
276 - Lots of changes from Metze
277 * Wed Jan 13 2010 : Version 1.0.113
278 - Incorrect use of dup2() could cause ctdb to spin eating 100% cpu.
279 * Tue Jan 12 2010 : Version 1.0.112
280 - Revert the use of wbinfo --ping-dc as it is proving too unreliable.
281 - Minor testsuite changes.
282 * Fri Dec 18 2009 : Version 1.0.111
283 - Fix a logging bug when an eventscript is aborted that could cause a crash.
284 - Add back cb_status that was lost in a previous commit.
285 * Fri Dec 18 2009 : Version 1.0.110
286 - Metxe: fix for filedescriptor leak in the new eventscript code.
287 - Rusty: fix for a crash bug in the eventscript code.
288 * Thu Dec 17 2009 : Version 1.0.109
289 - Massive eventscript updates. (bz58828)
290 - Nice the daemon instead of using realtime scheduler, also use mlockall() to
291 reduce the risk of blockign due to paging.
292 - Workarounds for valgrind when forking once for each script. Valgrind consumes
293 massive cpu when terminating the scripts on virtual systems.
294 - Sync the tdb library with upstream, and use the new TDB_DISALLOW_NESTING flag.
295 - Add new command "ctdb dumpdbbackup"
296 - Start using the new tdb check framework to validate tdb files upon startup.
297 - A new framework where we can control health for individual tdb databases.
298 - Fix a crash bug in the logging code.
299 - New transaction code for persistent databases.
300 - Various other smaller fixes.
301 * Mon Dec 7 2009 : Version 1.0.108
302 - Transaction updates from Michael Adam.
303 - Use the new wbinfo --ping-dc instead of -p in the eventscript for samba
304 the check if winbindd is ok.
305 - Add a better "process-exist" for samba so it will automatically
306 reap smbd's on stopped and banned nodes to reclaim subrecords.
307 This will be done a bit differently in the next release.
308 - Use a statically allocated buffer for the 'first-time' capture buffer
309 to reduce the pressure on malloc/free.
310 * Wed Dec 2 2009 : Version 1.0.107
311 - fix for rusty to solve a double-free that can happen when there are
312 multiple packets queued and the connection is destroyed before
313 all packets are processed.
314 * Tue Dec 1 2009 : Version 1.0.106
315 - Buildscript changes from Michael Adam
316 - Dont do a full recovery when there is a mismatch detected for ip addresses,
317 just do a less disruptive ip-reallocation
318 - When starting ctdbd, wait until all initial recoveries have finished
319 before we issue the "startup" event.
320 So dont start services or monitoring until the cluster has
322 - Major eventscript overhaul by Ronnie, Rusty and Martins and fixes of a few
324 * Thu Nov 19 2009 : Version 1.0.105
325 - Fix a bug where we could SEGV if multiple concurrent "ctdb eventscript ..."
326 are used and some of them block.
327 - Monitor the daemon from the syslog child process so we shutdown cleanly when
328 the main daemon terminates.
329 - Add a 500k line ringbuffer in memory where all log messages are stored.
330 - Add a "ctdb getlog <level>" command to pull log messages from the in memory
332 - From martin : fixes to cifs and nfs autotests
333 - from michael a : fix a bashism in 11.natgw
334 * Fri Nov 6 2009 : Version 1.0.104
335 - Suggestion from Metze, we can now use killtcp to kill local connections
336 for nfs so change the killtcp script to kill both directions of an NFS
338 We used to deliberately only kill one direction in these cases due to
340 - Suggestion from christian Ambach, when using natgw, try to avoid using a
341 UNHEALTHY node as the natgw master.
342 - From Michael Adam: Fix a SEGV bug in the recent change to the eventscripts
343 to allow the timeout to apply to each individual script.
344 - fix a talloc bug in teh vacuuming code that produced nasty valgrind
346 - From Rusty: Set up ulimit to create core files for ctdb, and spawned
347 processes by default. This is useful for debugging and testing but can be
348 disabled by setting CTDB_SUPRESS_COREFILE=yes in the sysconfig file.
349 - Remove the wbinfo -t check from the startup check that winbindd is happy.
350 - Enhance the test for bond devices so we also check if the sysadmin have
351 disabled all slave devices using "ifdown".
352 * Tue Nov 3 2009 : Version 1.0.103
353 - Dont use vacuuming on persistent databases
354 - Michael A : transaction updates to persistent databases
355 - Dont activate service automatically when installing the RPM. Leave this to the admin.
356 - Create a child process to send all log messages to, to prevent a hung/slow syslogd
357 from blocking the main daemon. In this case, discard log messages instead and let the child
359 - Michael A: updates to log messages
360 * Thu Oct 29 2009 : Version 1.0.102
361 - Wolfgang: fix for the vacuuming code
362 - Wolfgang: stronger tests for persistent database filename tests
363 - Improve the log message when we refuse to startup since wbinfo -t fails
364 to make it easier to spot in the log.
365 - Update the uptime command output and the man page to indicate that
366 "time since last ..." if from either the last recovery OR the last failover
367 - Michael A: transaction updates
368 * Wed Oct 28 2009 : Version 1.0.101
369 - create a separate context for non-monitoring events so they dont interfere with the monitor event
370 - make sure to return status 0 in teh callback when we abort an event
371 * Wed Oct 28 2009 : Version 1.0.100
372 - Change eventscript handling to allow EventScriptTimeout for each individual script instead of for all scripts as a whole.
373 - Enhanced logging from the eventscripts, log the name and the duration for each script as it finishes.
374 - Add a check to use wbinfo -t for the startup event of samba
375 - TEMP: allow clients to attach to databases even when teh node is in recovery mode
376 - dont run the monitor event as frequently after an event has failed
377 - DEBUG: in the eventloops, check the local time and warn if the time changes backward or rapidly forward
378 - From Metze, fix a bug where recovery master becoming unhealthy did not trigger an ip failover.
379 - Disable the multipath script by default
380 - Automatically re-activate the reclock checking if the reclock file is specified at runtime. Update manpage to reflect this.
381 - Add a mechanism where samba can register a SRVID and if samba unexpectedly disconnects, a message will be broadcasted to all other samba daemons.
382 - Log the pstree on hung scripts to a file in /tmp isntead of /var/log/messages
383 - change ban count before unhealthy/banned to 10
384 * Thu Oct 22 2009 : Version 1.0.99
385 - Fix a SEGV in the new db priority code.
386 - From Wolfgang : eliminate a ctdb_fatal() if there is a dmaster violation detected.
387 - During testing we often add/delete eventscripts at runtime. This could cause an eventscript to fail and mark the node unhealthy if an eventscript was deleted while we were listing the names. Handle the errorcode and make sure the node does not becomne unhealthy in this case.
388 - Lower the debuglevel for the messages when ctdb creates a filedescruiptor so we dont spam the logs with these messages.
389 - Dont have the RPM automatically restart ctdb
390 - Volker : add a missing transaction_cancel() in the handling of persistent databases
391 - Treat interfaces with the anme ethX* as bond devices in 10.interfaces so we do the correct test for if they are up or not.
392 * Tue Oct 20 2009 : Version 1.0.98
393 - Fix for the vacuuming database from Wolfgang M
394 - Create a directory where the test framework can put temporary overrides
395 to variables and functions.
396 - Wait a lot longer before shutting down the node when the reclock file
397 is incorrectly configured, and log where it is configured.
398 - Try to avoid running the "monitor" event when databases are frozen.
399 - Add logging for every time we create a filedescriptor so we can trap
401 * Thu Oct 14 2009 : Version 1.0.97
402 - From martins : update onnode.
403 Update onnode to allow specifying an alternative nodes file from
404 the command line and also to be able to specify hostnames on the
406 onnode host1,host2,...
407 * Tue Oct 13 2009 : Version 1.0.96
408 - Add more debugging output when eventscripts have trouble. Print a
409 "pstree -p" to the log when scripts have hung.
410 - Update the initscript, only print the "No reclock file used" warning
411 when we do "service ctdb start", dont also print them for all other
413 - When changing between unhealthy/healthy state, push a request to the
414 recovery master to perform an ip reallocation instead of waiting for the
415 recovery master to pull and check the state change.
416 - Fix a bug in the new db-priority handling where a pre-.95 recovery master
417 could no longer lock the databases on a post-.95 daemon.
418 - Always create the nfs state directories during the "monitor" event.
419 This makes it easier to configure and enable nfs at runtime.
420 - From Volker, forward-port a simper deadlock avoiding patch from the 1.0.82
421 branch. This is a simpler versionof the "db priority lock order" patch
422 that went into 1.0.95, and will be kept for a few versions until samba
423 has been updated to use the functionality from 1.0.95.
424 * Mon Oct 12 2009 : Version 1.0.95
425 - Add database priorities. Allow samba to set the priority of databases
426 and lock the databases in priority order during recovery
427 to avoid a deadlock when samba locks one database then blocks indefinitely
428 while waiting for the second databaso to become locked.
429 - Be aggressive and ban nodes where the recovery transaction start call
431 * Thu Oct 10 2009 : Version 1.0.94
432 - Be very aggressive and quickly ban nodes that can not freeze their databases
433 * Tue Oct 8 2009 : Version 1.0.93
434 - When adding an ip, make sure to update this assignment on all nodes
435 so it wont show up as -1 on other nodes.
436 - When adding an ip and immediately deleting it, it was possible that
437 the daemon would crash accessing already freed memory.
438 Readjust the memory hierarchy so the destructors are called in the right order.
439 - Add a handshake to the recovery daemon to eliminate some rare cases where
440 addip/delip might cause a recovery to occur.
441 - updated onnode documenation from Martin S
442 - Updates to the natgw eventscript to allow disabling natgw at runtime
443 * Fri Oct 2 2009 : Version 1.0.92
444 - Test updates and merge from martin
445 - Add notification for "startup"
446 - Add documentation for notification
447 - from martin, a fix for restarting vsftpd in the eventscript
448 * Tue Sep 29 2009 : Version 1.0.91
449 - New vacuum and repack design from Wolgang Mueller.
450 - Add a new eventscript 01.reclock that will first mark a node unhealthy and later ban the node if the reclock file can not be accessed.
451 - Add machinereadable output to the ctdb getreclock command
452 - merge transaction updates from Michael Adam
453 - In the new banning code, reset the culprit count to 0 for all nodes that could successfully compelte a full recovery.
454 - dont mark the recovery master as a ban culprit because a node in the cluster needs a recovery. this happens naturally when using ctdb recover command so dont make this cause a node to be banned.
455 * Sat Sep 12 2009 : Version 1.0.90
456 - Be more forgiving for eventscripts that hang during startup
457 - Fix for a banning bug in the new banning logic
458 * Thu Sep 3 2009 : Version 1.0.89
459 - Make it possible to manage winbind independently of samba.
460 - Add new prototype banning code
461 - Overwrite the vsftpd state file instead of appending. This eliminates
462 annoying errors in the log.
463 - Redirect some iptables commands to dev null
464 - From Michael A, explicitely set the broadcast when we takeover a public ip
465 - Remove a reclock file check we no longer need
466 - Skip any persistent database files ending in .bak
467 * Mon Aug 17 2009 : Version 1.0.88
468 - Add a new state for eventscripts : DISABLED.
469 Add two new commands "ctdb enablescript/disablescript" to enable/disable
470 eventscripts at runtime.
471 - Bugfixes for TDB from rusty.
472 - Merge/Port changes from upstream TDB library by rusty.
473 - Additional new tests from MartinS. Tests for stop/continue.
474 - Initial patch to rework vacuuming/repacking process from Wolfgang Mueller.
475 - Updates from Michael Adam for persistent writes.
476 - Updates from MartinS to handle the new STOPPED bit in the test framework.
477 - Make it possible to enable/disable the RECMASTER and LMASTER roles
478 at runtime. Add two new commands
479 "ctdb setlmasterrole/setrecmasterrole on/off"
480 - Make it possible to enable/disable the natgw feature at runtime. Add
481 the command "ctdb setnatgwstate on/off"
482 * Fri Jul 17 2009 : Version 1.0.87
483 - Add a new event "stopped" that is called when a node is stopped.
484 - Documentation of the STOPPED flag and the stop/continue commands
485 - Make it possible to start a node in STOPPED mode.
486 - Add a new node flag : STOPPED and commands "ctdb stop" "ctdb continue"
487 These commands are similar to "diasble/enable" but will also remove the node from the vnnmap, while disable only fails all ip addresses over.
488 - tests for NFS , CIFS by martins
489 - major updates to the init script by martins
490 - Send gratious arps with a 1.1 second stride instead of a 1 second stride to workaround interesting "features" of common linux stacks.
491 - Various test enhancements from martins:
492 - additional other tests
493 - add tests for grat arp generation, ping during failover, ssh and failover
494 - New/updated tcp tickle tests and supprot functions
495 - provide better debugging when a test fails
496 - make ctdbd restarts more reliable in the tests
497 - update the "wait bar" to make the wait progress in tests more obvious
499 - when dispatching a message to a handler, make the message a real talloc object so that we can reparent the object in the tallic hierarchy.
500 - document the ipreallocate command
501 - Updates to enable/disable to use the ipreallocate command to block until the following ipreallocation has completed.
502 - Update the main daemon and the tools to allow debug level to be a string instead of an integer.
503 - Update the sysconfig file to show using string literals instead of numeric values for the debuglevels used.
504 - If no debuglevel is specific, make "ctdb setdebug" show the available options.
505 - When trying to allocate network packets, add explicit checks if the network transport has been shutdown before trying and failing, to make log messages easier to read. Add this extra check and logging to every plave packets are allocated.
506 * Tue Jun 30 2009 : Version 1.0.86
507 - Do not access the reclock at all if VerifyRecoveryLock is zero, not even try to probe it.
508 - Allow setting the reclock file as "", which means that no reclock file at all should be used.
509 - Document that a reclock file is no longer required, but that it is dangerous.
510 - Add a control that can be used to set/clear/change the reclock file in the daemon during runtime.
511 - Update the recovery daemon to poll whether a reclock file should be sued and if so which file at runtime in each monitoring cycle.
512 - Automatically disable VerifyRecoveryLock everytime a user changes the location of the reclock file.
513 - do not allow the VerifyRecoveryLock to be set using ctdb setvar if there is no recovery lock file specified.
514 - Add two commands "ctdb getreclock" and "ctdb setreclock" to modify the reclock file.
515 * Tue Jun 23 2009 : Version 1.0.85
516 - From William Jojo : Dont use getopt on AIX
517 - Make it possible to use "ctdb listnodes" also when the daemon is not running
518 - Provide machinereadable output to "ctdb listnodes"
519 - Dont list DELETED nodes in the ctdb listnodes output
520 - Try to avoid causing a recovery for the average case when adding/deleting/moving an ip
521 - When banning a node, drop the IPs on that node only and not all nodes.
522 - Add tests for NFS and CIFS tickles
523 - Rename 99.routing to 11.routing so it executes before NFS and LVS scripts
524 - Increase the default timeout before we deem an unresponsive recovery daemon hung and shutdown
525 - Reduce the reclock timout to 5 seconds
526 - Spawn a child process in the recovery daemon ot check the reclock file to
527 avoid blocking the process if the underlying filesystem is unresponsive
528 - fix for filedescriptor leak when a child process timesout
529 - Dont log errors if waitpid() returns -1
530 - Onnode updates by Martins
531 - Test and initscript cleanups from Martin S
532 * Tue Jun 2 2009 : Version 1.0.84
533 - Fix a bug in onnode that could not handle dead nodes
534 * Tue Jun 2 2009 : Version 1.0.83
535 - Document how to remove a ndoe from a running cluster.
536 - Hide all deleted nodes from ctdb output.
537 - Lower the loglevel on some eventscript related items
538 - Dont queue packets to deleted nodes
539 - When building initial vnnmap, ignode any nonexisting nodes
540 - Add a new nodestate : DELETED that is used when deleting a node from an
542 - dont remove the ctdb socket when shutting down. This prevents a race in the
543 initscripts when restarting ctdb quickly after stopping it.
544 - TDB nesting reworked.
545 - Remove obsolete ipmux
546 - From Flavio Carmo Junior: Add eventscript and documentation for ClamAV antivirus engine
547 - From Sumit Bose: fix the regex in the test to handle the new ctdb
548 statistics output that was recently added.
549 - change the socket type we use for grauitious arps from the obsolete
550 AF_INET/SOCK_PACKET to instead use PF_PACKET/SOCK_RAW.
551 - Check return codes for some functions, from Sumit Bose, based on codereview by Jim Meyering.
552 - Sumit Bose: Remove structure memeber node_list_file that is no longer used.
553 - Sumit Bose: fix configure warning for netfilter.h
554 - Updates to the webpages by Volker.
555 - Remove error messages about missing /var/log/log.ctdb file from ctdb_diagnostics.sh from christian Ambach
556 - Additional error logs if hte eventscript switching from dameon to client mode fails.
557 - track how long it takes for ctdbd and the recovery daemon to perform the rec-lock fcntl() lock attemt and show this in the ctdb statistics output.
558 * Thu May 14 2009 : Version 1.0.82
559 - Update the "ctdb lvsmaster" command to return -1 on error.
560 - Add a -Y flag to "ctdb lvsmaster"
561 - RHEL5 apache leaks semaphores when crashing. Add semaphore cleanup to the
562 41.httpd eventscript and try to restart apache when it has crashed.
563 - Fixes to some tests
564 - Add a -o option to "onnode" which will redirect all stdout to a file for
566 - Add a natgw and a lvs node specifier to onnode so that we can use
568 - Assign the natgw address to lo instead of the private network so it can also
569 be used where private and public networks are the same.
570 - Add GPL boilerplates to two missing scripts.
571 - Change the natgw prefix NATGW_ to CTDB_NATGW_
572 * Fri May 8 2009 : Version 1.0.81
573 - use smbstatus -np instead of smbstatus -n in the 50.samba eventscript
574 since this avoids performing an expensive traverse on the locking and brlock
576 - make ctdb automatically terminate all traverse child processes clusterwide
577 associated to a client application that terminates before the traversal is
579 - From Sumit Bose : fixes to AC_INIT handling.
580 - From Michael Adam, add Tridge's "ping_pong" tool the the ctdb distro since
581 this is very useful for testing the backend filesystem.
582 - From Sumit bose, add support for additional 64 bit platforms.
583 - Add a link from the webpage to Michael Adams SambaXP paper on CTDB.
584 * Fri May 1 2009 : Version 1.0.80
585 - change init shutdown level to 01 for ctdb so it stops before any of the other services
586 - if we can not pull a database from a remote node during recovery, mark that node as a culprit so it becomes banned
587 - increase the loglevel when we volunteer to drop all ip addresses after beeing in recovery mode for too long. Make this timeout tuneable with "RecoveryDropAllIPs" and have it default to 60 seconds
588 - Add a new flag TDB_NO_NESTING to the tdb layer to prevent nested transactions which ctdb does not use and does not expect. Have ctdb set this flag to prevent nested transactions from occuring.
589 - dont unconditionally kill off ctdb and restrat it on "service ctdb start". Fail "service ctdb start" with an error if ctdb is already running.
590 - Add a new tunable "VerifyRecoveryLock" that can be set to 0 to prevent the main ctdb daemon to verify that the recovery master has locked the reclock file correctly before allowing it to set the recovery mode to active.
591 - fix a cosmetic bug with ctdb statistics where certain counters could become negative.
592 * Wed Apr 8 2009 : Version 1.0.79
593 - From Mathieu Parent: add a ctdb pkgconfig file
595 - add a funciton remove_ip to safely remove an ip from an interface, taking care to workaround an issue with linux alias interfaces.
596 - Update the natgw eventscript to use the safe remove_ip() function
597 - fix a bug in the eventscript child process that would cause the socket to be removed.
598 - dont verify nodemap on banned nodes during cluster monitoring
599 - Update the dodgy SeqnumInterval to have ms resolution
600 * Tue Mar 31 2009 : Version 1.0.78
601 - Add a notify mechanism so we can send snmptraps/email to external management systems when the node becomes unhealthy
602 - include 11.natgw eventscript in thew install so that the NATGW feature works
603 * Tue Mar 31 2009 : Version 1.0.77
604 - Update the 99.routing eventscript to also try to add the routes (back) during a releaseip event. Similar to the reasons why we must add addresses back during releaseip in 10.interfaces
605 * Wed Mar 24 2009 : Version 1.0.76
606 - Add a debugging command "xpnn" which can print the pnn of the node even when ctdbd is not running.
607 - Redo the NATGW implementation to allow multiple disjoing NATGW groups in the same cluster.
608 * Tue Mar 24 2009 : Version 1.0.75
609 - Various updates to LVS
610 - Fix a bug in the killtcp control where we did not set the port correctly
611 - add a new "ctdb scriptstatus" command that shows the status of the eventrscripts.
612 * Mon Mar 16 2009 : Version 1.0.74
613 - Fixes to AIX from C Cowan.
614 - Fixes to ctdb_diagnostics so we collect correct GPFS data
615 - Fixes to the net conf list command in ctdb_diagnostics
616 - Check the static-routes file IFF it exists in ctdb_diagnostics
617 * Wed Mar 4 2009 : Version 1.0.73
618 - Add possibility to disable the check of shares for NFS and Samba
619 - From Sumit Bose, fix dependencies so make -j works
620 * Wed Feb 18 2009 : Version 1.0.72
621 - Updates to test scripts by martin s
622 - Adding a COPYING file
623 - Use netstat to check for services and ports and fallback to netcat
624 only if netstat is unavailable.
625 * Mon Feb 2 2009 : Version 1.0.71
626 - Additional ipv6 fixes from Michael Adams
627 * Fri Jan 16 2009 : Version 1.0.70
628 - IPv6 support is completed. this is backward compatible with ipv4-only
629 systems. To use IPv6 with samba and ctdb you need current GIT of samba 3.3
630 or michael adams samba-ctdeb branch.
631 - Many enhancements to the build system and scripts to make it more SUSE
632 friendly by Michael Adams.
633 - Change of how the naming of the package is structured. We are now
634 using "1.0.70" as a release and "-1" as the revision instead of as
635 previously using "1.0" as release and ".70" as the revision.
637 * Thu Dec 18 2008 : Version 1.0.69
638 - Various fixes to scripts by M Adam
639 - Dont call ctdb_fatal() when the transport is down during shutdown
640 * Fri Dec 12 2008 : Version 1.0.68
641 - Fixes for monitoring of interfaces status from Michael Adam.
642 - Use -q instead of >/dev/null for grep to enhance readability of the
643 scripts from Michael Adam.
644 - Update to the "ctdb recover" command. This command now block until the
645 has completed. This makes it much easier to use in scripts and avoids
646 the common workaround :
648 ... loop while waiting for recovery completes ...
650 - Add a CTDB_TIMEOUT variable. If set, this variable provides an automatic
651 timeout for "ctdb <command>", similar to using -T <timeout>
652 - Set a unique errorcode for "ctdb <command>" when it terminates due to a
653 timeout so that scripts can distinguish between a hung command and what was
655 - Update "ctdb ban/unban" so that if the cluster is in recovery these commands
656 blocks and waits until after recovery is complete before the perform the
657 ban/unban operation. This is necessary since the recovery process can cause
658 nodes to become automatically unbanned.
659 - Update "ctdb ban/unban" to block until the recovery that will follow shortly
660 after this command has completed.
661 This makes it much easier to use in scripts and avoids the common
664 ... loop while waiting for recovery completes ...
666 - Bugfix for the new flags handling in 1.0.67. Abort and restart monitoring
667 if we failed to get proper nodemaps from a remote node instead of
668 dereferencing a null pointer.
669 - If ctdbd was explicitely started with the '--socket' argument, make
670 ctdbd automatically set CTDB_SOCKET to the specified argument.
671 This ensures that eventscripts spawned by the ctdb daemon will default to
672 using the same socket and talk to the correct daemon.
673 This primarily affects running multiple daemons on the same host and where
674 you want each instance of ctdb daemons have their eventscripts talk to the
676 - Update "ctdb ping" to return an error code if the ping fail so that it
677 can be used in scripts.
678 - Update to how to synchronize management of node flags across the cluster.
679 * Thu Dec 3 2008 : Version 1.0.67
680 - Add a document describing the recovery process.
681 - Fix a bug in "ctdb setdebug" where it would refuse to set a negative
683 - Print the list of literals for debug names if an invalid one was given
685 - Redesign how "ctdb reloadnodes" works and reduce the amont of tcp teardowns
686 used during this event.
687 - Make it possible to delete a public ip from all nodes at once using
689 * Mon Nov 24 2008 : Version 1.0.66
690 - Allow to change the recmaster even when we are not frozen.
691 - Remove two redundant SAMBA_CHECK variables from the sysconf example
692 - After a node failure it can take very long before some lock operations
693 ctdb needs to perform are allowed/works with gpfs again. Workaround this
694 by treating a hang/timeout as success.
695 - Dont override CTDB_BASE is fet in the shell already
696 - Always send keepalive packets regardless of whether the link is idle or not.
697 - Rewrite the disable/enable flag update logic to prevent a race between
698 "ctdb disable/enable" and the recovery daemon when updating the flags to
700 * Thu Nov 13 2008 : Version 1.0.65
701 - Update the sysconfig example: The default debug level is 2 (NOTICE) and not
703 - Add support for a CTDB_SOCKET environment variable for the ctdb command
704 line tool. If set, this overrides the default socket the ctdb tool will
706 - Add logging of high latency operations.
707 * Mon Oct 22 2008 : Version 1.0.64
708 - Add a context and a timed event so that once we have been in recovery for
709 too long we drop all public addresses.
710 * Mon Oct 20 2008 : Version 1.0.63
711 - Remove logging of "periodic cleanup ..." in 50.samba
712 - When we reload a nodes file, we must detect this and reload the file also
713 in the recovery daemon before we try to dereference somethoung beyond the end
715 * Thu Oct 16 2008 : Version 1.0.62
716 - Allow multiple eventscritps using the same prefix number.
717 It is undefined which order scripts with the same prefix will execute in.
718 * Wed Oct 15 2008 : Version 1.0.61
719 - Use "route add -net" instead of "ip route add" when adding routes in 99.routing
720 - lower the loglevel os several debug statements
721 - check the status returned from ctdb_ctrl_get_tickles() before we try to print them out to the screen.
722 - install a new eventscript 20.multipathd whoich can be used to monitor that multipath devices are healthy
723 * Wed Oct 15 2008 : Version 1.0.60
724 - Verify that nodes we try to ban/unban are reachable and print an error othervise.
725 - Update the client and server sides of TAKEIP/RELEASEIP/GETPUBLICIPS and GETNODEMAP to fall back to the old style ipv4-only controls if the new ipv4/ipv6 controls fail. This allows an ipv4/v6 enabled ctdb daemon to interoperate with earlier ipv4-only versions of the daemons.
726 - From Mathieu Parent : log debian systems log the package versions in ctdb diagnostics
727 - From Mathieu Parent : specify logdir location for debian (this patch was later reversed)
728 - From Michael Adams : allow # comments in nodes/public_addresses files
729 * Tue Oct 7 2008 : Version 1.0.59
730 - Updated "reloadnodes" logic. Instead of bouncing the entire tcp layer it is sufficient to just close and reopen all outgoing tcp connections.
731 - New eventscript 99.routing which can be used to re-attach routes to public interfaces after a takeip event. (routes may be deleted by the kernel when we release an ip)
732 - IDR tree fix from Jim Houston
733 - Better handling of critical events if the local clock is suddenly changed forward by a lot.
734 - Fix three slow memory leaks in the recovery daemon
735 - New ctdb command : ctdb recmaster which prints the pnn of the recmaster
736 - Onnode enhancements from Martin S : "healthy" and "connected" are now possible nodespecifiers
737 - From Martin S : doc fixes
738 - lowering some debug levels for some nonvital informational messages
739 - Make the daemon daemon monitoring stronger and allow ctdbd to detect a hung
741 - From C Cowan : patches to compile ipv6 under AIX
742 - zero out some structs to keep valgrind happy
743 * Wed Aug 27 2008 : Version 1.0.58
744 - revert the name change tcp_tcp_client back to tcp_control_tcp so
746 - Updates to the init script from Abhijith Das <adas@redhat.com>
747 * Mon Aug 25 2008 : Version 1.0.57
748 - initial support for IPv6
749 * Mon Aug 11 2008 : Version 1.0.56
750 - fix a memory leak in the recovery daemon.
751 * Mon Aug 11 2008 : Version 1.0.55
752 - Fix the releaseip message we seond to samba.
753 * Fri Aug 8 2008 : Version 1.0.54
754 - fix a looping error in the transaction code
755 - provide a more detailed error code for persistent store errors
756 so clients can make more intelligent choices on how to try to recover
757 * Thu Aug 7 2008 : Version 1.0.53
758 - Remove the reclock.pnn file it can cause gpfs to fail to umount
759 - New transaction code
760 * Mon Aug 4 2008 : Version 1.0.52
761 - Send an explicit gratious arp when starting sending the tcp tickles.
762 - When doing failover, issue a killtcp to non-NFS/non-CIFS clients
763 so that they fail quickly. NFS and CIFS already fail and recover
765 - Update the test scripts to handle CTRL-C to kill off the test.
766 * Mon Jul 28 2008 : Version 1.0.51
767 - Strip off the vlan tag from bond devices before we check in /proc
768 if the interface is up or not.
769 - Use testparm in the background in the scripts to allow probing
770 that the shares do exist.
771 - Fix a bug in the logging code to handle multiline entries better
772 - Rename private elements from private to private_data
773 * Fri Jul 18 2008 : Version 1.0.50
774 - Dont assume that just because we can establish a TCP connection
775 that we are actually talking to a functioning ctdb daemon.
776 So dont mark the node as CONNECTED just because the tcp handshake
778 - Dont try to set the recmaster to ourself during elections for those
779 cases we know this will fail. To remove some annoying benign but scary
780 looking entries from the log.
781 - Bugfix for eventsystem for signal handling that could cause a node to
783 * Thu Jul 17 2008 : Version 1.0.49
784 - Update the safe persistent update fix to work with unpatched samba
786 * Thu Jul 17 2008 : Version 1.0.48
787 - Update the spec file.
788 - Do not start new user-triggered eventscripts if we are already
789 inside recovery mode.
790 - Add two new controls to start/cancel a persistent update.
791 A client such as samba can use these to tell ctdbd that it will soon
792 be writing directly to the persistent database tdb file. So if
793 samba is -9ed before it has eitehr done the persistent_store or
794 canceled the operation, ctdb knows that the persistent databases
795 'may' be out of sync and therefore a full blown recovery is called for.
796 - Add two new options :
797 CTDB_SAMBA_SKIP_CONF_CHECK and CTDB_SAMBA_CHECK_PORTS that can be used
798 to override what checks to do when monitoring samba health.
799 We can no longer use the smbstatus, net or testparm commands to check
800 if samba or its config is healthy since these commands may block
801 indefinitely and thus can not be used in scripts.
802 * Fri Jul 11 2008 : Version 1.0.47
803 - Fix a double free bug where if a user striggered (ctdb eventscript)
804 hung and while the timeout handler was being processed a new user
805 triggered eventscript was started we would free state twice.
806 - Rewrite of onnode and associated documentation.
807 * Thu Jul 10 2008 : Version 1.0.46
808 - Document both the LVS:cingle-ip-address and the REMOTE-NODE:wan-accelerator
810 - Add commands "ctdb pnn", "ctdb lvs", "ctdb lvsmaster".
811 - LVS improvements. LVS is the single-ip-address mode for a ctdb cluster.
812 - Fixes to supress rpmlint warnings
814 - Change \s to [[:space:]] in some scripts. Not all RHEL5 packages come
815 with a egrep that handles \s even same version but different arch.
816 - Revert the change to NFS restart. CTDB should NOT attempt to restart
818 - Rewrite of the waitpid() patch to use the eventsystem for handling
820 * Tue Jul 8 2008 : Version 1.0.45
821 - Try to restart the nfs service if it has failed to respond 3 times in a row.
822 - waitpid() can block if the child does not respond promptly to SIGTERM.
823 ignore all SIGCHILD signals by setting SIGCHLD to SIG_DEF.
824 get rid of all calls to waitpid().
825 - make handling of eventscripts hanging more liberal.
826 only consider the script to have failed and making the node unhealthy
827 IF the eventscript terminated wiht an error
828 OR the eventscript hung 5 or more times in a row
829 * Mon Jul 7 2008 : Version 1.0.44
830 - Add a CTDB_VALGRIND option to /etc/sysconfig/ctdb to make it start
831 ctdb under valgrind. Logs go to /var/log/ctdb_valgrind.PID
832 - Add a hack to show the control opcode that caused uninitialized data
833 in the valgrind output by encoding the opcode as the line number.
834 - Initialize structures and allocated memory in various places in
835 ctdb to make it valgrind-clean and remove all valgrind errors/warnings.
836 - If/when we destroy a lockwait child, also make sure we cancel any pending transactions
837 - If a transaction_commit fails, delete/cancel any pending transactions and
838 return an error instead of calling ctdb_fatal()
839 - When running ctdb under valgrind, make sure we run it with --nosetsched and also
840 ensure that we do not use mem-mapped i/o when accessing the tdb's.
841 - zero out ctdb->freeze_handle when we free/destroy a freeze-child.
842 This prevent a heap corruption/ctdb crash bug that could trigger
843 if the freeze child times out.
844 - we dont need to explicitely thaw the databases from the recovery daemon
845 since this is done implicitely when we restore the recovery mode back to normal.
846 - track when we start and stop a recovery. Add the 'time it took to complete the
847 recovery' to the 'ctdb uptime' output.
848 Ensure by tracking the start/stop recovery timestamps that we do not
849 check that the ip allocation is consistend from inside the recovery daemon
850 while a different node (recovery master) is performing a recovery.
851 This prevent a race that could cause a full recovery to trigger if the
852 'ctdb disable/enable' commands took very long.
853 - The freeze child indicates to the master daemon that all databases are locked
854 by writing data to the pipe shared with the master daemon.
855 This write sometimes fail and thus the master daemon never notices that the databases
856 are locked cvausing long timeouts and extra recoveries.
857 Check that the write is successful and try the write again if it failed.
858 - In each node, verify that the recmaster have the right node flags for us
859 and force a push of our flags to the recmaster if wrong.
860 * Tue Jul 1 2008 : Version 1.0.43
861 - Updates and bugfixes to the specfile to keep rpmlint happy
862 - Force a global flags update after each recovery event.
863 - Verify that the recmaster agrees with our node flags and update the
865 - When writing back to the parent from a freeze-child across the pipe,
866 loop over the write in case the write failed with an error othervise
867 the parent will never be notified tha the child has completed the operation.
868 - Automatically thaw all databases when recmaster marks us as being in normal
869 mode instead of recovery mode.
870 * Fri Jun 13 2008 : Version 1.0.42
871 - When event scripts have hung/timedout more than EventScriptBanCount times
872 in a row the node will ban itself.
873 - Many updates to persistent write tests and the test scripts.
874 * Wed May 28 2008 : Version 1.0.41
875 - Reactivate the safe writes to persistent databases and solve the
876 locking issues. Locking issues are solved the only possible way,
877 by using a child process to do the writes. Expensive and slow but... .
878 * Tue May 27 2008 : Version 1.0.40
879 - Read the samba sysconfig file from the 50.samba eventscript
880 - Fix some emmory hierarchical bugs in the persistent write handling
881 * Thu May 22 2008 : Version 1.0.39
882 - Moved a CTDB_MANAGES_NFS, CTDB_MANAGES_ISCSI and CTDB_MANAGES_CSFTPD
883 into /etc/sysconfig/ctdb
884 - Lowered some debug messages to not fill the logfile with entries
885 that normally occur in the default configuration.
886 * Fri May 16 2008 : Version 1.0.38
887 - Add machine readable output support to "ctdb getmonmode"
888 - Lots of tweaks and enhancements if the event scripts are "slow"
889 - Merge from tridge: an attempt to break the chicken-and-egg deadlock that
890 net conf introduces if used from an eventscript.
891 - Enhance tickles so we can tickle an ipv6 connection.
892 - Start adding ipv6 support : create a new container to replace sockaddr_in.
893 - Add a checksum routine for ipv6/tcp
894 - When starting up ctdb, let the init script do a tdbdump on all
895 persistent databases and verify that they are good (i.e. not corrupted).
896 - Try to use "safe transactions" when writing to a persistent database
897 that was opened with the TDB_NOSYNC flag. If we can get the transaction
898 thats great, if we cant we have to write anyway since we cant block here.
899 * Mon May 12 2008 : Version 1.0.37
900 - When we shutdown ctdb we close the transport down before we run the
901 "shutdown" eventscripts. If ctdb decides to send a packet to a remote node
902 after we have shutdown the transport but before we have shutdown ctdbd
903 itself this could lead to a SEGV instead of a clean shutdown. Fix.
904 - When using the "exportfs" command to extract which NFS export directories
905 to monitor, exportfs violates the "principle of least surprise" and
906 sometimes report a single export line as two lines of text output
907 causing the monitoring to fail.
908 * Fri May 9 2008 : Version 1.0.36
909 - fix a memory corruption bug that could cause the recovery daemon to crash.
910 - fix a bug with distributing public ip addresses during recovery.
911 If the node that is the recovery master did NOT use public addresses,
912 then it assumed that no other node in the cluster used them either and
913 thus skipped the entire step of reallocating public addresses.
914 * Wed May 7 2008 : Version 1.0.35
915 - During recovery, when we define the new set of lmasters (vnnmap)
916 only consider those nodes that have the can-be-lmaster capability
917 when we create the vnnmap. unless there are no nodes available which
918 supports this capability in which case we allow the recmaster to
919 become lmaster capable (temporarily).
920 - Extend the async framework so that we can use paralell async calls
921 to controls that return data.
922 - If we do not have the "can be recmaster" capability, make sure we will
923 lose any recmaster elections, unless there are no nodes available that
924 have the capability, in which case we "take/win" the election anyway.
925 - Close and reopen the reclock pnn file at regular intervals.
926 Make it a non-fatal event if we occasionally fail to open/read/write
928 - Monitor that the recovery daemon is still running from the main ctdb
929 daemon and shutdown the main daemon when recovery daemon has terminated.
930 - Add a "ctdb getcapabilities" command to read the capabilities off a node.
931 - Define two new capabilities : can be recmaster and can be lmaster
932 and default both capabilities to YES.
933 - Log denied tcp connection attempts with DEBUG_ERR and not DEBUG_WARNING
934 * Thu Apr 24 2008 : Version 1.0.34
935 - When deleting a public ip from a node, try to migrate the ip to a different
937 - Change catdb to produce output similar to tdbdump
938 - When adding a new public ip address, if this ip does not exist yet in
939 the cluster, then grab the ip on the local node and activate it.
940 - When a node disagrees with the recmaster on WHO is the recmaster, then
941 mark that node as a recovery culprit so it will eventually become
943 - Make ctdb eventscript support the -n all argument.
944 * Thu Apr 10 2008 : Version 1.0.33
945 - Add facilities to include site local adaptations to the eventscript
946 by /etc/ctdb/rc.local which will be read by all eventscripts.
947 - Add a "ctdb version" command.
948 - Secure the domain socket with proper permissions from Chris Cowan
949 - Bugfixes for AIX from Chris Cowan
950 * Wed Apr 02 2008 : Version 1.0.32
951 - Add a control to have a node execute the eventscripts with arbitrary
952 command line arguments.
953 - Add a control "rddumpmemory" that will dump the talloc memory allocations
954 for the recovery daemon.
955 - Decorate the talloc memdump to produce better and easier memory leak
957 - Update the RHEL5 iscsi tgtd scripts to allow one iscsi target for each
959 - Add two new controls "addip/delip" that can be used to add/remove public
960 addresses to a node at runtime. After using these controls a "ctdb recover"
961 ir required to make the changes take.
962 - Fix a couple of slow memory leaks.
963 * Tue Mar 25 2008 : Version 1.0.31
964 - Add back controls to disable/enable monitoring on a node.
965 - Fix a memory leak where we used to attach CALL data to the ctdb structure
966 when performing a local call. Memory which would be lost if the call was
968 - Reduce the loglevel for the log output when someone connects to a non
969 public ip address for samba.
970 - Redo and optimize the vacuuming process to send only one control to each
971 other node containing all records to be vacuumed instead of one
972 control per node per record.
973 * Tue Mar 04 2008 : Version 1.0.30
974 - Update documentation cor new commands and tuneables
975 - Add machinereadable output to the ip,uptime and getdebug commands
976 - Add a moveip command to manually failover/failback public ips
977 - Add NoIPFallback tuneable that prevents ip address failback
978 - Use file locking inside the CFS as alternative to verify when other nodes
979 Are connected/disconnected to be able to recover from split network
980 - Add DisableWhenUnhealthy tunable
981 - Add CTDB_START_AS_DISABLED sysconfig param
982 - Add --start-as-disabled flag to ctdb
983 - Add ability to monitor for OOM condition
984 * Thu Feb 21 2008 : Version 1.0.29
985 - Add a new command to make expansion of an existing cluster easier
986 - Fix bug with references to freed objects in the ctdb structure
987 - Propagate debuglevel changes to the recovery daemon
988 - Merge patches to event scripts from Mathieu Parent :
989 - MP: Simulate "service" on systems which do not provide this tool
990 - MP: Set correct permissions for events.d/README
991 - Add nice helper functions to start/stop nfs from the event scripts
992 * Fri Feb 08 2008 : Version 1.0.28
993 - Fix a problem where we tried to use ethtool on non-ethernet interfaces
994 - Warn if the ipvsadm packege is missing when LVS is used
995 - Dont use absolute pathnames in some of the event scripts
996 - Fix for persistent tdbs growing inifinitely.
997 * Wed Feb 06 2008 : Version 1.0.27
998 - Add eventscript for iscsi
999 * Thu Jan 31 2008 : Version 1.0.26
1000 - Fix crashbug in tdb transaction code
1001 * Tue Jan 29 2008 : Version 1.0.25
1002 - added async recovery code
1003 - make event scripts more portable
1004 - fixed ctdb dumpmemory
1005 - more efficient tdb allocation code
1006 - improved machine readable ctdb status output
1008 * Wed Jan 16 2008 : Version 1.0.24
1009 - added syslog support
1010 - documentation updates
1011 * Wed Jan 16 2008 : Version 1.0.23
1012 - fixed a memory leak in the recoveryd
1013 - fixed a corruption bug in the new transaction code
1014 - fixed a case where an packet for a disconnected client could be processed
1015 - added http event script
1016 - updated documentation
1017 * Thu Jan 10 2008 : Version 1.0.22
1018 - auto-run vacuum and repack ops
1019 * Wed Jan 09 2008 : Version 1.0.21
1020 - added ctdb vacuum and ctdb repack code
1021 * Sun Jan 06 2008 : Version 1.0.20
1022 - new transaction based recovery code
1023 * Sat Jan 05 2008 : Version 1.0.19
1024 - fixed non-master bug
1025 - big speedup in recovery for large databases
1026 - lots of changes to improve tdb and ctdb for high churn databases
1027 * Thu Dec 27 2007 : Version 1.0.18
1028 - fixed crash bug in monitor_handler
1029 * Tue Dec 04 2007 : Version 1.0.17
1030 - fixed bugs related to ban/unban of nodes
1031 - fixed a race condition that could lead to monitoring being permanently disabled,
1032 which would lead to long recovery times
1033 - make deterministic IPs the default
1034 - fixed a bug related to continuous recovery
1035 - added a debugging option --node-ip