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

[ronnie sahlberg]

Maybe you are running a different smbd binary on that node?

Check with 'ls -l /proc/<smbd-pid>/exe' on both nodes.

This should give you the exact path to the binary that is running.
Verify that this is the same path on both nodes   and then check with
md5sum on the two nodes and verify that they are exactly the same.


On Wed, Dec 10, 2014 at 2:36 PM, ronnie sahlberg
<ronniesahlberg at gmail.com> wrote:
> On Wed, Dec 10, 2014 at 2:23 PM, Richard Sharpe
> <realrichardsharpe at gmail.com> wrote:
>> On Wed, Dec 10, 2014 at 10:48 AM, ronnie sahlberg
>> <ronniesahlberg at gmail.com> wrote:
>>> On Wed, Dec 10, 2014 at 1:45 PM, Richard Sharpe
>>>> Why is the process ctdb_reco holding on to the registry tdb?
>>>
>>> It is the recovery daemon. It has all tdbs open in case it need to
>>> read/write it during a recovery.
>>>
>>> Pick one of the smbd processes and check with
>>> ls -l /proc/<smbd-pid/fd
>>> that it too has /var/lib/ctdb/persistent/registry.tdb.1  open
>>> (and that it does not have a different  registry.tdb file open)
>>
>> On node 1, which is not the recovery master, and is the node I am
>> having problems with:
>>
>> smbd has this file open:
>>
>> lrwx------ 1 root root 64 Dec 10 10:29 3 -> /var/lib/samba/registry.tdb
>>
>> ctdb has this file open:
>>
>> lrwx------ 1 root root 64 Dec 10 10:31 19 ->
>> /var/lib/ctdb/persistent/registry.tdb.1
>>
>> an strace of net conf list does not show it accessing the ctdb socket
>> and does not show it opening registry.tdb.1
>>
>
> Ok,  so it seems that smbd is not using clustering/ctdb then and
> instead is using the local
> non-clustered tdb files : /var/lib/samba/registry.tdb
>
> This is definitely the problem why it is not working.   Now,   why is
> samba running in non-clustered mode using local tdb files?  that is a
> different question.
>
>
>
>> --
>> Regards,
>> Richard Sharpe
>> (何以解憂？唯有杜康。--曹操)