registry config not being updated on one of my clusters ... how do I troubleshoot this

Michael Adam obnox at samba.org
Tue Dec 9 23:11:19 MST 2014


On 2014-12-10 at 07:09 +0100, Volker Lendecke wrote:
> On Wed, Dec 10, 2014 at 07:01:01AM +0100, Michael Adam wrote:
> > On 2014-12-10 at 06:55 +0100, Volker Lendecke wrote:
> > > On Tue, Dec 09, 2014 at 12:35:34PM -0800, Richard Sharpe wrote:
> > > > 
> > > > Curious.
> > > > 
> > > > When I do ctdb cattdb registry.tdb on both nodes, there is no
> > > > difference, but node 1 shows nothing when I do net conf list.
> > > 
> > > Missing include=registry in smb.conf on one node?
> > 
> > That would not affect "net conf list".
> > 
> > "net conf" is just a special path to part
> > of the registry irrespective of whether
> > that part is actually used as configuration.
> > (Much like cat and other tools would be used
> > to operate on a smb.conf.)
> 
> But a missing "clustering=yes" would affect net conf list...

It would, because "net conf list" lists the contents of the
smbconf key from registry.tdb. And "clustering = yes" changes
how registry is accessed - as local tdb file or as clustered
database via ctdb.

Michael
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20141210/fd0072e9/attachment.pgp>


More information about the samba-technical mailing list