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 scriptstatus" shown "50.Samba - OK") so there could be a little misconfiguration in my following advices couse i did'nt look further into it yet. Anyways... heres what i did: ## IN /etc/ctdb/script.options ## (this was the most tricky thing for me since i use the sernet build) | CTDB_SAMBA_SKIP_SHARE_CHECK=yes # For me this is needed couse of the use of the vfs_glusterfs module. You may not need it. | CTDB_SERVICE_NMB=sernet-samba-nmbd | CTDB_SERVICE_SMB=sernet-samba-smbd | CTDB_SERVICE_WINBIND=sernet-samba-winbindd ## IN /etc/ctdb/commands.sh | ctdb event script enable legacy 50.samba | ctdb event script enable legacy 49.winbind ## IN /etc/ctdb/ctdb.conf | [cluster] | recovery lock = /pathTo/your/.ctdb/lockfile ## IN /etc/ctdb/nodes you only have to add your heartbeat IPs HeartbeatIPofNode1 HeartbeatIPofNode2 HeartbeatIPofNode3 HeartbeatIPofNodeN # EXAMPLE: | 192.168.2.111 | 192.168.2.112 ## IN /etc/ctdb/public_addresses FirstPublicIP/CIDR INTERFACE SecondPublicIP/CIDR INTERFACE ThirdPublicIP/CIDR INTERFACE # EXAMPLE: | 192.168.1.111/30 ens160 | 192.168.1.112/30 ens160 I hope this will help you getting your cluster to work. Regards Sascha Brutscher | Hello, | | from SAMBA 4.9/4.10 there was a big change regarding CTDB. Does anyone | have an example configuration, how to configure a CTDB cluster from | version 4.10? | | Is there someone who run CTDB with SAMBA 4.10? | | Best regards | | Micha
Hi Sascha, On 7/9/19 2:35 PM, Sascha Brutscher via samba wrote:> ## IN /etc/ctdb/script.options > ## (this was the most tricky thing for me since i use the sernet build) > | CTDB_SAMBA_SKIP_SHARE_CHECK=yes # For me this is needed couse of the > use of the vfs_glusterfs module. You may not need it. > | CTDB_SERVICE_NMB=sernet-samba-nmbd > | CTDB_SERVICE_SMB=sernet-samba-smbd > | CTDB_SERVICE_WINBIND=sernet-samba-winbinddthis configuration is not required. It's already included in the per-script configuration files in the sernet-samba packages, by default: # ls /etc/ctdb/events/legacy/*.options /etc/ctdb/events/legacy/49.winbind.options /etc/ctdb/events/legacy/50.samba.options> ## IN /etc/ctdb/commands.sh > | ctdb event script enable legacy 50.samba > | ctdb event script enable legacy 49.winbindIt is not required to store the commands.sh in the ctdb config directory. The commands.sh just provides some commands which you might like to run manually, when you convert your ctdb config to ctdb 4.10 or newer. This replaces the CTDB_MANAGES_* commands. Best regards, Bj?rn -- SerNet GmbH, Bahnhofsallee 1b, 37081 G?ttingen phone: 0551-370000-0, mailto:kontakt at sernet.de Gesch.F.: Dr. Johannes Loxen und Reinhild Jung AG G?ttingen: HR-B 2816 - http://www.sernet.de