similar to: CTDB: Failed to connect client socket to daemon.

Ubuntu 14.04. 2 node ctdb in an 4.1.11 AD domain with 4.1.11 member servers on each node. winbindd is present but nss and pam are controlled by sssd. All OK, except that the event script which starts samba is not working. smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER clustering = Yes ctdbd socket =

Ubuntu 14.04, ctdb 2.5.1 from the ubuntu package. samba 4.1.11 with cluster support from source. Error upon startup only. Restarting ctdb on that node clears the error. The other node with the same config is OK. Any ideas? Cheers, Steve smb.conf [global] workgroup = ALTEA realm = ALTEA.SITE security = ADS kerberos method = secrets and keytab netbios name = SMBCLUSTER disable netbios = Yes

ctdb 2.5.3 dual node file server with 4.1.9 serving AD domain Hi We have enabled the script at: /etc/cdb/events.d/50.samba but when we are the enabled node, it starts not only smbd but also nmbd. This doesn't make sense in an AD domain. I've tried disabling nmbd starting under openSUSE's systemd but ctdb overrides that, I've had a look at the script but can't decipher the bit

Hi We have installed a two node ctdb cluster using glusterfs it works fine, but we want that the users be able to find the server in the network section of windows explorer. We are using fedora 23 and nmb doesn't start with ctdb i tried the following change in /etc/ctdb/events.d/50.samba *) # Use redhat style as default:

Hi there, I use Samba 4.9 since its releaseday and also had some troubles first due to the lack of informations in the wiki. Anyways... after some try & error i got it working and since i run the Cluster (non-production environment) had no errors except CTDBs monitoring of the Samba process did'nt work as i would expect it (RPC-Server was dead but CTDB did'nt complain and "ctdb

On Sat, Apr 2, 2016 at 4:05 PM, Rowland penny <rpenny at samba.org> wrote: > I compile Samba myself and I use init files, I would rather have them than > the bloat systemd comes with. They are not complex if you understand bash > and are a lot easier to understand than all that systemd comes with. At first I felt the same way but the service files are starting to seem simpler. Yes,

>> You don't have smbd/smbstatus installed from a package in /usr/ and the >> other left over in /usr/local/, or similar? In that case, they could >> be getting their configurations from different places... >> >> peace & happiness, >> martin > Hi Martin, > > No, nothing like that. Installing the Sernet packages obsoletes the > distro ones.

Hi all, A while ago I posted about needing to access samba shares on the same machine that the samba server was running on. Someone posted a script to mount the shares and all was well till I upgraded my PC hadware and had a small accident :( I have tried modifing /etc/init.d/samba adding ... mount -t smbfs //127.0.0.1/common /mnt/samba/common -o

Hello together, > * Report your success/failure! > * Samba4 as a replicating domain controller is still developing rapidly, and we > like to hear from users about their successes and failures. While Samba4 is > still in rc state we would encourage you to report both your successes and > failures to the samba-technical mailing list on

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

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

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

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

Hello, 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 ctdbd[4503]: Failed to read nodes file "/usr/local/samba/etc/ctdb/nodes" 2018/05/07 12:56:44.363546 ctdbd[4503]: Failed to

Hi Alex, On Thu, 20 Oct 2016 14:28:38 +0100, Alex Crow via samba <samba at lists.samba.org> wrote: > > > > It appears that samba is still using local databases and not clustered > > databases. > > > > What does "ctdb getdbmap" list? Is locking.tdb a clustered database? > > Do you have "clustering = yes" in smb.conf on all the

Hello, at this time i want to install a CTDB Cluster with SAMBA 4.7.7 from SOURCE! I compiled samba as follow: |./configure| |--with-cluster-support ||--with-shared-modules=idmap_rid,idmap_tdb2,idmap_ad| The whole SAMBA enviroment is located in /usr/local/samba/. CTDB is located in /usr/local/samba/etc/ctdb. I guess right that the correct path of ctdbd.conf (node file, public address file

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

Very helpful. Thank you, Martin. I'd like to share the information below with you and solicit your fine feedback :-) I provide additional detail in case there is something else you feel strongly we should consider. We made some changes last night, let me share those with you. The error that is repeating itself and causing these failures is: Takeover run starting RELEASE_IP 10.200.1.230

Hi to all, I'm having a CTDB-Cluster with two nodes (both Ubuntu wit Sernet-packages 4.17.4). Now I want to replace one of the nodes. The first step was to bring a new node to the CTDB-Cluster. This time a Debian 11 but with the same sernet-packages (4.17.4). Adding the new node to /etc/ctdb/nodes at the end of the list. And the virtual IP to /etc/ctdb/public_addresses, also at the end