similar to: ctdb patches in samba v4

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

https://bugzilla.samba.org/show_bug.cgi?id=5763 Summary: rsync not working at above url Product: rsync Version: 3.1.0 Platform: Other URL: http://ctdb.samba.org/download.html OS/Version: Linux Status: NEW Severity: blocker Priority: P3 Component: core AssignedTo: wayned@samba.org

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

Hi Jo?o, On Tue, 6 Aug 2019 14:54:32 +0100, Jo?o Ba?to via samba <samba at lists.samba.org> wrote: > I'm setting up a clustered environment on CentOS 7.6.1810 with > Samba 4.8.3-6.el7_6 and the corresponding ctdb package. I'm using FreeIPA > 4.6.4 as my auth backend. > > Currently I'm running into this bug > https://bugzilla.samba.org/show_bug.cgi?id=13465

Hi, What did I miss / do wrong? My config didn't work like on the below linked video: http://www.samba.org/~tridge/ctdb_movies/node_disable.html With my config, the copy process fails/breaks despite that the tesztxp PC successfully maps the other (samba) PC in case the first (samba) PC is out. In the samba logs (even at log level = 10) I didn't see any information that can help me solve

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

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

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 Benedikt, On Thu, 16 May 2019 10:32:51 +0200, Benedikt Kaleß via samba <samba at lists.samba.org> wrote: > 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

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 all, I'm setting up a clustered environment on CentOS 7.6.1810 with Samba 4.8.3-6.el7_6 and the corresponding ctdb package. I'm using FreeIPA 4.6.4 as my auth backend. Currently I'm running into this bug https://bugzilla.samba.org/show_bug.cgi?id=13465 however I would assume that it is fixed in the latest release (dated 29July 2019). It crashed once CTDB runs testparm to check the

Hi Micha, On Mon, 7 May 2018 15:46:50 +0200, Micha Ballmann <ballmann at uni-landau.de> wrote: > i'm still trying to find out what is the right path for ctdb.conf > (ubuntu 18.04, samba was compiled from source!!). > > When im trying to start CTDB without any config file, my log in > /usr/local/samba/var/log/log.ctdb shows me: > > 2018/05/07 12:56:44.363513

Hello, First and foremost, thanks *very* much for ctdb. It's a joy to use after banging around with other HA solutions. We're planning to use it to export Samba and NFS shares throughout campus. I'm having one problem with the NFS part though. When ctdbd first starts statd (we're using CTDB_MANAGES_NFS=yes), it does so without appending the stuff in the STATD_HOSTNAME variable

On Thu, 2 Nov 2017 12:17:56 -0700, Computerisms Corporation via samba <samba at lists.samba.org> wrote: > 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 > >

Ah, yes, thats it Ralph.. Good one. Then in the systemd.service file you need to add. [Service] Environment=PATH=$PATH:/usr/local/samba/bin > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Ralph Boehme via samba > Verzonden: dinsdag 3 maart 2020 10:13 > Aan: Micha Ballmann; Anoop C S > CC: samba at lists.samba.org >

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"

Changes in CTDB 2.5 =================== User-visible changes -------------------- * The default location of the ctdbd socket is now: /var/run/ctdb/ctdbd.socket If you currently set CTDB_SOCKET in configuration then unsetting it will probably do what you want. * The default location of CTDB TDB databases is now: /var/lib/ctdb If you only set CTDB_DBDIR (to the old default of