similar to: CTDB issues with Windows XP clients

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

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

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

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

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? > >> So, in that case, I'm assuming from your comments that it is no worry >> that the mmap test does not

hello folks. congrats on samba 3.2 it's an awesome release. i'm trying to take advantage of the parallel cifs capabilities of this release. lustre (too complex) and gpfs (not free) at not available to me right now, so i'm using gfs v2 and iscsi as my storage building blocks. i'm running 3.2 on centos 5.2. everything is configured and i compiled samba4 to use smbtorture,

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

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

greetings, trying to follow tridge's failover process at http://samba.org/~tridge/ctdb_movies/node_disable.html I encounter this error. oss02:~ # smbstatus -np Processing section "[homes]" Processing section "[profiles]" Processing section "[users]" Processing section "[groups]" Processing section "[local]" Processing section

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 Max, On Tue, 1 Oct 2019 18:57:43 +0000, Max DiOrio via samba <samba at lists.samba.org> wrote: > 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

How did you mount your cephfs filesystem? Am 18. September 2018 20:34:25 MESZ schrieb David C via samba <samba at lists.samba.org>: >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

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

Ubuntu 14.04, ctdb 2.5.3, samba 4.1.11. CTDB is working with IP takeover between the 2 nodes. The machine is joined to the domain. Any help with the following errors would be most gratefully received. 1. connect to socket error: ctdb status 2014/08/16 15:32:03.248034 [23255]: client/ctdb_client.c:267 Failed to connect client socket to daemon. Errno:Connection refused(111) common/cmdline.c:156

As soon as I made the configuration change and restarted CTDB, it crashes. Oct 2 11:05:14 hq-6pgluster01 systemd: Started CTDB. Oct 2 11:05:21 hq-6pgluster01 systemd: ctdb.service: main process exited, code=exited, status=1/FAILURE Oct 2 11:05:21 hq-6pgluster01 ctdbd_wrapper: connect() failed, errno=111 Oct 2 11:05:21 hq-6pgluster01 ctdbd_wrapper: Failed to connect to CTDB daemon

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:

Martin - thank you for this. I don't know why I couldn't find any of this information anywhere. How long has this change been in place, every website I see about configuring nfs-ganesha with ctdb shows the old information, not the new. Do I need to enable the legacy 06.nfs 60.nfs files when using ganesha? I assume no. ?On 10/1/19, 5:46 PM, "Martin Schwenke" <martin at

Hi Marin - again thank you for the help. I can't believe I coundn't find any info about this big configuration change. Even the Samba WIKI doesn't really spell this out at all in instructs you to use ctdbd.conf. Do I need to enable the 20.nfs_ganesha.check script file at all, or will the config itself take care of that? Also, are there any recommendations on which nfs-checks.d