Contents of ctdb nodes file reverting back
Steve French
smfrench at gmail.com
Mon Jan 23 20:42:18 UTC 2017
One of our testers noted a case where /etc/ctdb/nodes file 'lost' an
entry, and I do see a log entry on the master about reloading the
recovery file ("Reload nodes file from recovery daemon") - which at
first sounds suspicious but when I looked at this code, I don't see
ctdb replacing/changing the contents of /etc/ctdb/nodes file just
reloading the existing /etc/ctdb/nodes file. Is there any case where
ctdb recovery would alter the contents of the file /etc/ctdb/nodes?
Otherwise I was leaning toward simultaneous update of the nodes file
(outside Samba) as the culprit. The excerpt from the ctdb log on the
recovery master is:
2017/01/23 13:10:48.215785 [31112]: Starting CTDBD (Version
4.5.4-GIT-33e267b) as PID: 31112
2017/01/23 13:10:48.287553 [31112]: 10.interface: No public addresses
file found. Nothing to do for 10.interfaces
2017/01/23 13:10:48.459866 [31112]: 00.ctdb: Set TDBMutexEnabled to 1
2017/01/23 13:10:50.917093 [31112]: DB Attach to database registry.tdb
deferred for client with pid:31711 since node is in recovery mode.
2017/01/23 13:10:51.665780 [recoverd:31283]: recovery: set recovery
mode to ACTIVE
2017/01/23 13:10:51.863907 [recoverd:31283]: recovery: start_recovery
event finished
2017/01/23 13:10:51.863991 [recoverd:31283]: recovery: updated VNNMAP
2017/01/23 13:10:51.864021 [recoverd:31283]: recovery: 0 of 0
databases recovered
2017/01/23 13:10:51.864064 [recoverd:31283]: recovery: set recovery
mode to NORMAL
2017/01/23 13:10:52.053491 [recoverd:31283]: recovery: recovered event finished
2017/01/23 13:10:52.256587 [recoverd:31283]: Resetting ban count to 0
for all nodes
2017/01/23 13:10:52.872819 [31112]: Vacuuming is disabled for
persistent database registry.tdb
2017/01/23 13:10:52.911509 [31112]: Vacuuming is disabled for
persistent database secrets.tdb
2017/01/23 13:10:52.933244 [31112]: Vacuuming is disabled for
persistent database passdb.tdb
2017/01/23 13:10:52.995871 [31112]: Vacuuming is disabled for
persistent database group_mapping.tdb
2017/01/23 13:10:53.015813 [31112]: Vacuuming is disabled for
persistent database account_policy.tdb
2017/01/23 13:10:55.786692 [recoverd:31283]:
../ctdb/server/ctdb_recoverd.c:1622 Reload nodes file from recovery
daemon
2017/01/23 13:11:01.730541 [recoverd:31283]: recovery: set recovery
mode to ACTIVE
2017/01/23 13:11:01.964806 [recoverd:31283]: recovery: start_recovery
event finished
--
Thanks,
Steve
More information about the samba-technical
mailing list