similar to: CTDB vs HA(clusterlabs)

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

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

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

hi everybody, would you know if 8 version is going to have HA solutions from clusterlabs.org available, just like Centos7 has? (from Centos' own repos/streams) many thanks, L.

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

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

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, from SAMBA 4.9/4.10 there was a big change regarding CTDB. Does anyone have an example configuration, how to configure a CTDB cluster from version 4.10? Is there someone who run CTDB with SAMBA 4.10? Best regards Micha

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 Folks, We're in the process of setting up a Samba cluster (Samba+CTDB+etcd), and we (presently) using Winbind. We use AD. We're finding that the domain join (or kerberos ticket renewal) is unreliable. Every day we find Samba/Winbind is no longer joined to the domain. Now, we're in a bit of a learning curve here, and automating everything with Terraform + Ansible. We have yet to

On 09/11/16 23:28, Martin Schwenke via samba wrote: > On Wed, 9 Nov 2016 16:05:32 +0000, lejeczek via samba > <samba at lists.samba.org> wrote: > >> 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? > No, this is not

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

Release Announcements ===================== This is the third release candidate of Samba 4.6. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.6 will be the next version of the Samba suite. UPGRADING ========= vfs_fruit option

Release Announcements ===================== This is the third release candidate of Samba 4.6. This is *not* intended for production environments and is designed for testing purposes only. Please report any defects via the Samba bug reporting system at https://bugzilla.samba.org/. Samba 4.6 will be the next version of the Samba suite. UPGRADING ========= vfs_fruit option

====================================================== "Nothing you wear is more important than your smile." Connie Stevens ====================================================== Release Announcements ===================== This is the first stable release of Samba 4.6. Please read the release notes carefully before upgrading. UPGRADING ========= ID Mapping ---------- We

====================================================== "Nothing you wear is more important than your smile." Connie Stevens ====================================================== Release Announcements ===================== This is the first stable release of Samba 4.6. Please read the release notes carefully before upgrading. UPGRADING ========= ID Mapping ---------- We

Hi All, I am using Samaba for my network users and I run out of space soon as so many users store BIG files on the share folders. Is there a way to specify the max size for a file that can be stored using Samaba? Or At least max size for a folder will also help. -- Thank you, Kani

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

Dear list, We are about to upgrade to Samba 4.2.9 from sernet-samba 4.1.6 + CTDB 1.0.114.7 running on top of GPFS. My understanding is that as of 4.2, CTDB is now part of Samba. So does this mean we need to uninstall all of our sernet-samba and ctdb RPMs (we are on CentOS 6), then install the sernet-samba 4.2.9 rpms and reconfigure everything for CTDB? For those who have done this, how

A little off topic, but this does revolve around Samaba. I'm hoping someone can help me get to a working aolution. I haven't been able to find a clear quide, but it must have been done by others. I'm trying to use setup a VPN using OpenVPN on Pfsense with authentication via my Samba AD (Version 4.9.4-Debian) I keep getting a "Could not connect to LDAP server" error when