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 .tgz 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.

If the Linux system runs as a KVM guest operating system collect diagnostic data from KVM host and KVM guest.

The dbginfo.sh script is part of the s390-tools package in SUSE Linux Enterprise Server and Ubuntu, and the s390-utils-base 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.

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:

# s390-tools/scripts/dbginfo.sh
dbginfo.sh: Debug information script version 2.38.0-2.el10
Copyright IBM Corp. 2002, 2025

Hardware platform     = s390x
Runtime environment   = LPAR - DPM: NO
Kernel version        = 6.12.0 (6.12.0-55.9.1.el10_0.s390x)
OS version / distro   = Red Hat Enterprise Linux 10.0 (Coughlan)
Date and time of info = 2025-08-20-10-18-35

1 of 20: Collecting sysfs
2 of 20: Collecting procfs
3 of 20: Collecting config files
4 of 20: Collecting initrd config files
5 of 20: Collecting command output
6 of 20: Collecting hyptop for LPAR - 5s output
7 of 20: Skip z/VM: no z/VM environment
8 of 20: Collecting network output
9 of 20: Collecting osa oat output
10 of 20: Collecting ethtool output
11 of 20: Collecting Traffic Control output
12 of 20: Collecting bridge output
13 of 20: Skip OpenVSwitch: ovs-vsctl not available
14 of 20: Skip KVM: no virsh command
15 of 20: Skip container host: not found
16 of 20: Skip nvme: not available
17 of 20: Collecting DASD storage output
18 of 20: Collecting log files
 0 logfiles over 50 MB
19 of 20: Postprocessing
20 of 20: Finalizing: Creating archive with collected data
 
Collected data was saved to:
 >>  /tmp/DBGINFO-2025-08-20-10-18-35-a83lp78-5378E8.tgz  <<
 
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 2.38.0-2.el10
Copyright IBM Corp. 2002, 2025

Hardware platform     = s390x
Runtime environment   = z/VM - DPM: NO
LPAR Name:            A83LP30 
VM00 Name:            A8330040
Kernel version        = 6.12.0
OS version / distro   = Red Hat Enterprise Linux 10.0 (Coughlan)
KVM host              = NO
container host        Kubernetes: NO - docker: NO - podman: NO

Current user          = root (must be root for data collection)
Date and time         = Wed Aug 20 10:11:08 CEST 2025
Uptime                = 10:11:08 up 17:46,  2 users,  load average: 0.00, 0.00, 0.00
Number of coredumps   = 0
zdevice onl/conf/offl = 5 / 4 / 0
Log file check        = 0 logfiles over 50 MB

Working directory     = /tmp
Filesystem     1K-blocks    Used Available Use% Mounted on
/dev/dasda1     21118816 1275212  18745468   7% /


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

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