similar to: Recommended CTDB release for new installation

Displaying 20 results from an estimated 8000 matches similar to: "Recommended CTDB release for new installation"

2013 Aug 23
0
[Announce] CTDB 2.4 available for download
Changes in CTDB 2.4 =================== User-visible changes -------------------- * A missing network interface now causes monitoring to fail and the node to become unhealthy. * Changed ctdb command's default control timeout from 3s to 10s. * debug-hung-script.sh now includes the output of "ctdb scriptstatus" to provide more information. Important bug fixes
2013 Jul 11
0
[Announce] CTDB 2.3 available for download
Changes in CTDB 2.3 =================== User-visible changes -------------------- * 2 new configuration variables for 60.nfs eventscript: - CTDB_MONITOR_NFS_THREAD_COUNT - CTDB_NFS_DUMP_STUCK_THREADS See ctdb.sysconfig for details. * Removed DeadlockTimeout tunable. To enable debug of locking issues set CTDB_DEBUG_LOCKS=/etc/ctdb/debug_locks.sh * In overall statistics and database
2014 Sep 26
0
[Announce] CTDB release 2.5.4 is ready for download
This is the latest stable release of CTDB. CTDB 2.5.4 can be used with Samba releases 3.6.x, 4.0.x and 4.1.x. Changes in CTDB 2.5.4 ===================== User-visible changes -------------------- * New command "ctdb detach" to detach a database. * Support for TDB robust mutexes. To enable set TDBMutexEnabled=1. The setting is per node. * New manual page ctdb-statistics.7.
2013 Oct 30
0
[Announce] CTDB 2.5 available for download
Changes in CTDB 2.5 =================== User-visible changes -------------------- * The default location of the ctdbd socket is now: /var/run/ctdb/ctdbd.socket If you currently set CTDB_SOCKET in configuration then unsetting it will probably do what you want. * The default location of CTDB TDB databases is now: /var/lib/ctdb If you only set CTDB_DBDIR (to the old default of
2013 May 30
0
[Announce] CTDB 2.2 available for download
Changes in CTDB 2.2 =================== User-visible changes -------------------- * The "stopped" event has been removed. The "ipreallocated" event is now run when a node is stopped. Use this instead of "stopped". * New --pidfile option for ctdbd, used by initscript * The 60.nfs eventscript now uses configuration files in /etc/ctdb/nfs-rpc-checks.d/ for
2016 Apr 01
0
[Announce] CTDB release 2.5.6 is available for download
This will be the last stable release of CTDB 2.5.x. CTDB 2.5.6 should only be used with Samba releases prior to Samba 4.2.x (i.e. Samba releases 3.6.x, 4.0.x and 4.1.x). Please note that Samba releases 3.6.x, 4.0.x and 4.1.x are out of support. If you are still using any of these releases for clustered samba with CTDB 2.5.x, please switch to latest Samba 4.3.x or 4.4.0 (Since Samba 4.2.0 release
2014 Apr 02
0
[Announce] CTDB 2.5.3 available for download
Changes in CTDB 2.5.3 ===================== User-visible changes -------------------- * New configuration variable CTDB_NATGW_STATIC_ROUTES allows NAT gateway feature to create static host/network routes instead of default routes. See the documentation. Use with care. Important bug fixes ------------------- * ctdbd no longer crashes when tickles are processed after reloading the nodes
2020 Nov 12
0
Getting CTDB dbstatistics in csv format?
Hi Bob, On Wed, 11 Nov 2020 08:10:28 -0500, Robert Buck via samba <samba at lists.samba.org> wrote: > Folks, thank you for being so helpful. > > I can't quite figure out the exact command line to get ctdb > dbstatistics for the locking.tdb in CSV format. How do you do this? > > [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, > dbstatistics
2020 Nov 12
3
Getting CTDB dbstatistics in csv format?
Thanks, I'll do that. It might be a week or two. But I have solid C skills going back 25 years, and spent a decade doing C++. Let me know if there's a "getting started guide" for developers on the Samba project. Key tools to install, etc. I will need to spin up a VM to work in. Also, should chat with the CTO so he's aware. On Thu, Nov 12, 2020 at 4:46 AM Martin Schwenke
2016 Sep 07
0
[Announce] Samba 4.5.0 Available for Download
Does this push 4.2.x to discontinued? On Wed, Sep 7, 2016 at 9:06 AM, Stefan Metzmacher <metze at samba.org> wrote: > ====================================================== > "It does not matter how slowly you go > as long as you do not stop." > > Confucius >
2020 Nov 11
2
Getting CTDB dbstatistics in csv format?
Folks, thank you for being so helpful. I can't quite figure out the exact command line to get ctdb dbstatistics for the locking.tdb in CSV format. How do you do this? [root at use1-samba-server-c25-use1-01 ec2-user]# ctdb -X --separator=, dbstatistics locking.tdb --help Usage: [OPTION...] -d, --debug=STRING debug level -t, --timelimit=INT timelimit (in seconds) -n,
2013 Jan 09
0
[Announce] CTDB 2.1 available for download
Highlights ======= * Support for Samba 4.0.0 To use CTDB 2.1 with Samba 3.x, enable Samba3AvoidDeadlocks tunable * Set CTDB_BASE in eventscripts, so they can be run easily * Clean up orphaned interfaces * Do not restart NFS on reconfigure event * Fix RSN based recovery of persistent databases to avoid corruption * Re-factor and separate IP allocation algorithms Reporting bugs &
2018 Feb 26
0
[ctdb] Unable to take recovery lock - contention
When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node 2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602 2018/02/12 19:38:51.529060
2018 May 08
0
CTDB Path
Hi Micha, On Mon, 7 May 2018 15:46:50 +0200, Micha Ballmann <ballmann at uni-landau.de> wrote: > i'm still trying to find out what is the right path for ctdb.conf > (ubuntu 18.04, samba was compiled from source!!). > > When im trying to start CTDB without any config file, my log in > /usr/local/samba/var/log/log.ctdb shows me: > > 2018/05/07 12:56:44.363513
2020 Mar 03
2
start/stop ctdb
Thanks, i added "Environment=PATH=$PATH:/usr/local/samba/bin:/bin". Needed also to add "/bin" because couldnt find "sleep". Thats the script now: ---- [Unit] Description=CTDB Documentation=man:ctdbd(1) man:ctdb(7) After=network-online.target time-sync.target ConditionFileNotEmpty=/usr/local/samba/etc/ctdb/nodes [Service]
2020 Mar 03
1
start/stop ctdb
On 03/03/2020 09:13, Ralph Boehme via samba wrote: > Am 3/3/20 um 10:05 AM schrieb Micha Ballmann via samba: >> Mar? 3 09:50:50 ctdb1 systemd[1]: Starting CTDB... >> Mar? 3 09:50:50 ctdb1 ctdbd[24663]: CTDB starting on node >> Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Starting CTDBD (Version 4.11.6) as >> PID: 24667 >> Mar? 3 09:50:50 ctdb1 ctdbd[24667]: Created PID file
2020 Mar 03
0
start/stop ctdb
Ah, yes, thats it Ralph.. Good one. Then in the systemd.service file you need to add. [Service] Environment=PATH=$PATH:/usr/local/samba/bin > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Ralph Boehme via samba > Verzonden: dinsdag 3 maart 2020 10:13 > Aan: Micha Ballmann; Anoop C S > CC: samba at lists.samba.org >
2020 Mar 03
1
start/stop ctdb
Hai, Hmm, about .. > "Environment=PATH=$PATH:/usr/local/samba/bin:/bin". > Needed also > to add "/bin" because couldnt find "sleep". /bin should be found in $PATH.. In since it looks like it does not. Then i suggest this: Environment="PATH=$PATH:/usr/local/samba/bin:/usr/local/samba/sbin:/bin:/sbin:/usr/bin:/usr/sbin" # to make sure you
2018 Feb 26
0
答复: [ctdb] Unable to take recovery lock - contention
Am Montag, 26. Februar 2018, 17:26:06 CET schrieb zhu.shangzhong--- via samba: Decoded base64 encoded body with some chinese characters: ------------------原始邮件------------------ 发件人:朱尚忠10137461 收件人:samba at lists.samba.org <samba at lists.samba.org> 日 期 :2018年02月26日 17:10 主 题 :[ctdb] Unable to take recovery lock - contention When the ctdb is starting, the "Unable to take recovery lock
2018 Feb 26
2
[ctdb] Unable to take recovery lock - contention
When the ctdb is starting, the "Unable to take recovery lock - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The following the ctdb logs: 2018/02/12 19:38:51.147959 ctdbd[5615]: CTDB starting on node 2018/02/12 19:38:51.528921 ctdbd[6602]: Starting CTDBD (Version 4.6.10) as PID: 6602 2018/02/12 19:38:51.529060