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

[Richard Sharpe]

On Wed, Dec 10, 2014 at 10:04 AM, ronnie sahlberg
<ronniesahlberg at gmail.com> wrote:
> You have a smbd binary that supports clustering on both nodes ?

Yes, because I installed from the same RPMs on both nodes (and another
two nodes that do both work.)

> On Wed, Dec 10, 2014 at 12:27 PM, Richard Sharpe
> <realrichardsharpe at gmail.com> wrote:
>> 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:
>>
>> [global]
>>         clustering = yes
>>         config backend = registry
>>
>>
>>
>> --
>> Regards,
>> Richard Sharpe
>> (何以解憂？唯有杜康。--曹操)



-- 
Regards,
Richard Sharpe
(何以解憂？唯有杜康。--曹操)