Bug 13064 - 'ctdb reloadnodes' ignores value of CTDB_NODES
Summary: 'ctdb reloadnodes' ignores value of CTDB_NODES
Alias: None
Product: Samba 4.1 and newer
Classification: Unclassified
Component: CTDB (show other bugs)
Version: 4.7.0
Hardware: x64 Linux
: P5 minor (vote)
Target Milestone: ---
Assignee: Amitay Isaacs
QA Contact: Samba QA Contact
Depends on:
Reported: 2017-09-29 18:11 UTC by Rolf Anders
Modified: 2018-12-05 00:53 UTC (History)
3 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Rolf Anders 2017-09-29 18:11:07 UTC
I've set CTDB_NODES in /etc/default/sernet-samba-ctdb to a non-default
path. ctdbd works fine, but 'ctdb reloadnodes' seems to ignore the
setting of CTDB_NODES and uses the default instead.  It fails with
'Failed to read nodes file "/etc/ctdb/nodes"'.

I'm using sernet-samba version 99:4.7.0-1 on Ubuntu 14.04 (ctdb version
Comment 1 Amitay Isaacs 2017-10-06 01:35:20 UTC
We are aware of this problem.  The main issue is that the ctdb tool does not read the configuration file.

However, you can work around this problem by setting an environment variable CTDB_NODES before running "ctdb reloadnodes".

If you run ctdb command as follows, it should do the right thing.

  # CTDB_NODES=/path/to/nodes/file ctdb reloadnodes
Comment 2 Rolf Anders 2017-10-06 14:34:39 UTC
I worked around it by making a symlink from /etc/ctdb/nodes to the actual
file. I just found it confusing that the path can be configured but the
ctdb command ignores it.
Comment 3 Martin Schwenke 2018-08-08 23:01:21 UTC
Hi Rolf,

In Samba 4.9 the location of the nodes file is no longer configurable (we have also removed many other configuration variables).  It must now go in the CTDB configuration directory.  However, the documentation mentions that if you want to put the file somewhere else you can create a symlink from the expected place to the place where you want it.  ;-)

Are you happy to close this?  Or should we wait until 4.9 is officially released?

Comment 4 Rolf Anders 2018-08-09 10:29:51 UTC
Hi Martin,

please close this bug.  Thanks!
Comment 5 Martin Schwenke 2018-12-05 00:53:49 UTC
Fixed in 4.9 by not providing a configurable socket location that is ignored
by the ctdb command.