ctdb:banning: Improve debug message in ctdb_ban_node_event()

Make it more clear what happens when reading the logs.

Signed-off-by: Michael Adam <obnox@samba.org>
Reviewed-by: Amitay Isaacs <amitay@gmail.com>

diff --git a/ctdb/server/ctdb_banning.c b/ctdb/server/ctdb_banning.c
index 5b08b47ac8dde7a311c66e104dc5fb158f059d4f..9cd163645a17a6027f950688320334a53b5b81c4 100644 (file)
--- a/ctdb/server/ctdb_banning.c
+++ b/ctdb/server/ctdb_banning.c
@@ -42,7 +42,8 @@ static void ctdb_ban_node_event(struct tevent_context *ev,
 
        /* Make sure we were able to freeze databases during banning */
        if (!ctdb_db_all_frozen(ctdb)) {
-               DEBUG(DEBUG_ERR, ("Banning timed out, but still unable to freeze databases\n"));
+               DEBUG(DEBUG_ERR, ("Banning timed out, but not all databases "
+                                 "frozen yet - banning this node again.\n"));
                ctdb_ban_self(ctdb);
                return;
        }