instantly summarize system info Redhat sosreport sosreport examiner System Diagnostic Tool system monitoring xsos

xsos – A Tool To Read SOSReport In Linux

We all are already find out about sosreport. It’s used to collect system info that can be utilized for diagnostic.

Redhat help advise us to offer a sosreport once we increase a case with them to research the present system status.

It’s accumulating all type of studies that can help consumer to determine the basis causes of problem.

We will simply extract and skim the sosreport nevertheless it’s very troublesome to read. Because it has created a separate file for every part.

In case you are on the lookout for efficiency bottleneck software then i might advocate you to verify the oswbb (OSWatcher) utility.

So, what’s the easiest way to read all along with syntax highlighting in Linux.

Sure, it may be achieved by way of xsos device.

What Is sosreport?

The sosreport command is a device that collects bunch of configuration particulars, system info and diagnostic info from operating system (particularly RHEL & OEL system).

It helps technical help engineer to research the system in lots of facet.

This stories incorporates bunch of details about the system akin to boot info, filesystem, memory, hostname, installed rpms, system IP, networking particulars, OS version, put in kernel, loaded kernel modules, listing of open information, listing of PCI units, mount level and it’s details, operating process info, process tree output, system routing, all of the configuration information which is situated in /and so forth folder, and all the log information which is situated in /var folder.

It will take some time to generate a report and it’s is determined by your system installation and configuration.

As soon as completed, sosreport will generate a compressed archive file beneath /tmp directory.

What Is xsos?

xsos is a software that assist consumer to easily learn sosreport on Linux methods. In other hand, we will say sosreport examiner.

It immediately summarize system information from a sosreport or a operating system.

xsos will try and make it straightforward, parsing and calculating and formatting knowledge from dozens of information (and instructions) to offer you an in depth overview a few system.

You possibly can immediately summarize your system info by operating the next command.

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

How To Install xsos In Linux?

We will simply set up xsos using the following two methods.

In case you are on the lookout for latest bleeding-edge model. Use the next steps.

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

# chmod +x /usr/native/bin/xsos

That is the advisable technique to install xsos. It can install xsos from rpm file.

# yum install http://people.redhat.com/rsawhill/rpms/latest-rsawaroha-release.rpm

# yum set up xsos

How To Use xsos In Linux?

Once xsos is installed by one of many above methods. Merely run the xsos command with none options, which show you the essential details about your 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: (lacking)
RHSM: (lacking)
YUM: 2 enabled plugins: fastestmirror, langpacks
Runlevel: N 5 (default graphical)
SELinux: implementing (default implementing)
Arch: mach=x86_64 cpu=x86_64 platform=x86_64
Kernel:
Booted kernel: Three.10.0-957.el7.x86_64
GRUB default: Three.10.0-957.el7.x86_64
Construct version:
Linux model 3.10.0-957.el7.x86_64 ([email protected]) (gcc model four.8.5 20150623 (Purple
Hat 4.Eight.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-Eight
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-Eight
Taint-check: Zero (kernel untainted)
– – – – – – – – – – – – – – – – – – –
Sys time: Sun Might 12 10:05:21 CDT 2019
Boot time: Sun Might 12 09:50:20 CDT 2019 (epoch: 1557672620)
Time Zone: America/Chicago
Uptime: 15 min, 1 consumer
LoadAvg: [1 CPU] Zero.00 (Zero%), Zero.04 (four%), 0.09 (9%)
/proc/stat:
procs_running: 2 procs_blocked: Zero processes [Since boot]: 6423
cpu [Utilization since boot]:
us 1%, ni Zero%, sys 1%, idle 99%, iowait 0%, irq Zero%, sftirq Zero%, steal Zero%

How To Use xsos Command To View Generated sosreport Output In Linux?

We’d like the sosreport to learn additional using xsos command. To achieve this, navigate the following URL to install and generate sosreport on Linux.

Sure, i have already generated a sosreport and file is under.

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

Run the next command to untar it.

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

To view all the data, run xsos with -a, –all change.

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

To view the bios information, run xsos with -b, –bios change.

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

To view the system primary information resembling hostname, distro, SELinux, kernel information, uptime, and so forth, run xsos with -o, –os change.

# xsos –os /var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa
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
SELinux: implementing (default implementing)
Arch: mach=x86_64 cpu=x86_64 platform=x86_64
Kernel:
Booted kernel: Three.10.Zero-957.el7.x86_64
GRUB default: 3.10.Zero-957.el7.x86_64
Build model:
Linux model Three.10.Zero-957.el7.x86_64 ([email protected]) (gcc version 4.8.5 20150623 (Pink
Hat four.Eight.5-36) (GCC) ) #1 SMP Thu Nov Eight 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-Eight
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-Eight
Taint-check: 536870912 (see https://access.redhat.com/solutions/40594)
29 TECH_PREVIEW: Know-how Preview code is loaded
– – – – – – – – – – – – – – – – – – –
Sys time: Sun Might 12 10:12:22 CDT 2019
Boot time: Sun Might 12 09:50:20 CDT 2019 (epoch: 1557672620)
Time Zone: America/Chicago
Uptime: 22 min, 1 consumer
LoadAvg: [1 CPU] 1.19 (119%), 0.27 (27%), Zero.14 (14%)
/proc/stat:
procs_running: 8 procs_blocked: 2 processes [Since boot]: 9005
cpu [Utilization since boot]:
us 1%, ni Zero%, sys 1%, idle 99%, iowait 0%, irq Zero%, sftirq Zero%, steal 0%

To view the kdump configuration, run xsos with -k, –kdump change.

# xsos –kdump /var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa
KDUMP CONFIG
kexec-tools rpm model:
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.Zero-957.el7.x86_64kdump.img
Memory reservation config:
/proc/cmdline crashkernel=auto
GRUB default crashkernel=auto
Precise reminiscence 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” out there area:
System MemTotal (uncompressed core measurement) 1.80 GiB
Out there free area on track path’s fs 22.68 GiB (fs=/)
Panic sysctls:
kernel.sysrq [bitmask] = “16” (see proc man web page)
kernel.panic [secs] = Zero (no autoreboot on panic)
kernel.hung_task_panic = Zero
kernel.panic_on_oops = 1
kernel.panic_on_io_nmi = Zero
kernel.panic_on_unrecovered_nmi = Zero
kernel.panic_on_stackoverflow = 0
kernel.softlockup_panic = 0
kernel.unknown_nmi_panic = Zero
kernel.nmi_watchdog = 1
vm.panic_on_oom [0-2] = 0 (no panic)

To view the information about CPU, run xsos with -c, –cpu change.

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

To view about reminiscence utilization, run xsos with -m, –mem change.

# xsos –mem /var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa
MEMORY
Stats graphed as % of MemTotal:
MemUsed ▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊………………… 58.8%
Buffers ………………………………………….. Zero.6%
Cached ▊▊▊▊▊▊▊▊▊▊▊▊▊▊▊…………………………….. 29.9%
HugePages ………………………………………….. Zero.Zero%
Soiled ………………………………………….. 0.7%
RAM:
1.Eight GiB complete ram
1.1 GiB (59%) used
0.5 GiB (28%) used excluding Buffers/Cached
Zero.01 GiB (1%) dirty
HugePages:
No ram pre-allocated to HugePages
LowMem/Slab/PageTables/Shmem:
Zero.09 GiB (5%) of complete ram used for Slab
Zero.02 GiB (1%) of complete ram used for PageTables
Zero.01 GiB (1%) of complete ram used for Shmem
Swap:
0 GiB (0%) used of two GiB complete

To view the added disks info, run xsos with -d, –disks change.

# xsos –disks /var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa
STORAGE
Entire Disks from /proc/partitions:
2 disks, totaling 40 GiB (Zero.04 TiB)
– – – – – – – – – – – – – – – – – – – – –
Disk Measurement in GiB
—- ———–
sda 30
sdb 10

To view the community interface configuration, run xsos with -e, –ethtool change.

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

To view the information about IP tackle, run xsos with -i, –ip change.

# xsos –ip /var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa
IP4
Interface Grasp IF MAC Handle MTU State IPv4 Handle
========= ========= ================= ====== ===== ==================
lo – – 65536 up 127.0.Zero.1/Eight
enp0s9 – 08:00:27:0b:bc:e9 1500 up 192.168.1.8/24
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 Handle MTU State IPv6 Tackle Scope
========= ========= ================= ====== ===== =========================================== =====
lo – – 65536 up ::1/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 hyperlink
virbr0 – 52:54:00:ae:01:94 1500 up – –
virbr0-nic virbr0 52:54:00:ae:01:94 1500 DOWN – –

To view the operating processes by way of ps, run xsos with -p, –ps change.

# xsos –ps /var/tmp/sosreport-CentOS7-01-1005-2019-05-12-pomeqsa
PS CHECK
Complete variety of threads/processes:
501 / 171
Prime users of CPU & MEM:
USER %CPU %MEM RSS
root 20.6% 14.1% Zero.30 GiB
gdm Zero.Three% 16.Eight% Zero.33 GiB
postfix 0.Zero% 0.6% Zero.01 GiB
polkitd 0.0% Zero.6% Zero.01 GiB
daygeek Zero.0% 0.2% Zero.00 GiB
colord Zero.0% 0.four% Zero.01 GiB
Uninteruptible sleep threads/processes (Zero/Zero):
[None] Defunct zombie threads/processes (Zero/Zero):
[None] Prime 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.Zero Zero.1 10 2 pts/Zero S 10:12 Zero:00 /bin/bash /usr/sbin/dracut –print-cmdline
root 7969 0.7 Zero.1 95 4 ? Ss 10:12 Zero:00 /usr/sbin/certmonger -S -p
root 7889 Zero.4 Zero.2 24 4 ? Ss 10:12 Zero:00 /usr/lib/systemd/systemd-hostnamed
gdm 3866 Zero.3 7.1 2856 131 ? Sl 09:50 0:04 /usr/bin/gnome-shell
root 8553 Zero.2 0.1 47 3 ? S 10:12 0:00 /usr/lib/systemd/systemd-udevd
root 6971 0.2 0.four 342 9 ? Sl 10:12 0:00 /usr/sbin/abrt-dbus -t133
root 3200 0.2 0.9 982 18 ? Ssl 09:50 Zero:02 /usr/sbin/libvirtd
root 2855 Zero.1 0.1 88 Three ? Ss 09:50 0:01 /sbin/rngd -f
rtkit 2826 Zero.0 Zero.Zero 194 2 ? SNsl 09:50 0:00 /usr/libexec/rtkit-daemon
Prime MEM-using processes:
USER PID %CPU %MEM VSZ-MiB RSS-MiB TTY STAT START TIME COMMAND
gdm 3866 0.Three 7.1 2856 131 ? Sl 09:50 0:04 /usr/bin/gnome-shell
root 6542 15.6 four.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 :Zero -background
root 3200 Zero.2 0.9 982 18 ? Ssl 09:50 0:02 /usr/sbin/libvirtd
root 3189 Zero.0 0.9 560 17 ? Ssl 09:50 Zero:00 /usr/bin/python2 -Es /usr/sbin/tuned
gdm 4072 0.Zero 0.9 988 17 ? Sl 09:50 Zero:00 /usr/libexec/gsd-media-keys
gdm 4076 Zero.Zero 0.Eight 625 16 ? Sl 09:50 0:00 /usr/libexec/gsd-power
gdm 4056 Zero.0 0.8 697 16 ? Sl 09:50 0:00 /usr/libexec/gsd-color
root 2853 Zero.0 Zero.7 622 14 ? Ssl 09:50 Zero:00 /usr/sbin/NetworkManager –no-daemon
gdm 4110 0.0 Zero.7 544 14 ? Sl 09:50 Zero:00 /usr/libexec/gsd-wacom
Prime thread-spawning processes:
# USER PID %CPU %MEM VSZ-MiB RSS-MiB TTY STAT START TIME COMMAND
17 root 3200 Zero.2 0.9 982 18 ? – 09:50 Zero:02 /usr/sbin/libvirtd
12 root 6542 16.1 4.5 876 83 pts/Zero – 10:11 Zero:07 /usr/bin/python /sbin/sosreport
10 gdm 3866 0.Three 7.1 2856 131 ? – 09:50 Zero:04 /usr/bin/gnome-shell
7 polkitd 2864 Zero.0 0.6 602 13 ? – 09:50 Zero:01 /usr/lib/polkit-1/polkitd –no-debug
6 root 2865 Zero.0 0.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 Zero.0 0.Three 443 6 ? – 09:50 0:00 /usr/libexec/udisks2/udisksd
5 gdm 4102 Zero.0 Zero.2 461 5 ? – 09:50 Zero:00 /usr/libexec/gsd-smartcard
4 root 3215 Zero.Zero Zero.2 470 4 ? – 09:50 Zero:00 /usr/sbin/gdm
4 gdm 4106 0.Zero 0.2 444 5 ? – 09:50 0:00 /usr/libexec/gsd-sound