I ran into this problem as well, and the solution (editing /etc/default/ctdb) does resolve the issue.
Note, too, that this issue will prevent a CTDB cluster (or at least the problem node) from coming online (i.e. indicating a status of "HEALTHY") until the mentioned settings are updated.
One thing I would adjust (versus what the OP indicated) is changing the related variables in 50.samba to:
I ran into this problem as well, and the solution (editing /etc/default/ctdb) does resolve the issue.
Note, too, that this issue will prevent a CTDB cluster (or at least the problem node) from coming online (i.e. indicating a status of "HEALTHY") until the mentioned settings are updated.
One thing I would adjust (versus what the OP indicated) is changing the related variables in 50.samba to:
CTDB_ SERVICE_ SMB=${CTDB_ SERVICE_ SMB:-smbd} SERVICE_ NMB=${CTDB_ SERVICE_ NMB:-nmbd}
CTDB_
instead of:
CTDB_ SERVICE_ SMB=smbd SERVICE_ NMB=nmbd
CTDB_