Collect comprehensive system information in Linux (based on sosreport and supportconfig)

Collect comprehensive system information in Linux (based on sosreport and supportconfig)

Log collection and analysis in Linux is a very important task. Generally, the vendor has its own commands, here I will list the common collection commands of two Linux vendors (RedHat Linux and SUSE Linux), which will facilitate the collection and comprehensive analysis of the system.

1. redhat-based Log collection
[Root @ openstack-01 etc] # sosreport
Sosreport (version 3.2)
This command will collect diagnostic and configuration information from
This CentOS Linux system and installed applications.
An archive containing the collected information will be generated in
/Var/tmp/sos. NUmfab and may be provided to a CentOS support
Representative.
Any information provided to CentOS will be treated in accordance
The published support policies ies:
Https://www.centos.org/
The generated archive may contain in data considered sensitive and its
Content shoshould be reviewed by the originating organization before being
Passed to any third party.
No changes will be made to system configuration.
Press ENTER to continue, or CTRL-C to quit.
Please enter your first initial and last name [openstack-01]:
Please enter the case id that you are generating this report for []:
Setting up archive...
Setting up plugins...
Running plugins. Please wait...
Running 114/114: yum...
[Plugin: openstack_swift] regex substitution failed for '/etc/swift/container. builder 'with: ''utf8'codec can't decode byte 0x80 in position 0: invalid start byte'
[Plugin: openstack_swift] regex substitution failed for '/etc/swift/container.ring.gz' with: ''utf8'codec can't decode byte 0x8b in position 1: invalid start byte'
Creating compressed archive...
Your sosreport has been generated and saved in:
/Var/tmp/sosreport-openstack-01-20160603071544.tar.xz
The checksum is: 757286aeba8b7ca78b0614547c4d58c9
Please send this file to your support representative.

2. Log collection based on SUSE Linux
Use the script suppconfig config-A to collect logs. The log path will exist in/var/log.
--
TESTDBO2:/tmp/tools/nmon # supportconfig-
========================================================== ============================================ Support Utilities- supportconfig Script Version: 2.25-197 Script Date: 2010 04 02 ============================================== ==========================================================
Gathering system information Data Directory:/var/log/nts_TESTDBO2_140226_1114
Basic Server Health Check... done RPM Database... done Basic Environment... done Basic Health Report... done System Modules... done Memory Details... done Disk I/O... done System Logs... done YaST Files... done Auditing... done Crash Info... done NTP... done PROC... done Boot Files... done SLERT... skipped Updates... done SMT... skipped Novell eDirectory... please Wait... skipped Novell LUM... skipped Novell NCP... skipped Novell NSS... skipped Novell DFS... skipped Novell SMS... skipped Novell NCS... skipped Novell AFP... skipped Novell CIFS... skipped HA Cluster... skipped OCFS2... skipped PAM... done LDAP... done CIMOM... done Open Files... done Environment... done ETC... done SYSCONFIG... done SYSFS... done System Daemons... done CRON... done... done UDEV... done LVM... please Wait... base Detail Done EVMS... skipped Software Raid... done Multipathing... done Networking... done Web... done InfiniBand... done DNS... done DHCP... done SLP... please Wait... services Done SSH... done iSCSI... done Samba... done NFS... done AUTOFS... done SAR Files... skipped AppArmor... done Xen... skipped X... done Printing... done SMART Disks... done Hardware... please Wait... done File System List... please Wait... done Supportability Analysis... please Wait... done
Creating Tar Ball
= [DONE] ============================================= ================================== Log file tar ball: /var/log/nts_TESTDBO2_140226_1114.tbz Log file size: 25 M Log file md5sum: 36a0aaee37b5174e29278544ac3e8f61
Please attach the log file tar ball to your open Service Request at the following URL: https://secure-support.novell.com/eService_enu
You can also upload the tar ball to ftp.novell.com/incoming, or just use supportconfig-ur, to upload the tar ball automatically.
If you cannot attach the tar ball to the SR, then email it to the engineer. ========================================================== ============================================= --

Then we can analyze the system based on the collected information.

This article permanently updates the link address: