Shulou(Shulou.com)06/01 Report--

This article will explain in detail how to use xsos on Linux. The editor thinks it is very practical, so I share it for you as a reference. I hope you can get something after reading this article.

Sosreport

The sosreport command is a tool that collects a large amount of configuration details, system information, and diagnostic information from running systems, especially RHEL and OEL systems. It can help technical support engineers analyze the system in many ways.

This report contains a great deal of information about the system Such as boot information, file system, memory, hostname, installed RPM, system IP, network details, operating system version, installed kernel, loaded kernel module, open file list, PCI device list, mount point and its details, running process information, process tree output, system routing, all configuration files located in / etc folder And all log files located in the / var folder.

This will take some time to generate the report, depending on your system installation and configuration.

When finished, sosreport will generate a compressed archive file in the / tmp directory.

Xsos

Xsos is a tool that helps users easily read sosreport on Linux systems. On the other hand, we can say that it is the sosreport examiner.

It can immediately summarize system information from sosreport or running systems.

Xsos will try to simplify, parse, calculate, and format data from dozens of files (and commands) to give you a detailed overview of the system.

You can summarize the system information immediately by running the following command.

# curl-Lo. / xsos bit.ly/xsos-direct; chmod + x. / xsos;. / xsos- ya

How to install xsos on Linux

We can easily install xsos using the following two methods.

If you are looking for a cutting-edge version of *. Use the following steps:

# curl-Lo / usr/local/bin/xsos bit.ly/xsos-direct# chmod + x / usr/local/bin/xsos

Here are the recommended ways to install xsos. It will install xsos from the rpm file.

# how yum install http://people.redhat.com/rsawhill/rpms/latest-rsawaroha-release.rpm# yum install xsos uses xsos on Linux

Once you have installed xsos through one of the above methods. Simply run the xsos command without any options, and they display basic information about the system.

# xsos OS Hostname: CentOS7.2daygeek.com Distro: [redhat-release] CentOS Linux release 7.6.1810 (Core) [centos-release] CentOS Linux release 7.6.1810 (Core) [os-release] CentOS Linux 7 (Core) 7 (Core) RHN: (missing) RHSM: (missing) YUM: 2 enabled plugins: fastestmirror Langpacks Runlevel: N5 (default graphical) SELinux: enforcing (default enforcing) Arch: mach=x86_64 cpu=x86_64 platform=x86_64 Kernel: Booted kernel: 3.10.0-957.el7.x86_64 GRUB default: 3.10.0-957.el7.x86_64 Build version: Linux version 3.10.0-957.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8. 5-36) (GCC) # 1 SMP Thu Nov 8 23:39:32 UTC 2018 Booted kernel cmdline: root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8 GRUB default kernel cmdline: root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8 Taint-check: 0 (kernel untainted)-Sys time: Sun May 12 10:05:21 CDT 2019 Boot time: Sun May 12 09:50:20 CDT 2019 (epoch: 1557672620) Time Zone: America/Chicago Uptime: 15 min 1 user LoadAvg: [1 CPU] 0.00 (0), 0.04 (4), 0.09 (9) / proc/stat: 2 procs_blocked: 0 processes [Since boot]: 6423 cpu [Utilization since boot]: us 1%, ni 0%, sys 1%, idle 99%, iowait 0%, irq 0%, sftirq 0%, steal 0% how to use the xsos command to view the generated SOSReport output in Linux?

We need a SOSReport to read further using the xsos command.

Yes, I have generated a SOSReport with the following file.

# ls-lls-lh / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa.tar.xz9.8M-rw-. 1 root root 9.8m May 12 10:13 / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa.tar.xz

Run the following command to unlock it.

# tar xf sosreport-CentOS7-01-1005-2019-05-12-pomeqsa.tar.xz

To see all the information, run xsos with the-an or-- all switch:

# xsos-- all / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa

To view BIOS information, run xsos with the-b or-- bios switch.

# xsos-- bios / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaDMIDECODE BIOS: Vend: innotek GmbH Vers: VirtualBox Date: 12System 01BIOS Rev: FW Rev: System: Mfr: innotek GmbH Prod: VirtualBox Vers: 1.2Ser: 0 UUID: 002f47b8-2af2-48f5-be1d-67b67e03514c CPU: 0 of 0 CPU sockets populated, 0 cores/0 threads per CPU 0 total cores 0 total threads Mfr: Fam: Freq: Vers: Memory: Total: 0 MiB (0 GiB) DIMMs: 0 of 0 populated MaxCapacity: 0 MiB (0 GiB / 0.00 TiB)

To view basic system information, such as hostname, distribution, SELinux, kernel information, uptime, and so on, run xsos using the-o or-- os switch.

# xsos-- os / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaOS Hostname: CentOS7.2daygeek.com Distro: [redhat-release] CentOS Linux release 7.6.1810 (Core) [centos-release] CentOS Linux release 7.6.1810 (Core) [os-release] CentOS Linux 7 (Core) 7 (Core) RHN: (missing) RHSM: (missing) YUM: 2 enabled plugins: fastestmirror Langpacks SELinux: enforcing (default enforcing) Arch: mach=x86_64 cpu=x86_64 platform=x86_64 Kernel: Booted kernel: 3.10.0-957.el7.x86_64 GRUB default: 3.10.0-957.el7.x86_64 Build version: Linux version 3.10.0-957.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-36) (GCC)) # 1 SMP Thu Nov 8 23:39:32 UTC 2018 Booted kernel cmdline: root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8 GRUB default kernel cmdline: root=/dev/mapper/centos-root ro crashkernel=auto rd.lvm.lv=centos/root rd.lvm.lv=centos/swap rhgb quiet LANG=en_US.UTF-8 Taint-check: 536870912 (see https://access.redhat. Com/solutions/40594) 29 TECH_PREVIEW: Technology Preview code is loaded-Sys time: Sun May 12 10:12:22 CDT 2019 Boot time: Sun May 12 09:50:20 CDT 2019 (epoch: 1557672620) Time Zone: America/Chicago Uptime: 22 min 1 user LoadAvg: [1 CPU] 1.19 (119%), 0.27 (27%), 0.14 (14%) / proc/stat: 8 procs_blocked: 2 processes [Since boot]: 9005 cpu [Utilization since boot]: us 1%, ni 0%, sys 1%, idle 99%, iowait 0%, irq 0%, sftirq 0%, steal 0%

To view the kdump configuration, run xsos with the-k or-- kdump switch.

# xsos-kdump / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaKDUMP CONFIG kexec-tools rpm version: kexec-tools-2.0.15-21.el7.x86_64 Service enablement: UNIT STATE kdump.service enabled kdump initrd/initramfs: 13585734 Feb 19 05:51 initramfs-3.10.0-957.el7.x86_64kdump.img Memory reservation config: / proc/cmdline {crashkernel=auto} GRUB default {crashkernel=auto} Actual memory reservation per / proc/iomem: 2a000000-340fffff: Crash kernel kdump.conf: path / var/crash core_collector makedumpfile-l-- message-level 1-d 31 kdump.conf "path" available space: System MemTotal (uncompressed core size) {1.80 GiB} Available free space on target path's fs {22.68 GiB} (fs=/) Panic sysctls: kernel.sysrq [bitmask] = "16" (see proc man page) kernel. Panic [secs] = 0 (no autoreboot on panic) kernel.hung_task_panic = 0 kernel.panic_on_oops = 1 kernel.panic_on_io_nmi = 0 kernel.panic_on_unrecovered_nmi = 0 kernel.panic_on_stackoverflow = 0 kernel.softlockup_panic = 0 kernel.unknown_nmi_panic = 0 kernel.nmi_watchdog = 1 vm.panic_on_oom [0-2] = 0 (no panic)

To view information about CPU, run xsos using the-c or-- cpu switches.

# xsos-cpu / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaCPU 1 logical processors 1 Intel Core i7-6700HQ CPU @ 2.60GHz (flags: aes,constant_tsc,ht,lm,nx,pae,rdrand)

To see memory utilization, run xsos using the-m or-- mem switches.

# xsos-mem / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaMEMORY Stats graphed as percent of MemTotal: MemUsed ▊▊. 58.8% Buffers. 0.6% Cached ▊.. 29.9% HugePages... 0% Dirty... 0.7 RAM: 1.8 GiB total ram 1.1 GiB (59%) used 0.5 GiB (28%) used excluding Buffers/Cached 0.01 GiB (1%) dirty HugePages: No ram pre-allocated to HugePages LowMem/Slab/PageTables/Shmem: 0.09 GiB (5%) of total ram used for Slab 0.02 GiB (1%) of total ram used for PageTables 0.01 GiB (1%) of total ram used for Shmem Swap: 0 GiB (0%) used of 2 GiB total

To view the added disk information, run xsos using the-d and-disks switches.

# xsos-disks / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaSTORAGE Whole Disks from / proc/partitions: 2 disks, totaling 40 GiB (0.04 TiB)-Disk Size in GiB-sda 30 sdb 10

To view the network interface configuration, run xsos using the-e or-- ethtool switch.

# xsos-- ethtool / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaETHTOOL Interface Status: enp0s10 0000:00:0a.0 link=up 1000Mb/s full (autoneg=Y) rx ring 256A link=DOWN 4096 drv e1000 v7.3.21-k8-NAPI / fw UNKNOWN enp0s9 0000 Velcro 09.0 link=up 1000Mb/s full (autoneg=Y) rx ring 256 drv e1000 v7.3.21-k8-NAPI / fw UNKNOWN virbr0 Rx ring UNKNOWN drv bridge v2.3 / fw N/A virbr0-nic tap link=DOWN rx ring UNKNOWN drv tun v1.6 / fw UNKNOWN

To view information about the IP address, run xsos using the-I or-- ip switch.

# xsos-- ip / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaIP4 Interface Master IF MAC Address MTU State IPv4 Address = = lo-- 65536 up 127.0.0.1 08:00:27:0b:bc:e9 8 enp0s9-08:00:27:0b:bc:e9 1500 up 192.168.1.8 enp0s10 -08:00:27:b2:08:91 1500 up 192.168.1.9 + 24 virbr0- 52:54:00:ae:01:94 1500 up 192.168.122.1 + + 24 virbr0-nic virbr0 52:54:00:ae:01:94 1500 DOWN-IP6 Interface Master IF MAC Address MTU State IPv6 Address Scope = lo-- 65536 up:: 1 host enp0s9 128 host enp0s9-08:00:27:0b:bc:e9 1500 up fe80::945b:8333:f4bc:9723/64 link enp0s10-08:00 27:b2:08:91 1500 up fe80::7ed4:1fab:23c3:3790/64 link virbr0- 52:54:00:ae:01:94 1500 up-virbr0-nic virbr0 52:54:00:ae:01:94 1500 DOWN--

To view running processes through ps, run xsos using the-p or-- ps switches.

# xsos-- ps / var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsaPS CHECK Total number of threads/processes: 501171Top users of CPU & MEM: USER% CPU% MEM RSS root 20.6% 14.1% 0.30 GiB gdm 0.3% 16.8% 0.33 GiB postfix 0.0% 0.6% 0.01 GiB polkitd 0.06% 0.01 GiB daygeek 0.02% 0.2% 0.00 GiB colord 0.04% 0.4% 0.01 GiB Uninteruptible sleep threads/processes (0Unip 0): [None] Defunct zombie threads/processes (0Unip 0): [None] Top CPU-using processes: USER PID% CPU% MEM VSZ-MiB RSS-MiB TTY STAT START TIME COMMAND root 6542 15.6 4.2 875 78 Pts/0 Sl+ 10:11 0:07 / usr/bin/python / sbin/sosreport root 7582 3.0 0.1 10 2 pts/0 S 10:12 0:00 / bin/bash / usr/sbin/dracut-- print-cmdline root 7969 0.7 0.1 95 4? Ss 10:12 0:00 / usr/sbin/certmonger-S-p root 7889 0.4 0.2 24 4? Ss 10:12 0:00 / usr/lib/systemd/systemd-hostnamed gdm 3866 0.3 7.1 2856 131? Sl 09:50 0:04 / usr/bin/gnome-shell root 8553 0.2 0.1 47 3? S 10:12 0:00 / usr/lib/systemd/systemd-udevd root 6971 0.2 0.4 342 9? Sl 10:12 0:00 / usr/sbin/abrt-dbus-t133 root 3200 0.20.9 982 18? Ssl 09:50 0:02 / usr/sbin/libvirtd root 2855 0.1 0.1 88 3? Ss 09:50 0:01 / sbin/rngd-f rtkit 2826 0.00.0194 2? SNsl 09:50 0:00 / usr/libexec/rtkit-daemon Top MEM-using processes: USER PID% CPU% MEM VSZ-MiB RSS-MiB TTY STAT START TIME COMMAND gdm 3866 0.37.1 2856? Sl 09:50 0:04 / usr/bin/gnome-shell root 6542 15.6 4.2 875 78 pts/0 Sl+ 10:11 0:07 / usr/bin/python / sbin/sosreport root 3264 0.0 1.2 271 23 tty1 Ssl+ 09:50 0:00 / usr/bin/X: 0-background root 3200 0.2 0.9 982 18? Ssl 09:50 0:02 / usr/sbin/libvirtd root 3189 0.0 0.9 560 17? Ssl 09:50 0:00 / usr/bin/python2-Es / usr/sbin/tuned gdm 4072 0.00.9 988 17? Sl 09:50 0:00 / usr/libexec/gsd-media-keys gdm 4076 0.0 0.8 625 16? Sl 09:50 0:00 / usr/libexec/gsd-power gdm 4056 0.0 0.8 697 16? Sl 09:50 0:00 / usr/libexec/gsd-color root 2853 0.0 0.7 622 14? Ssl 09:50 0:00 / usr/sbin/NetworkManager-- no-daemon gdm 4110 0.00.7 544 14? Sl 09:50 0:00 / usr/libexec/gsd-wacom Top thread-spawning processes: # USER PID% CPU% MEM VSZ-MiB RSS-MiB TTY STAT START TIME COMMAND 17 root 3200 0.2 0.9 982 18?-09:50 0:02 / usr/sbin/libvirtd 12 root 6542 16.1 4.5 876 83 pts/0-10:11 0:07 / usr/bin/python / sbin/sosreport 10 gdm 3866 0.3 7.1 2856 131?-09:50 0:04 / usr/bin/gnome-shell 7 polkitd 2864 0.0 0.6 602 13?-09:50 0:01 / usr/lib/polkit-1/polkitd-- no-debug 6 root 2865 .0 203 1?-09:50 0:00 / usr/sbin/gssproxy-D 5 root 3189 0.0 0.9 560 17?-09:50 0:00 / usr/bin/python2-Es / usr/sbin/tuned 5 root 2823 0.0 0.3 443 6?-09:50 0:00 / usr/libexec/udisks2/udisksd 5 gdm 4102 0.0 0.2 461 5?-09:50 0:00 / usr/libexec/gsd-smartcard 4 root 3215 0.0 0.2 470 4?-09:50 0:00 / usr/sbin/gdm 4 gdm 4106 0.0 0.2 444 5 ?-09:50 0:00 / usr/libexec/gsd-sound, that's all for the article on "how to use xsos on Linux" Hope that the above content can be helpful to you, so that you can learn more knowledge, if you think the article is good, please share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.