similar to: Porting CTDB to Solaris

I'm trying to build 3.0.30 on Alpha/Tru64-4.0G. The configure step works, but make fails when it tries to link smbd: Compiling popt/popt.c Compiling popt/poptconfig.c Compiling popt/popthelp.c Compiling popt/poptparse.c Linking bin/smbd ld: Unresolved: __unsafe_string_function_usage_here_size_t__ gmake: *** [bin/smbd] Error 1 This Should Never Happen :) -- that looks like a message for the

How can I confirm that idmap_ad is being called? I've configured Samba with --with-shared-modules=idmap_ad, built and installed it; the file ad.so is now present in /usr/local/samba/lib/ idmap/ as expected. I then added the following to smb.conf: idmap backend = tdb idmap uid = 65536 - 999999 idmap gid = 65536 - 999999 idmap config SU : backend = ad idmap config SU :

We're trying to share a directory that's mounted via NFS from another server; when we connect to that share, smbd panics and tries to dump core. This is samba-3.0.30 on Alpha/Tru64-4.0G. The directory we're trying to use is exported from a Linux box called sesfs (Centos 4.4) and mounted on the Alpha server via NFS as /sesfs/scratch. I've appended below an edited summary from

Hi, All I test with ctdb-1.2.0-18.1, and there is a corefile. I want to analyze the corefile, but can't find the ctdb debuginfo. Could you tell me where to find the ctdb debuginfo? -- Best Regards. Yu Liao

I think I've found out why MacOS 10.5.x (Leopard) clients are unable to connect to Samba shares when authenticating with Kerberos. Basically, the Leopard Macs insert a few extra bytes (Padding and reqFlags, according to wireshark) into the security blob within the Session Setup AndX Request packet, bytes whose start tag is 0xa1, in a spot where Samba's parser expects 0xa2. The critical

Hello, I try to set up a clustered samba server (on Novell SLES11SP2) based upon CTDB and NFS. My problem is that I do not yet understand the structure of the setup when using NFS. I followed the documentation in http://wiki.samba.org/index.php/CTDB_Setup#Setting_up_CTDB_for_clustered_NFS As far as I understand this documentation, it should be possible to set up a samba cluster say having 3

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 >

Hello, I am trying to migrate samba domain controller (version 3.6, passdb backend = tdbsam) to a new clustered environment with CTDB (same samba version). I have a functional ceph storage and the ctdbd configured according to the documentation. However, all available guides are for the fresh installations and I can't migrate current data into the CTDB. Simply restoring tdb database into

Hello all, 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. I'm trying to test clustered samba and have a two node CTDB setup (Following the guide here:

Hi All, Are there any special CTDB/SMB configuration settings/dependencies to manage Winbind across CTDB managed servers authenticating via Active Directory(AD)? An example would be Samba's IDMAP backend for Winbind: RID vs. AD or tag Winbind to a primary CTDB node and point other nodes to authenticate from AD via proxy primary CTDB node? /etc/sysconfig/ctdb on all nodes is as follows:

Hi All, My site has two separate clustered Samba instances (managed by two independent CTDB instances) running over GPFS. In the last couple of weeks, we have seen a recurring issue that causes the `smbd` process in *one* of these instances to become unresponsive (as seen by CTDB), which results in flapping of CTDB and multiple IP takeover runs. The symptoms that we observe are: 1) Samba

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

Hi everyone, I'm setting up a clustered Samba+CTDB in front of CephFS and am running into an issue during failover. For the most part everything seems to work: the IP moves quickly, smbd is started on the right node, etc, but if there is an IO load from a client during failover (e.g., copying a big directory full of files in File Explorer), it pauses for a couple of seconds and then pops up

hi guys, we're evaluating the available clustering options to get ctdb up and running for a highly available file server. we've set up both gluster and ocfs2 both on seperate 2 node setups. ocfs2 seems to provide better throughput and iops to samba clients than does gluster and that is comparing a single node server to a ctdb clustered 2 node server. problem with ocfs2 is that i've

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

Hi all, I try to update two clustered samba file servers. Right now samba 4.7.0 with ctdb is running on both of them. To update samba I stopped ctdb on one of the servers, and compiled and installed samba 4.7.1 with: ./configure --with-cluster-support --with-shared-modules=idmap_tdb2,idmap_ad,vfs_glusterfs --with-systemd Trying to start ctdb on the updated server fails with "

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

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

I have been working on a CTDB cluster on and off for a while now. I had it working great for a while. THen I decide dthat I wanted to change the configuration of my replicated volumes. I changed my DRBD configuration to match my desired configuration. Now I can get the CTDB to work quite right. I am able to join the cluster to the domain without issues. I can also list my ad users and groups using

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