1sos(1) General Commands Manual sos(1)
2
3
4
6 sos - A unified tool for collecting system logs and other debug infor‐
7 mation
8
10 sos component [options]
11
12
14 sos is a diagnostic data collection utility, used by system administra‐
15 tors, support representatives, and the like to assist in troubleshoot‐
16 ing issues with a system or group of systems.
17
18 The most well known function is sos report or sosreport as it was pre‐
19 viously known.
20
21 An sos archive is typically requested by support organizations to col‐
22 lect baseline configuration and system data from which to begin the
23 troubleshooting process.
24
25
26
28 sos supports several subcommands or components. Each provides a differ‐
29 ent set of information for the user. Supported components are as fol‐
30 lows
31
32
33 report Report generates an archive of system information including con‐
34 figuration files and command output. Information included in the
35 report is based upon plugins that are activated automatically
36 when certain criteria, such as installed packages, files, ser‐
37 vices, or system architecture is detected.
38
39 See sos report --help and man sos-report for more information.
40
41 May also be invoked via the alias rep or the deprecated command
42 sosreport.
43
44
45 collect
46 Collect is used to capture reports on multiple systems simulta‐
47 neously. These systems can either be defined by the user at the
48 command line and/or defined by clustering software that exists
49 either on the local system or on a "master" system that is able
50 to inform about other nodes in the cluster.
51
52 When running collect, sos report will be run on the remote
53 nodes, and then the resulting archives will be copied from those
54 nodes to the local system running sos collect. Archives are then
55 removed from the remote systems.
56
57 See sos collect --help and man sos-collect for more information.
58
59 May also be invoked via the alias sos collector or the depre‐
60 cated command sos-collector.
61
62
63 clean|cleaner|mask
64 This subcommand takes input of either 1) an sosreport tarball,
65 2) a collection of sosreport tarballs such as from collect, or
66 3) the unpackaged directory of an sosreport and obfuscates po‐
67 tentially sensitive system information that is not covered by
68 the standard postprocessing of sos report.
69
70 Such data includes IP addresses, networks, MAC addresses, and
71 more. Data obfuscated by this command will remain consistent
72 throughout the report and across reports provided in the same
73 invocation. Additionally, care is taken to maintain network
74 topology relationships between matched data items.
75
76 See sos clean --help and man sos-clean for more information.
77
78 May be invoked via either sos clean, sos cleaner, sos mask, or
79 via the --clean, --cleaner or --mask options for report and
80 collect.
81
82
84 sos components provide their own set of options, however the following
85 are available to be set across all components.
86
87 --batch Do not prompt interactively, user will not be prompted for any
88 data
89
90 --encrypt-key KEY
91 Encrypts the resulting archive that sosreport produces using
92 GPG. KEY must be an existing key in the user's keyring as GPG
93 does not allow for keyfiles. KEY can be any value accepted by
94 gpg's 'recipient' option.
95
96 Note that the user running sosreport must match the user owning
97 the keyring from which keys will be obtained. In particular this
98 means that if sudo is used to run sosreport, the keyring must
99 also be set up using sudo (or direct shell access to the ac‐
100 count).
101
102 Users should be aware that encrypting the final archive will re‐
103 sult in sos using double the amount of temporary disk space -
104 the encrypted archive must be written as a separate, rather than
105 replacement, file within the temp directory that sos writes the
106 archive to. However, since the encrypted archive will be the
107 same size as the original archive, there is no additional space
108 consumption once the temporary directory is removed at the end
109 of execution.
110
111 This means that only the encrypted archive is present on disk
112 after sos finishes running.
113
114 If encryption fails for any reason, the original unencrypted ar‐
115 chive is preserved instead.
116
117 --encrypt-pass PASS
118 The same as --encrypt-key, but use the provided PASS for symmet‐
119 ric encryption rather than key-pair encryption.
120
121 --config-file CONFIG
122 Specify alternate configuration file.
123
124 -s, --sysroot SYSROOT
125 Specify an alternate root file system path.
126
127 --tmp-dir DIRECTORY
128 Specify alternate temporary directory to copy data during execu‐
129 tion.
130
131 --threads THREADS
132 Specify the number of threads sosreport will use for concur‐
133 rency. Defaults to 4.
134
135 -v, --verbose
136 Increase logging verbosity. May be specified multiple times to
137 enable additional debugging messages.
138
139 -q, --quiet
140 Only log fatal errors to stderr.
141
142 -z, --compression-type {auto|xz|gzip}
143 Compression type to use when compression the final archive out‐
144 put
145
146 --help Display usage message.
147
149 Jake Hunsaker <jhunsake@redhat.com>
150
152 See AUTHORS file in the package documentation.
153
154
155
156 April 2020 sos(1)