[Samba] SAMBA & CTDB Configuration Issue using LDAP as back end.

[Gerry George]

On Wed, Jun 4, 2014 at 1:03 AM, Volker Lendecke <Volker.Lendecke at sernet.de>
wrote:

> On Tue, Jun 03, 2014 at 05:28:17PM -0400, Gerry George wrote:
> > I have tried the following:
> >
> >
> >    - stop CTDB (and cluster services) on both nodes
> >    - stop SAMBA
> >    - edit /etc/samba/smb.conf to reflect teh desired passdb backend
> entry.
> >    - synchronize both systems with the edited smb.conf file
> >    - copy the smb.conf file to  /etc/ctdb/state/samba/smb.conf.cache
> >    - reboot both server & start all services
> >
> > Check files - still saying
> >
> > passdb backend = tdbsam
> > idmap backend = tdb2
>
> Samba does not modify the smb.conf. There must be other
> software on your system doing this. Please contact your
> system vendor about what this can be.
>
> With best regards,
>
> Volker Lendecke
>
> --
>

I think it is CTDB doing the modification, as it inserts the following stub
at the top of the smb.conf file, which includes the troublesome "passdb
backend" line:

# CTDB-RA: Begin auto-generated section (do not change below)
passdb backend = tdbsam
 clustering = yes
idmap backend = tdb2
ctdbd socket = /var/lib/ctdb/ctdb.socket
 fileid:algorithm = fsid
# CTDB-RA: End auto-generated section (do not change above)


This line is inserted into the smb.conf file of the active node, and
removed once that node becomes inactive.  It also (correctly) removes other
references to passdb/idmap anywhere else in the file.

Hence the reason why I think (thought) it was a CTDB issue (as opposed to a
SAMBA).  Are you saying that this is not the direct action of the CTDB
Cluster software? (I am using SLES 11 SP3).


Thanks again.

George-G