dbginfo.sh - Collect information for debugging

Edit online

The dbginfo.sh script collects various system-related files for debugging purposes. It captures the current system environment and generates a .tar file.

Note: The dbginfo.sh script also collects current debugging and trace information, which is saved in the virtual Linux file system sysfs. This information is not persistent across reboots. You must run the dbginfo.sh script before a Linux system is rebooted to avoid losing important debugging and trace information.

If the Linux® system runs as z/VM® guest operating system, dbginfo.sh also collects information about the z/VM guest setup.

The dbginfo.sh script is part of the s390-tools package in SUSE Linux Enterprise Server and Ubuntu, and the s390-utils package in Red Hat Enterprise Linux.

The service and development team continuously improve dbginfo.sh. You can download the latest version from Github at github.com/ibm-s390-linux/s390-tools/releases. The dbginfo.sh script is included in the s390-tools .tar file.

Authorization

Running the dbginfo.sh script requires root authority.
For z/VM guest operating systems, any privilege class gives you relevant troubleshooting data. Privilege class B gives you the most data.

Syntax

where

-c: prints an overview of the environment and checks that any dependent commands are available. No data is saved.

Examples

To generate a diagnostic report with dbginfo.sh, issue dbginfo.sh. The output is similar to the following:

[root@system]# dbginfo.sh
dbginfo.sh: Debug information script version <version>
Copyright IBM Corp. 2002, 2022

Hardware platform     = s390x
Runtime environment   = z/VM
Kernel version        =  <version> (<version>)
OS version / distro   = <version>
Date and time of info = 2022-11-02-10-42-09

1 of 18: Collecting sysfs
2 of 18: Collecting procfs
3 of 18: Collecting config files
4 of 18: Collecting command output
5 of 18: Collecting hyptop for LPAR - 5s output
6 of 18: Skip z/VM: no z/VM environment
7 of 18: Collecting network output
8 of 18: Collecting osa oat output
9 of 18: Collecting ethtool output
10 of 18: Collecting Traffic Control output
11 of 18: Collecting bridge output
12 of 18: Skip OpenVSwitch: ovs-vsctl not available
13 of 18: Collecting KVM output
14 of 18: Collecting container host output
 Kubernetes ...
15 of 18: Skip nvme: not available
16 of 18: Collecting log files
 0 logfiles over 50 MB
17 of 18: Postprocessing
18 of 18: Finalizing: Creating archive with collected data

Collected data was saved to:
 >>  /tmp/DBGINFO-2022-11-02-10-42-09-<hostname>-<serial>.tgz  <<

Please review all collected data before sending to your service organization. 

Please review all collected data before sending to your service organization.

To see an environment overview, issue dbginfo.sh -c, for example:

# dbginfo.sh -c   
dbginfo.sh: Debug information script version <version>
Copyright IBM Corp. 2002, 2022

Hardware platform     = s390x
Runtime environment   = LPAR
LPAR Name:            <name> 
Kernel version        = <version>
OS version / distro   = <version>
KVM host              = YES
container host        Kubernetes: YES - docker: NO

Current user          = root (must be root for data collection)
Date and time         = Wed Nov  2 10:44:28 UTC 2022
Uptime                = 10:44:28 up 6 days,  5:24,  1 user,  load average: 0.04, 0.05, 0.01
Number of coredumps   = 0
zdevice onl/conf/offl = 4 / 4 / 1741
Log file check        = 0 logfiles over 50 MB

Working directory     = /tmp
Filesystem                           1K-blocks    Used Available Use% Mounted on
/dev/disk/by-path/ccw-0.0.7f76-part1  21118816 8842804  11177876  45% /
-rw------- 1 root root 12529573 Nov  2 10:42 /tmp/DBGINFO-2022-11-02-10-42-09-<hostname>-<serial>.tgz

Tool/command dependency check successful:
        timeout       = YES
        dump2tar      = YES

This is a console output only - no data was saved using option -c !