1SSS_DEBUGLEVEL(8)              SSSD Manual pages             SSS_DEBUGLEVEL(8)
2
3
4

NAME

6       sss_debuglevel - change debug level while SSSD is running
7

SYNOPSIS

9       sss_debuglevel [options] NEW_DEBUG_LEVEL
10

DESCRIPTION

12       sss_debuglevel changes debug level of SSSD monitor and providers to
13       NEW_DEBUG_LEVEL while SSSD is running.
14

OPTIONS

16       -c,--config
17           Specify a non-default config file. The default is
18           /etc/sssd/sssd.conf. For reference on the config file syntax and
19           options, consult the sssd.conf(5) manual page.
20
21       NEW_DEBUG_LEVEL
22           SSSD supports two representations for specifying the debug level.
23           The simplest is to specify a decimal value from 0-9, which
24           represents enabling that level and all lower-level debug messages.
25           The more comprehensive option is to specify a hexadecimal bitmask
26           to enable or disable specific levels (such as if you wish to
27           suppress a level).
28
29           Please note that each SSSD service logs into its own log file. Also
30           please note that enabling “debug_level” in the “[sssd]” section
31           only enables debugging just for the sssd process itself, not for
32           the responder or provider processes. The “debug_level” parameter
33           should be added to all sections that you wish to produce debug logs
34           from.
35
36           In addition to changing the log level in the config file using the
37           “debug_level” parameter, which is persistent, but requires SSSD
38           restart, it is also possible to change the debug level on the fly
39           using the sss_debuglevel(8) tool.
40
41           Currently supported debug levels:
42
43
44           0, 0x0010: Fatal failures. Anything that would prevent SSSD from
45           starting up or causes it to cease running.
46
47
48           1, 0x0020: Critical failures. An error that doesn´t kill the SSSD,
49           but one that indicates that at least one major feature is not going
50           to work properly.
51
52
53           2, 0x0040: Serious failures. An error announcing that a particular
54           request or operation has failed.
55
56
57           3, 0x0080: Minor failures. These are the errors that would
58           percolate down to cause the operation failure of 2.
59
60
61           4, 0x0100: Configuration settings.
62
63
64           5, 0x0200: Function data.
65
66
67           6, 0x0400: Trace messages for operation functions.
68
69
70           7, 0x1000: Trace messages for internal control functions.
71
72
73           8, 0x2000: Contents of function-internal variables that may be
74           interesting.
75
76
77           9, 0x4000: Extremely low-level tracing information.
78
79           To log required bitmask debug levels, simply add their numbers
80           together as shown in following examples:
81
82
83           Example: To log fatal failures, critical failures, serious failures
84           and function data use 0x0270.
85
86
87           Example: To log fatal failures, configuration settings, function
88           data, trace messages for internal control functions use 0x1310.
89
90
91           Note: The bitmask format of debug levels was introduced in 1.7.0.
92
93
94           Default: 0
95

SEE ALSO

97       sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5),
98       sssd-ipa(5), sssd-ad(5), sssd-sudo(5), sss_cache(8), sss_debuglevel(8),
99       sss_groupadd(8), sss_groupdel(8), sss_groupshow(8), sss_groupmod(8),
100       sss_useradd(8), sss_userdel(8), sss_usermod(8), sss_obfuscate(8),
101       sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8),
102       sss_ssh_knownhostsproxy(8), sssd-ifp(5), pam_sss(8).  sss_rpcidmapd(5)
103

AUTHORS

105       The SSSD upstream - http://fedorahosted.org/sssd
106
107
108
109SSSD                              01/15/2019                 SSS_DEBUGLEVEL(8)
Impressum