Displaying 15 results from an estimated 15 matches similar to: "CTDB Samba 4.10 example?"
2014 Aug 23
2
CTDB 50.samba: ERROR: smb.conf cache create failed
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
2014 Jul 18
1
ctdb do not start nmbd if serving AD
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
2014 Aug 15
1
ctdb event script 50.samba does not start smbd
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 =
2014 Aug 16
1
CTDB: Failed to connect client socket to daemon.
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
2019 Jun 14
1
Update 4.10.2 to 4.10.4: Cant create files in subdirectorie anymore
You're totally right and after i rechecked my conf i've seen that i already set
vfs objects = acl_xattr gluster
in my share definition. I just played around with these options to see if it helps.
Neither combination made any difference so i guess my problem isnt related to the xattr module,
it could be related to the gluster module since i did'nt check what would happen if i'd use
2016 Oct 06
1
Ctdb and mdb
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:
2016 Oct 21
6
CTDB and locking issues in 4.4.6 (Classic domain)
>> 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.
2016 Oct 21
0
CTDB and locking issues in 4.4.6 (Classic domain)
> 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
>
2016 Oct 21
1
CTDB and locking issues in 4.4.6 (Classic domain)
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
2010 Aug 17
1
UID syncing issues with CTDB
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
2014 Oct 07
1
CDTB On Samba 4.1.12 As Member files 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
2016 Oct 20
2
CTDB and locking issues in 4.4.6 (Classic domain)
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
2019 Jun 14
1
Update 4.10.2 to 4.10.4: Cant create files in subdirectorie anymore
Hi everyone,
since i upgraded from 4.10.2 to 4.10.4 i can't write into subdirectories
of a share anymore.
This worked perfectly fine before i upgraded and also works again if i
downgrade.?
I think either something is fishy with the 'filename_convert_internal'
function of ".../source3/smbd/filename.c"
or my configuration needs to be adjusted for 4.10.4. I tried several
2018 Feb 01
2
Upgrading a ctdb cluster: samba not listening on TCP port 445
Hi all,
I try to update two clustered samba file servers. Right now samba 4.7.0
with ctdb is running on both of them. To update samba I stopped ctdb on
one of the servers, and compiled and installed samba 4.7.1 with:
./configure --with-cluster-support --with-shared-modules=idmap_tdb2,idmap_ad,vfs_glusterfs --with-systemd
Trying to start ctdb on the updated server fails with "
2012 May 24
0
Could not find node to take over public address
Hi,
we run ctdb with samba on SLES11. It was running for some month ok but
after an update of the system and ctdb it fails to run.
I tried to setup a new ctdb setup on two other nodes and it still fails
with the same error.
After startup the status is:
> ctdb status
> Number of nodes:2
> pnn:0 10.94.43.7 DISABLED
> pnn:1 10.94.43.8 DISABLED (THIS NODE)
>