similar to: CTDB_Recovery_Lock

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

I've been having issues with KVM lately where I sometimes put my host into sleep while a guest is still running, which prevents it from waking up properly. This is somewhat expected due to my setup, but I have mistakenly done this more than once and could use a workaround to stop this from happening. So I've been trying to setup a libvirt hook to fork an instance of systemd-inhibit

Hello! I have two Samba servers (domain members) in cluster format to provide file shares, as follows: GlusterFS for data replication Heartbeat for HA Everything works fine... however I made a recent improvement (I think) which was the addition of CTDB for replication of Samba connections, just that, and nothing more. It worked and works but after that both nodes of the cluster started to lose

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 More information.. Another thing that indicates to me is CTDB and that several other Linux Domonio (not the same version of Samba) and Windows also do not present this problem (not with this frequency of 24 to 48 hours). Regards; Em qui., 23 de jan. de 2025 ?s 08:50, Carlos Alberto Panozzo Cunha < carlos.hollow at gmail.com> escreveu: > Hello! > > I have two Samba servers

As I see in your configuration you use smb.conf on the CTDB-Server. You should use the registry, because that's the way the configuration will replicate the configuration. CTDB stands for clustered trivial databases. The registry is a tdb-database. There are a lot more wrong configurations in your config. Take a look at my tutorial from sambaxp 2020

Hello all, I've some CTDB issue which I'm not sure where to start... I follow this guide by steve which is nice. The different on what have is that I don't have drbd running... Also I've 4 x GE which is all Connected to a switch with different ip but same subnet This is suppose to load balance the traffic as under samba dns, they all have the same name. I'm only planing 3

Hi! I am doing backups from a number of machines to an rsync server. For some time I was trying to come up with a solution, which would prevent users from peeking at each other's files, which are backed up. Finally, I've hacked rsync, introducing a new option "write only" for rsyncd.conf. When set to true, this option forbids the transfers from server to the client, thus solving

Yes, I saw that they are different I was just willing to test something similar. Actually, I'm searching for a Samba feature that allow transparent failover, or continuos availablity in a cluster setup (Samba + ctbd + gluster) Based on the following link my understanding is that such feature is not currently available in Samba:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, I'm trying to bring up a three node cluster using CTDB and SAMBA4 on a GlusterFS clustered file system. The filesystem itself seems to be working just fine, but CTDB doesn't seem happy. If I start a single node up: service ctdb start After about 10 seconds it becomes healthy, starts SAMBA and takes over all 3 IP addresses. However,

Hi there ? I seem to be having trouble wrapping my brain about the CTDB and ganesha configuration. I thought I had it figured out, but it doesn?t seem to be doing any checking of the nfs-ganesha service. I put nfs-ganesha-callout as executable in /etc/ctdb I create nfs-checks-ganesha.d folder in /etc/ctdb and in there I have 20.nfs_ganesha.check In my ctdbd.conf file I have: # Options to

Hi All, We're using CTDB to cluster protocols over a large SAN and have had some pain related to a bit of a design flaw: we store CTDB and protocol-specific accounting files (recovery locks, state files, etc) on the same filesystem that we're offering through CTDB itself. This makes our front-end services pretty intolerant of flapping in the back-end filesystem, which is obviously not

Hi, I'm happily progressing toward the successful setup of my two nodes samba cluster : cman, qdisk, clvm, gfs2, ctdb, samba, winbind, ad. And now, I'm in testing phase. When my cluster is up and running, I can transfer each ip address toward on node or the other, seamlessly. They can fence each other. But I still have one big issue : though they have been setup as clones, they

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 would like to ask, when the "vanished files" warning is a sign that something bad is happening somewhere. I know that the `rsync-no-vanished` script can silence the warning, but I am wondering whether this is a sane thing to do. My guess based on https://bugzilla.samba.org/show_bug.cgi?id=3653#c26 and https://bugzilla.samba.org/show_bug.cgi?id=10356 is that it's fine, but

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:

hello perl experts i am working with "ast-rad-acc.pl" from http://www.voip-info.org/tiki-index.php?page=PortaOne+Radius+auth i dont know why $cdr{'DNID'} and $cdr{'CALLERID'} under 'sub send_acc {' are empty. i m successfully connected with asterisk manager and when call i hangup my perl application is getting that all other thing are ok but i dont know why only

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