similar to: CTDB + Samba + Winbind + ActiveDirectory

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

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 everybody, I have tested CTDB+GFS2+CMAN under Debian. It works good but I do not understand some points. It is possible to run the CTDB defining it under services section in cluster.conf but running it on the second node shuts down the process at the first one. My CTDB configuration implies 2 active-active nodes. Does CTDB care if the node starts with clean_start="0" or

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

I am attempting to configure a Samba cluster using DRBD and CTDB. I am currently having some issues with winbind. Everytime I start winbind or attempt to join my server to the domain the machine stalls and the ctdb error log is filled with the following: 2010/04/30 14:49:59.367076 [ 8394]: server/ctdb_control.c:445 Unknown CTDB control opcode 119 I have not been able to find a description of

Hi, I am setting up ctdb samba, and have hit a brick wall trying to solve the following issue. 1. getent does not retrieve the list of domain users or groups (wbinfo works fine) I'm not sure what I'm missing but I've almost spent the whole day trying to resolve this one and haven't made any progress :-( Any help or suggestions are appreciated My configuration is

Hi Jeremy, Thanks so much for your reply! As a matter of fact, we did just that around 3:45p yesterday when our CTDB cluster was unable to self-heal from the latest in this series of failover events. Here's how the situation went down: 1) We saw flapping identical to that described in my original post 2) After about 30 minutes of waiting, CTDB was just spinning with `smbd` repeatedly

Hi All I have a newly implemented two node CTDB cluster running on CentOS 7, Samba 4.7.1 The node network is a direct 1Gb link Storage is Cephfs ctdb status is OK It seems to be running well so far but I'm frequently seeing the following in my log.smbd: [2018/09/18 19:16:15.897742, 0] > ../source3/lib/dbwrap/dbwrap_ctdb.c:1207(fetch_locked_internal) > db_ctdb_fetch_locked for

Hi, I have a two server setup that acts as SMB as well as NFS servers in active/active configuration managed by CTDB(http://ctdb.samba.org/). When a file is updated by SMB clients(followed by file-close), other SMB clients can see and modify the file. But when a NFS client (same user) updates the same file(followed by file-close), only one SMB server can see the updates. The clients mounting

Hi guys, I try to set up two identical installed up to date CentOS6 machines with Glusterfs/CTDB/Samba . I have set up Glusterfs and it works. I have set up CTDB from CentOS and it seems to work too. Samba is AD integrated and works mainly. The main problem is that file locking seem to not work between the machines at all. If two Win7 clients try to open an document from the same Samba server

Hi all, We're running gpfs 3.5.0.12 (5 total nsds & quorum servers, 2 nsds running samba), sernet-samba 4.1.4-7, and ctdb 1.0.114.7-1 and trying to get transparent failover to work from a windows 8 client. We have ctdb failover working, i.e. if I run mmshutdown on one of the nodes the IPs failover in a few seconds after the GPFS mount is unmounted. For our transparent failover test, I

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

Hi Can anyone advise me on "kernel oplocks" in a ctdb cluster. I have a ctdb (GPFS is the parallel file system) setup that uses samba (3.5.8) for cifs and IBM CNFS for NFS. Reading the documentation on kernel oplocks it seems to me that I can export the same area via samba and NFS with "kernel oplocks = Yes" . My logic is that IBM CNFS has shared NFS locking

Hi, in the following scenario I've got the Problem of "STATUS_SHARE_VIOLATION". Client A (with User 1) copies a file to share X. (with: DENY_NONE 0x120196 WRONLY NONE) Client B (with User 1) reads this file from share X (with: DENY_NONE 0x120089 RDONLY NONE) Now Client C (with User 1) wants also to read this file from share X and gets the STATUS_SHARE_VIOLATION.

Hi I'm encountering an error with some of my Windows clients when using CTDB and samba to access a GPFS hosted share. We see the following error all the time. [2011/03/14 12:31:16.549084, 1] modules/vfs_gpfs.c:1099(vfs_gpfs_ntimes) vfs_gpfs_ntimes: set GPFS ntimes failed -1 The copy continues but is slow. All the timestamps seem reasonable for the data copied. The GPFS

I am attempting to configure a Samba cluster using DRBD and CTDB. I am currently having some issues with winbind. Everytime I start winbind or attempt to join my server to the domain the machine stalls and the ctdb error log is filled with the following: 2010/04/30 14:49:59.367076 [ 8394]: server/ctdb_control.c:445 Unknown CTDB control opcode 119 I have not been able to find a description of

Dear all, after downloading ctdb with rsync -avz samba.org::ftp/unpacked/ctdb and compiling well. I installed on my Centos 5.3 sernet package samba 3.5.2. Also working well. But after setting up ctdb and samba und running it my two nodes freezing for a while And ctdb and samba are down again. On Both nodes My /etc/sysconfig/ctdb: CTDB_RECOVERY_LOCK="/cluster/recovery/recovery"

Hi, I am using samba samba3-3.3.4-39, with ctdb ctdb-1.0-69.x86_64, gpfs gpfs-3.2.1 on centos 5.3 x86_64. My problem is that from samba share I can't read file permissions and file ownership, although I'm in "domain admins" group, which has full permissions(rwx) via inherited acl (not user or group ownership). If I'm in a group that owns the file, I can read the permissions,

Tried single quotes on Domain Admins in the pam.d file as well as a backslash on the space with no effect. I've found several references that just say "no spaces in group names." Is there really no way to do this? Also, most references I find to using these lines in pam.d say that "sufficient" should work, but I'm finding that users in the named group can then log in