similar to: [Announce] CTDB 2.3 available for download

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

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,

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

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

Can anyone help with some pointers to debug a problem with Samba and CTDB with smbstatus traversing the connections tdb? I've got a new two node cluster with Samba and CTDB on AIX. If I run smbstatus when the server has much user activity it hangs and the node it was run on gets banned. I see the following in the ctdb log: 2014/10/29 11:12:45.374580 [3932342]:

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

Hi folks, We're building a new CTDB cluster - any recommendation on what version of CTDB is the most "production" at the moment? We're currently on 1.2.66 on our currently in-service clusters. Cheers, Orlando > -------- Original Message -------- > Subject: [Samba] [Announce] CTDB 2.4 available for download > Date: Fri, 23 Aug 2013 14:11:29 +1000 > From:

Hi Bob, On Thu, 26 Oct 2017 22:44:30 -0700, Computerisms Corporation via samba <samba at lists.samba.org> wrote: > I set up a ctdb cluster a couple months back. Things seemed pretty > solid for the first 2-3 weeks, but then I started getting reports of > people not being able to access files, or some times directories. It > has taken me a while to figure some stuff out,

Hi, This morning our CTDB managed cluster took a nosedive. We had member machines with hung smbd tasks which causes them to reboot, and the cluster did not come back up consistently. We eventually got it more or less stable with two nodes out of the 3, but we're still seeing worrying messages, eg we've just noticed: 2017/04/19 12:10:31.168891 [ 5417]: Vacuuming child process timed

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

On Wed, 19 Apr 2017 18:06:35 +0200, David Disseldorp via samba wrote: > > 2017/04/19 10:40:31.294250 [ 7423]: /etc/ctdb/debug_locks.sh: line 73: > > gstack: command not found > > This script attempts to dump the stack trace of the blocked process, > but can't as gstack isn't installed - it should be available in the > gdb package. > > @Martin: would the

Hi, This occurred again this morning, when the user reported the problem, I found in the ctdb logs that vacuuming has been going on since last night. The need to fix it was urgent (when isn't it?) so I didn't have time to poke around for clues, but immediately restarted the lxc container. But this time it wouldn't restart, which I had time to trace to a hung smbd process, and

hm, I stand correct on the problem solved statement below. Ip addresses are simply not cooperating on the 2nd node. root at vault1:~# ctdb ip Public IPs on node 0 192.168.120.90 0 192.168.120.91 0 192.168.120.92 0 192.168.120.93 0 root at vault2:/service/ctdb/log/main# ctdb ip Public IPs on node 1 192.168.120.90 0 192.168.120.91 0 192.168.120.92 0 192.168.120.93 0 root at

Hi List, I set up a ctdb cluster a couple months back. Things seemed pretty solid for the first 2-3 weeks, but then I started getting reports of people not being able to access files, or some times directories. It has taken me a while to figure some stuff out, but it seems the common denominator to this happening is vacuuming timeouts for locking.tdb in the ctdb log, which might go on

On Thu, 2 Nov 2017 11:17:27 -0700, Computerisms Corporation via samba <samba at lists.samba.org> wrote: > This occurred again this morning, when the user reported the problem, I > found in the ctdb logs that vacuuming has been going on since last > night. The need to fix it was urgent (when isn't it?) so I didn't have > time to poke around for clues, but immediately

Hi Martin, Thanks for reading and taking the time to reply >> ctdbd[89]: Unable to get RECORD lock on database locking.tdb for 20 seconds >> /usr/local/samba/etc/ctdb/debug_locks.sh: 142: >> /usr/local/samba/etc/ctdb/debug_locks.sh: cannot create : Directory >> nonexistent >> sh: echo: I/O error >> sh: echo: I/O error > > That's weird. The only

Hi, Since CTDB tree has been merged in Samba tree, any new CTDB development would be done in Samba tree. Till combined Samba+CTDB is released, CTDB fixes would be released as minor releases starting with 2.5.1. Amitay. Changes in CTDB 2.5.1 ===================== Important bug fixes ------------------- * The locking code now correctly implements a per-database active locks limit. Whole

Hi Alex, On Wed, 19 Apr 2017 12:55:45 +0100, Alex Crow via samba wrote: > ----- Process in D state, printing kernel stack only > [<ffffffffa05b253d>] __fuse_request_send+0x13d/0x2c0 [fuse] > [<ffffffffa05b26d2>] fuse_request_send+0x12/0x20 [fuse] > [<ffffffffa05bb66c>] fuse_setlk+0x16c/0x1a0 [fuse] > [<ffffffffa05bc40f>] fuse_file_lock+0x5f/0x210 [fuse]

Hi Martin, well, it has been over a week since my last hung process, but got another one today... >> So, not sure how to determine if this is a gluster problem, an lxc >> problem, or a ctdb/smbd problem. Thoughts/suggestions are welcome... > > You need a stack trace of the stuck smbd process. If it is wedged in a > system call on the cluster filesystem then you can blame

On Tue, 14 Nov 2017 22:48:57 -0800, Computerisms Corporation via samba <samba at lists.samba.org> wrote: > well, it has been over a week since my last hung process, but got > another one today... > >> So, not sure how to determine if this is a gluster problem, an lxc > >> problem, or a ctdb/smbd problem. Thoughts/suggestions are welcome... > > > >