registry config not being updated on one of my clusters ... how do I troubleshoot this
realrichardsharpe at gmail.com
Wed Dec 10 10:27:08 MST 2014
On Tue, Dec 9, 2014 at 10:11 PM, Michael Adam <obnox at samba.org> wrote:
> 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.
However, this is the content of the smb.conf on both nodes, and
certainly on the one where the listing is not happening:
clustering = yes
config backend = registry
More information about the samba-technical