1SSSCTL(8) SSSD Manual pages SSSCTL(8)
2
3
4
6 sssctl - SSSD control and status utility
7
9 sssctl COMMAND [options]
10
12 sssctl provides a simple and unified way to obtain information about
13 SSSD status, such as active server, auto-discovered servers, domains
14 and cached objects. In addition, it can manage SSSD data files for
15 troubleshooting in such a way that is safe to manipulate while SSSD is
16 running.
17
19 To list all available commands run sssctl without any parameters. To
20 print help for selected command run sssctl COMMAND --help.
21
23 Those options are available with all commands.
24
25 --debug LEVEL
26 SSSD supports two representations for specifying the debug level.
27 The simplest is to specify a decimal value from 0-9, which
28 represents enabling that level and all lower-level debug messages.
29 The more comprehensive option is to specify a hexadecimal bitmask
30 to enable or disable specific levels (such as if you wish to
31 suppress a level).
32
33 Currently supported debug levels:
34
35 0, 0x0010: Fatal failures. Anything that would prevent SSSD from
36 starting up or causes it to cease running.
37
38 1, 0x0020: Critical failures. An error that doesn't kill SSSD, but
39 one that indicates that at least one major feature is not going to
40 work properly.
41
42 2, 0x0040: Serious failures. An error announcing that a particular
43 request or operation has failed.
44
45 3, 0x0080: Minor failures. These are the errors that would
46 percolate down to cause the operation failure of 2.
47
48 4, 0x0100: Configuration settings.
49
50 5, 0x0200: Function data.
51
52 6, 0x0400: Trace messages for operation functions.
53
54 7, 0x1000: Trace messages for internal control functions.
55
56 8, 0x2000: Contents of function-internal variables that may be
57 interesting.
58
59 9, 0x4000: Extremely low-level tracing information.
60
61 10, 0x10000: Even more low-level libldb tracing information. Almost
62 never really required.
63
64 To log required bitmask debug levels, simply add their numbers
65 together as shown in following examples:
66
67 Example: To log fatal failures, critical failures, serious failures
68 and function data use 0x0270.
69
70 Example: To log fatal failures, configuration settings, function
71 data, trace messages for internal control functions use 0x1310.
72
73 Note: The bitmask format of debug levels was introduced in 1.7.0.
74
75 Default: 0x0070 (i.e. fatal, critical and serious failures;
76 corresponds to setting 2 in decimal notation)
77
79 sssd(8), sssd.conf(5), sssd-ldap(5), sssd-krb5(5), sssd-simple(5),
80 sssd-ipa(5), sssd-ad(5), sssd-files(5), sssd-sudo(5), sssd-session-
81 recording(5), sss_cache(8), sss_debuglevel(8), sss_obfuscate(8),
82 sss_seed(8), sssd_krb5_locator_plugin(8), sss_ssh_authorizedkeys(8),
83 sss_ssh_knownhostsproxy(8), sssd-ifp(5), pam_sss(8). sss_rpcidmapd(5)
84 sssd-systemtap(5)
85
87 The SSSD upstream - https://github.com/SSSD/sssd/
88
89
90
91SSSD 07/04/2022 SSSCTL(8)