s3:locking: log g_lock_dump() error in locking_tdb_data_fetch() at level 0

This should never fail without notice...

Note we already checked for NT_STATUS_NOT_FOUND before.

BUG: https://bugzilla.samba.org/show_bug.cgi?id=15125

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Jeremy Allison <jra@samba.org>

diff --git a/source3/locking/share_mode_lock.c b/source3/locking/share_mode_lock.c
index 8df51a985894bfcf5635ebdf976f832313b0e75e..4aa11e2d097395a51f068b83d51083a9d428242f 100644 (file)
--- a/source3/locking/share_mode_lock.c
+++ b/source3/locking/share_mode_lock.c
@@ -500,7 +500,8 @@ static NTSTATUS locking_tdb_data_fetch(
                goto done;
        }
        if (!NT_STATUS_IS_OK(status)) {
-               DBG_DEBUG("g_lock_dump failed: %s\n", nt_errstr(status));
+               DBG_ERR("g_lock_dump failed: %s\n",
+                       nt_errstr(status));
                return status;
        }
        if (state.datalen == 0) {