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