Comment 2 for bug 1734225

Revision history for this message
Thomas Smith (theitsmith) wrote :

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}
    CTDB_SERVICE_NMB=${CTDB_SERVICE_NMB:-nmbd}

instead of:

    CTDB_SERVICE_SMB=smbd
    CTDB_SERVICE_NMB=nmbd