similar to: [CTDB] how does LMASTER know where the record is stored?

Hi 2 node drbd cluster with ocfs2. both nodes: openSUSE 4.1.9 with drbd 8.4 and ctdbd 2.3 All seems OK with ctdb: n1: ctdb status Number of nodes:2 pnn:0 192.168.0.10 OK (THIS NODE) pnn:1 192.168.0.11 OK Generation:1187222392 Size:2 hash:0 lmaster:0 hash:1 lmaster:1 Recovery mode:NORMAL (0) Recovery master:0 n2: ctdb status Number of nodes:2 pnn:0 192.168.0.10 OK pnn:1 192.168.0.11

hi everyone an attempt to set up a cluster, I'm reading around and see some howto writers would say to put "private dir on the FS cluster" - one question I have: is this correct? necessary? I have partial success, I get: $ ctdb status Number of nodes:2 pnn:0 10.5.6.32 OK pnn:1 10.5.6.49 UNHEALTHY (THIS NODE) Generation:323266562 Size:2 hash:0 lmaster:0 hash:1

Hello, i upgraded my ctdb cluster (3 nodes) from samba 4.7.7 to 4.8.3. Followed the steps under "policy" in this wikipage https://wiki.samba.org/index.php/Upgrading_a_CTDB_cluster. I shutdown all CTDB nodes and upgraded them. After the upgrade i started all nodes and ctdb status shows: Number of nodes:3 pnn:0 192.168.199.52   OK (THIS NODE) pnn:1 192.168.199.53   OK pnn:2

drbd ctdb ocfs2 Hi Everything seems OK apart from the IP takeover. public_addresses 192.168.1.80/24 enp0s3 192.168.1.81/24 enp0s3 ctdb status Number of nodes:2 pnn:0 192.168.1.10 PARTIALLYONLINE pnn:1 192.168.1.11 PARTIALLYONLINE (THIS NODE) Generation:2090727463 Size:2 hash:0 lmaster:0 hash:1 lmaster:1 Recovery mode:NORMAL (0) Recovery master:1 but we are getting: 2014/07/11

hi Michael Adam: Thanks for you work on samba. Here I am looking for some advice and your help. I have been stuck in continuous availability of samba 4.3.9 for two weeks. Continuous availability in SMB3 is an attractive feature and I am strugling to enable it. smb.conf, ctdb.conf are attached. Cluster file system is cephfs and mount to /CephStorage client: Windows 8 Pro root at node0:~# samba

hello everyone: I want to know if the lastest version of ctdb has the following mechanism: when a record in tdb was added or upadted, if there are two same record in different nodes.In other words, if ctdb need to backup a record on other node? if not, do we plan to add this mechanism? thank you ! ________________________________ sunyekuan at outlook.com

Hi , I have set up a 2-node CTDB cluster serving NFS and CIFS authenticating Windows and Linux users via Active Directory. The setup works fine, except only one server in the CTDB-cluster is able to join the AD domain at a given instance. If you manually add the other server into AD, the already connected server gets disconnected. There is no specific error message logged in /var/log/message or

On 03/07/16 13:06, Volker Lendecke wrote: > On Fri, Jul 01, 2016 at 10:00:21AM +0100, Alex Crow wrote: >> We've had a strange issue after following the recommendations at >> https://wiki.samba.org/index.php/Ping_pong, particularly the part >> about mmap coherence. We are running CTDB/Samba over a MooseFS >> clustered FS, and we'd not done the ping-pong before.

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

Hello, at this time i want to install a CTDB Cluster with SAMBA 4.7.7 from SOURCE! I compiled samba as follow: |./configure| |--with-cluster-support ||--with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad| The whole SAMBA enviroment is located in /usr/local/samba/. CTDB is located in /usr/local/samba/etc/ctdb. I guess right that the correct path of ctdbd.conf (node file, public address file

Hi, I came across the 'CTDB_CAPABILITY_LMASTER=no' and 'CTDB_CAPABILITY_RECMASTER=no' options in my quest to salvage a rather poorly performing CTDB cluster over Ceph(fs). Unfortunately, the docs provide not enough information for a clustering noop like myself. Would there be any benefit to disabling those options for a branch office node on a high-latency WAN connection?

Hi, What did I miss / do wrong? My config didn't work like on the below linked video: http://www.samba.org/~tridge/ctdb_movies/node_disable.html With my config, the copy process fails/breaks despite that the tesztxp PC successfully maps the other (samba) PC in case the first (samba) PC is out. In the samba logs (even at log level = 10) I didn't see any information that can help me solve

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

All, I have a 3 node CTDB cluster which serves 4 'public addresses'. /etc/ctdb/public_addresses file is node specific and present in the above path in participating nodes. All the nodes run RHEL 6.2. Other ctdb config files such as "nodes" and "public_addresses" are placed on a shared filesystem mounted on a known location (say, /gluster/lock) On starting CTDB

Hi Bob, On Tue, 27 Oct 2020 15:09:34 +1100, Martin Schwenke via samba <samba at lists.samba.org> wrote: > On Sun, 25 Oct 2020 20:44:07 -0400, Robert Buck <robert.buck at som.com> > wrote: > > > 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 > >

greetings, trying to follow tridge's failover process at http://samba.org/~tridge/ctdb_movies/node_disable.html I encounter this error. oss02:~ # smbstatus -np Processing section "[homes]" Processing section "[profiles]" Processing section "[users]" Processing section "[groups]" Processing section "[local]" Processing section

Hi, I?ve setup a simple ctdb cluster. Actually copied the config file from an existing system. Thats what happens: Node 1, alone Number of nodes:2 pnn:0 10.0.0.1 OK (THIS NODE) pnn:1 10.0.0.2 DISCONNECTED|UNHEALTHY|INACTIVE Generation:1369816268 Size:1 hash:0 lmaster:0 Recovery mode:NORMAL (0) Recovery master:0 Node1, after start of ctdb on Node 2 Number of nodes:2 pnn:0

On Thu, 28 Jun 2018 10:30:07 +0200 Micha Ballmann via samba <samba at lists.samba.org> wrote: > Hello, > > i upgraded my ctdb cluster (3 nodes) from samba 4.7.7 to 4.8.3. > Followed the steps under "policy" in this wikipage > https://wiki.samba.org/index.php/Upgrading_a_CTDB_cluster. I shutdown > all CTDB nodes and upgraded them. After the upgrade i started

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

Hi Bob, On Tue, 6 Oct 2020 20:56:39 -0400, Robert Buck <robert.buck at som.com> wrote: > Hi Martin, you seem to do a lot of work on CTDB. Let me ask a question... Yes, I have done a lot of work on CTDB. A bit less lately... > 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 >