ctdb-vl.spec 52 KB

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