similar to: CTDB doesn't restart samba

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

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

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

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

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

Hi, everyone, I setup two-node samba cluster with ctdb and glusterfs. When one node fails, another node can takeover ip and cifs sessions, so application can not breaks. Linux cifs client works fine when disable one node. However, it does not work under windows xp. I am copying a big file to samba share, meanwhile I disable the connected node, then copy break with "The specified network

Hi, I?ve setup a simple ctdb cluster. Actually copied the config file from an existing system. Thats what happens: Node 1, alone Number of nodes:2 pnn:0 10.0.0.1 OK (THIS NODE) pnn:1 10.0.0.2 DISCONNECTED|UNHEALTHY|INACTIVE Generation:1369816268 Size:1 hash:0 lmaster:0 Recovery mode:NORMAL (0) Recovery master:0 Node1, after start of ctdb on Node 2 Number of nodes:2 pnn:0

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

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

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

I suggest have a look in : https://bugzilla.samba.org/show_bug.cgi?id=12371 i think that wil help you. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Martin Schwenke > via samba > Verzonden: vrijdag 21 oktober 2016 11:46 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] CTDB and locking issues in

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

I did a new rsync and compiled ctdb new. This version did not establish a new config file!!!: /etc/sysconfig/ctdb. I had to use my old one. After starting ctdb recognizing that ctdb wants his state directory in /usr/local/var/ctdb/state I could not fix that in /etc/sysconfig/ctdb file. So I had do mkdir /usr/local/var/ctdb manually. After starting ctdb on both nodes all nodes rest unhealthy. And

> Interestingly I have a setup here for testing for rollout of S4 AD. > The file servers are in an AD domain and are running Sernet 4.4.5, so > one version older than production. I have tested the locking on these > and it works. The only difference I can find that in prod, > /etc/default/sernet-samba-ctdb contains these lines: > > CTDB_MANAGES_SAMBA=yes >

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 all We did some failover/failback tests on 2 nodes��A and B�� with architecture 'glusterfs + ctdb(public address) + nfs-ganesha'�� 1st: During write, unplug the network cable of serving node A ->NFS Client took a few seconds to recover to conitinue writing. After some minutes, plug the network cable of serving node A ->NFS Client also took a few seconds to recover