search for: ctdb_service_winbind

...nning 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 CTDB_MANAGES_WINBIND=yes Whereas in the test environment they are: CTDB_SERVICE_WINBIND="sernet-samba-winbindd" CTDB_SERVICE_SMB="sernet-samba-smbd" I'm wondering if this is what's making the difference? Cheers, Alex -- This message is intended only for the addressee and may contain confidential information. Unless you are that person, you may not disc...

...der 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 > CTDB_MANAGES_WINBIND=yes > > Whereas in the test environment they are: > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > CTDB_SERVICE_SMB="sernet-samba-smbd" > > I'm wondering if this is what's making the difference? > > Cheers, > > Alex > > The above is not what I meant, apologies. In the prod cluster, these lines: CTDB_SERVICE_WINBIN...

...works. The only difference I can find that in prod, > > > /etc/default/sernet-samba-ctdb contains these lines: > > > > > > CTDB_MANAGES_SAMBA=yes > > > CTDB_MANAGES_WINBIND=yes > > > > > > Whereas in the test environment they are: > > > CTDB_SERVICE_WINBIND="sernet-samba-winbindd" > > > CTDB_SERVICE_SMB="sernet-samba-smbd" > > > > > > I'm wondering if this is what's making the difference? > > > The above is not what I meant, apologies. In the prod cluster, these > lines: > > &gt...

...N /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 Hear...

...es: files nisplus ctdb.conf: CTDB_RECOVERY_LOCK="/EDAPT/ctdb/CTDB_lock" CTDB_PUBLIC_INTERFACE=eth0 CTDB_PUBLIC_ADDRESSES=/etc/ctdb/public_addresses CTDB_MANAGES_SAMBA=no CTDB_SAMBA_CHECK_PORTS="445" CTDB_MANAGES_WINBIND=no CTDB_INIT_STYLE=redhat CTDB_SERVICE_SMB=smb CTDB_SERVICE_WINBIND=winbind ulimit -n 10000 CTDB_NODES=/etc/ctdb/nodes CTDB_DBDIR=/var/ctdb CTDB_DBDIR_PERSISTENT=/EDAPT/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/tmp/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_LOGFILE=/var/log/log.ctdb CTDB_DEBUGLEVEL=2

...c/ctdb/public_addresses CTDB_MANAGES_SAMBA=yes CTDB_SAMBA_SKIP_SHARE_CHECK=yes CTDB_NFS_SKIP_SHARE_CHECK=yes CTDB_MANAGES_WINBIND=yes CTDB_MANAGES_VSFTPD=no CTDB_MANAGES_ISCSI=no CTDB_MANAGES_NFS=no CTDB_MANAGES_HTTPD=no CTDB_SYSLOG=yes CTDB_DEBUGLEVEL=NOTICE CTDB_INIT_STYLE= CTDB_SERVICE_SMB=samba CTDB_SERVICE_WINBIND=winbind CTDB_NODES=/etc/ctdb/nodes CTDB_NOTIFY_SCRIPT=/etc/ctdb/notify.sh CTDB_DBDIR=/var/lib/ctdb CTDB_DBDIR_PERSISTENT=/var/lib/ctdb/persistent CTDB_EVENT_SCRIPT_DIR=/etc/ctdb/events.d CTDB_SOCKET=/var/lib/ctdb/ctdb.socket CTDB_TRANSPORT="tcp" CTDB_MONITOR_FREE_MEMORY=100 CTDB_START_AS_...

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

...rride from auto-detection. ## Type: string ## Default: nmb CTDB_SERVICE_NMB=nmb ## Description: Samba winbind services init script # The following is a winbind specific Samba init script / service that you # can override from auto-detection. ## Type: string ## Default: winbind CTDB_SERVICE_WINBIND=winbind # you may wish to raise the file descriptor limit for ctdb # use a ulimit command here. ctdb needs one file descriptor per # connected client (ie. one per connected client in Samba) # ulimit -n 10000 ## Description: This file enumerates all nodes of the cluster ## Type: string ##...