similar to: Directly Get CTDB or SMB Status/Stats?

Hi Team, I'm working on a CTDB Prometheus Exporter. I have two questions... First, does anyone have an "internal" cheat sheet on the metrics and their descriptions? I didn't really see much online, or in the source code. Thanks -- BOB BUCK SENIOR PLATFORM SOFTWARE ENGINEER SKIDMORE, OWINGS & MERRILL 7 WORLD TRADE CENTER 250 GREENWICH STREET NEW YORK, NY 10007 T (212)

What is the impact of turning profiling on? profiling support = on More specifically, we're setting up a custom Prometheus exporter for Samba, but smbstatus does not provide a whole lot of detailed information for samba health, etc. I was hoping for more detailed information that we can forward to Prometheus. So my question is: 1. What options exist for efficiently getting metrics?

Hi Martin It seems as though, when I go from `clustering = no` to `clustering = yes`, if I do a domain join, it will fail. However, if I do a `systemctl restart ctdb` (knowing full well it will fail every time), if after this I add a sleep(15), then do a domain join, then do a `systemctl restart ctdb`, then the join will have worked, AND CTDB will start properly. So in a nutshell, in Ansible, -

And more information, wondering about DNS issues or DC issues... # wbinfo --ping-dc checking the NETLOGON for domain[MYDOMAINNAME] dc connection to "" failed failed to call wbcPingDc: WBC_ERR_DOMAIN_NOT_FOUND On Thu, Oct 1, 2020 at 9:21 AM Robert Buck <robert.buck at som.com> wrote: > Martin, > > Here you go, > > # echo "mypassword" | net

This turns out to be an SELinux issue. Does anyone know the proper commands to restorecon or otherwise to set the SELinux policy for persistent/volatile database files moved to a different directory? Martin or Amitay? On Wed, Nov 4, 2020 at 9:02 AM Robert Buck <robert.buck at som.com> wrote: > Running into problems configuring different locations for the volatile and > other

On Thu, Oct 15, 2020 at 09:01:01AM -0400, Robert Buck via samba wrote: > Can someone please respond to this question? We're unsure how to > persistently set these flags, which are VERY useful for performance from > what we see. We want to ensure that after reboot, particular nodes are > always set on (or others off). From the ctdb/doc/ctdb.1.xml man page file:

Folks, We use a Golang-based lock tool that we wrote for CTDB. That tool interacts with our 3.4 etcd cluster, and follows the requirements specified in the project. Question, does the external command line tool get called when LMASTER and RECMASTER are false? Given a scenario where we have a set of processes that have it set to false, then others that have it set to true, does the locking tool

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,

Could I impose upon someone to provide some guidance? Some hint? Thank you Is a shared file system actually required? If etcd is used to manage the global recovery lock, is there any need at that point for a shared file system? In other words, are there samba or CTDB files (state) that must be on a shared file system, or can each clustered host simply have these files locally? What must be

Martin, Here you go, # echo "mypassword" | net --no-dns-updates -U service-account-name ads testjoin domain.local kerberos_kinit_password NETBIOS_NAME$@DOMAIN.LOCAL failed: Client not found in Kerberos database Join to domain is not valid: The name provided is not a properly formed account name. On Wed, Sep 30, 2020 at 9:34 PM Martin Schwenke <martin at meltin.net> wrote:

Hi Martin, you seem to do a lot of work on CTDB. Let me ask a question... Is there a way to segment CTDB/Samba to minimize chatter? Specifically, what I have in mind... In recent years advances have been made in distributed SQL databases (ideas which are applicable here) whereby the communication profile between peers are minimized, and synchronization is never necessary except in circumstances

Hi Jeremy, and Martin, Digging in the code I think I figured it out (though untested). Here is my Ansible fragment. Is this correct for the property names? ... [legacy] realtime scheduling = false {% if ctdb_lmaster_capability is defined %} lmaster capability = {{ ctdb_lmaster_capability }} {% endif %} {% if ctdb_recmaster_capability is defined %} recmaster capability = {{

Hi I have a question regarding CTDB RecLockLatencyMs tunable parameter. Is there any relationship between the RecLockLatencyMs property and the RecoverInterval property? Does one need to be larger than the other? Or if RecLockLatencyMs were increased to 5000ms, should some other setting be changed in proportion? We're using a geo-distributed etcd cluster for the CTDB recovery lock and I

When I try to enable CTDB to manage (legacy) SMB and Winbind, I get startup errors. Sep 29 22:23:06 euw2-samba-server-c21-01 ctdb-eventd[1509]: *49.winbind: Failed to start winbind* Sep 29 22:23:06 euw2-samba-server-c21-01 ctdb-eventd[1509]: *startup event failed* Sep 29 22:23:06 euw2-samba-server-c21-01 ctdbd[1507]: *startup event failed* Sep 29 22:23:11 euw2-samba-server-c21-01 ctdbd[1507]:

Very helpful. Thank you, Martin. I'd like to share the information below with you and solicit your fine feedback :-) I provide additional detail in case there is something else you feel strongly we should consider. We made some changes last night, let me share those with you. The error that is repeating itself and causing these failures is: Takeover run starting RELEASE_IP 10.200.1.230

Running into problems configuring different locations for the volatile and other database directories. Can someone provide a quick sanity check on what I'm doing below? Thank you. Given [database] volatile database directory = /var/cache/dbdir/volatile persistent database directory = /var/cache/dbdir/persistent state database directory = /var/cache/dbdir/state And given, [root

Superb. I'll take a look. Thank you On Tue, Oct 6, 2020 at 1:46 AM Martin Schwenke <martin at meltin.net> wrote: > Hi Bob, > > On Mon, 5 Oct 2020 09:31:59 -0400, Robert Buck <robert.buck at som.com> > wrote: > > > It seems as though, when I go from `clustering = no` to `clustering = > yes`, > > if I do a domain join, it will fail. However, if I do a

On Sat, Aug 8, 2020 at 2:52 AM Martin Schwenke <martin at meltin.net> wrote: > Hi Bob, > > On Thu, 6 Aug 2020 06:55:31 -0400, Robert Buck <robert.buck at som.com> > wrote: > > > And so we've been rereading the doc on the public addresses file. So it > may > > be we have gravely misunderstood the *public_addresses* file, we never > read > >

Thank you, Martin. Yes, we happen to be using Samba and CTDB v4.10.7, on Ubuntu. *Would these happen to include the defect?* *In your opinion, will 4s be an issue?* We happen to be running this on top of a geo-distributed etcd cluster, and in this particular case there was about 4200 miles between the two data centers. We're running a distributed NFS file system over a total of three data

How can setlmasterrole be set persistently? Is there a way to put it in some config file? If not, if setting it from the command line is the only option, what is the recommended approach to ensure it is set upon reboot? Thx -- BOB BUCK SENIOR PLATFORM SOFTWARE ENGINEER SKIDMORE, OWINGS & MERRILL 7 WORLD TRADE CENTER 250 GREENWICH STREET NEW YORK, NY 10007 T (212) 298-9624 ROBERT.BUCK at