80a9c398f47bc9cca585e42eb1a6f236d337b385Stephen Gallagher SSSD supports two representations for specifying the debug level. The
80a9c398f47bc9cca585e42eb1a6f236d337b385Stephen Gallagher simplest is to specify a decimal value from 0-9, which represents
80a9c398f47bc9cca585e42eb1a6f236d337b385Stephen Gallagher enabling that level and all lower-level debug messages. The more
80a9c398f47bc9cca585e42eb1a6f236d337b385Stephen Gallagher comprehensive option is to specify a hexadecimal bitmask to enable or
80a9c398f47bc9cca585e42eb1a6f236d337b385Stephen Gallagher disable specific levels (such as if you wish to suppress a level).
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek Please note that each SSSD service logs into its own log
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek file. Also please note that enabling <quote>debug_level</quote>
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek in the <quote>[sssd]</quote> section only enables debugging just
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek for the sssd process itself, not for the responder or provider
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek processes. The <quote>debug_level</quote> parameter should be
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek added to all sections that you wish to produce debug logs from.
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek In addition to changing the log level in the config file using
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek the <quote>debug_level</quote> parameter, which is persistent, but
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek requires SSSD restart, it is also possible to change the debug level
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek on the fly using the
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek <citerefentry>
86bbaa25fd393f9f5c76750f3375778afdac51e4Jakub Hrozek </citerefentry>
930b8d8442c3ee88ad088d45e744510a5f815187Pavel Březina Currently supported debug levels:
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher Fatal failures. Anything that would prevent SSSD from starting up or
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher causes it to cease running.
f5d3f4304a767f20484c5a97012720e272a9a022Pavel Březina Critical failures. An error that doesn't kill SSSD, but one that
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher indicates that at least one major feature is not going to work
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher <emphasis>0x0040</emphasis>: Serious failures. An error announcing
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher that a particular request or operation has failed.
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher <emphasis>0x0080</emphasis>: Minor failures. These are the errors that
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher would percolate down to cause the operation failure of 2.
930b8d8442c3ee88ad088d45e744510a5f815187Pavel Březina <emphasis>0x0100</emphasis>: Configuration settings.
930b8d8442c3ee88ad088d45e744510a5f815187Pavel Březina <emphasis>0x0400</emphasis>: Trace messages for operation functions.
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher <emphasis>0x1000</emphasis>: Trace messages for internal control
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher <emphasis>0x2000</emphasis>: Contents of function-internal variables
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher that may be interesting.
930b8d8442c3ee88ad088d45e744510a5f815187Pavel Březina <emphasis>0x4000</emphasis>: Extremely low-level tracing information.
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher To log required bitmask debug levels, simply add their numbers together
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher as shown in following examples:
930b8d8442c3ee88ad088d45e744510a5f815187Pavel Březina <emphasis>Example</emphasis>: To log fatal failures, critical failures,
930b8d8442c3ee88ad088d45e744510a5f815187Pavel Březina serious failures and function data use 0x0270.
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher <emphasis>Example</emphasis>: To log fatal failures, configuration
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher settings, function data, trace messages for internal control functions
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher <emphasis>Note</emphasis>: The bitmask format of debug levels was
06ba148a64e1e6ed0251332092a4b6a363ee4360Stephen Gallagher introduced in 1.7.0.