msg: hexdump bad messages at debug level 1 (not 30)

These are rare, and when they do happen, we want to see them in the
logs.

Signed-off-by: Sage Weil <sage@redhat.com>

diff --git a/src/common/config_opts.h b/src/common/config_opts.h
index 310d432e1754be4e5ec71d600e8bba9c2d566195..369737bc92ca5a3f2b0e0a9df5236d66ba8428eb 100644 (file)
--- a/src/common/config_opts.h
+++ b/src/common/config_opts.h
@@ -136,7 +136,7 @@ OPTION(ms_inject_delay_max, OPT_DOUBLE, 1)         // seconds
 OPTION(ms_inject_delay_probability, OPT_DOUBLE, 0) // range [0, 1]
 OPTION(ms_inject_internal_delays, OPT_DOUBLE, 0)   // seconds
 OPTION(ms_dump_on_send, OPT_BOOL, false)           // hexdump msg to log on send
-OPTION(ms_dump_corrupt_message_level, OPT_INT, 30)  // debug level to hexdump undecodeable messages at
+OPTION(ms_dump_corrupt_message_level, OPT_INT, 1)  // debug level to hexdump undecodeable messages at
 
 OPTION(inject_early_sigterm, OPT_BOOL, false)