similar to: Nodes in CTDB Cluster don't release recovery lock

Hello all, Thanks for the input. I opened up the firewall ports and testing connectivity by ctdb's ping to no avail. I did however fix the problem. I must have missed the section of the guide outlining the importance of the nodes file, but it seems the issue was that machine A's nodes file was in reverse order compared to B's. After rectifying that the cluster came up without issue,

Hi Christian, On Wed, 6 May 2020 13:16:36 -0700, Christian Kuntz via samba <samba at lists.samba.org> wrote: > First of all, apologies if this isn't the right location for this question, > I couldn't find a CTDB specific mailing list or IRC so I figured the > general one would be appropriate. Please let me know if this question is > better placed elsewhere. This is the

Hello all, I'm currently running samba on debian buster, version 2:4.9.5+dsfg-5 with lustre 2.13.0. The problem I'm experiencing is pretty straightforward, if I set "use mmap = no" in my global config (as suggested by the wiki), winbind fails to start and the cluster grinds to a halt. Here is the error messages from systemd: Sep 28 22:14:17 tenzin systemd[1]: Starting Samba

Dear All, I'm thinking of implementing Samba CTDB as a Files server which join to DC. Would like to have your advise on which distro get the setup example and the package ready? Also anythings that I should be know... Thank You Regards, Min Wai

Hi all, is it possible to use AD DC mode with clustering mode (clustering = yes)? And if so, what is the procedure? Should I setup CTDB and Gluster before calling samba-tool domain provision? I think it would be nice to mention it in the documentation. Regards.

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

Hi to all, I'm having a CTDB-Cluster with two nodes (both Ubuntu wit Sernet-packages 4.17.4). Now I want to replace one of the nodes. The first step was to bring a new node to the CTDB-Cluster. This time a Debian 11 but with the same sernet-packages (4.17.4). Adding the new node to /etc/ctdb/nodes at the end of the list. And the virtual IP to /etc/ctdb/public_addresses, also at the end

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

Hi, I don't have the user root. No changes :( Sometimes a user gets permissions, sometimes not. This net conf is now running: [global] ??? winbind refresh tickets = Yes ??? winbind use default domain = yes ??? template shell = /bin/bash ??? idmap config * : range = 1000000 - 1999999 ??? idmap config EXAMPLE : backend = rid ??? idmap config EXAMPLE : range = 500 - 200000 ??? hide dot files

I'm currently testing fail-over with a two-node active-active cluster (with node dig and node dag): Both nodes are up, one is manually killed. CTDB on the node that's still alive should perform a recovery and everything should working again. What's infrequently happening is: After killing the pacemaker-process on dag (and dag consequently being fenced), dig's CTDB tries to

Hi everybody, I just updated my ctdb node from Samba version 4.9.4-SerNet-Debian-11.stretch to Samba version 4.9.8-SerNet-Debian-13.stretch. After restarting the sernet-samba-ctdbd service the node doesn't come back and remains in state "UNHEALTHY". I can find that in the syslog: May 16 11:25:40 ctdb-lbn1 ctdb-eventd[13184]: 50.samba: samba not listening on TCP port 445 May 16

Only thing i see to do this is setup a clustert print server. I cant tell if its possible with samba. ( sorry ) Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > basti via samba > Verzonden: woensdag 26 april 2017 16:39 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba AD Printer Failover >

------------------原始邮件------------------ 发件人：朱尚忠10137461 收件人：samba@lists.samba.org <samba@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 - contention" log will be output all the time. Which cases will the "unable to take lock" errror be output? Thanks! The

Hi, I'd like to set up a HA Samba server that serves out data from NFS mounts​. I was thinking that CTDB was the thing to do use but it is only mentioned with serving clustered file systems like Gluster, Lustre, etc. Is there a way to set up a HA Samba server without a clustered file system? ​Thanks, Steve​

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

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

Hello all, I'm running into a significant performance issue where copying a couple thousand <3kb files from my stretch SMB server to a mac client. Dragging + dropping the files from the gui results in a long period of time in which the client is "preparing to copy" and then actually transferring, during this time transfer starts around 300MB/s, then after around 5-10 seconds

There is a 3 nodes ctdb cluster is running. When one of 3 nodes is powered down, lots of logs will be wrote to log.ctdb. node1: repeat logs: 2018/09/04 04:35:06.414369 ctdbd[10129]: Recovery has started 2018/09/04 04:35:06.414944 ctdbd[10129]: connect() failed, errno=111 2018/09/04 04:35:06.415076 ctdbd[10129]: Unable to run startrecovery event node2: repeat logs: 2018/09/04 04:35:09.412368

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 > >

On 03/07/16 21:47, Volker Lendecke wrote: > On Sun, Jul 03, 2016 at 08:42:36PM +0100, Alex Crow wrote: >> I've only put the "private dir" onto MooseFS, as instructed in the CTDB >> docs. > Can you quote these docs, so that we can correct them? Here, under the lustre section. I applied the same config at it's a similar FS (ie distributed with a central metadata