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