DBGINFO.SH(8)

πŸ“¦ version 2.44.1, in opensuse-leap 16.0

πŸŽ€ DBGINFO.SH(8) β€” dbginfo.sh πŸŽ€

okay so bestie, this is the manual for dbginfo.sh, and it is literally the β€œgrab everything we need for debugging” script for Linux on IBM Z. Keep reading, it’s giving very useful. πŸ’–


✨ NAME ✨

dbginfo.sh β€” collect runtime, configuration and trace information for debugging Linux on IBM Z


🌸 SYNOPSIS 🌸

dbginfo.sh [OPTIONS]
dbginfo.sh {-h|-c|-v}

πŸ¦‹ DESCRIPTION πŸ¦‹

This script collects runtime, configuration and trace information that can be used to debug a Linux on IBM Z instance. For Linux on z/VM, the script also traces information about the z/VM system. Virtualization platform data is collected on a host serving this.

The debug information is written to a file /<DIRECTORY>/DBGINFO-<date>-<time>-<hostname>-<processorid>.tgz where [date] and [time] are the date and time when the debug data was collected. [hostname] indicates the hostname of the system the data was collected from. The [processorid] is taken from the processor 0 and indicates the processor identification.


πŸ’… OPTIONS πŸ’…

  • -h, --help β€” Print usage information, then exit.
  • -v, --version β€” Print version information, then exit.
  • -d <DIRECTORY>, --directory <DIRECTORY> β€” Specify the DIRECTORY where the data collection stores the temporary data and the final archive. The specified directory must already exist. If this parameter is not specified, /tmp is used by default.
  • -c, --check β€” Print online quick check (not saving any data) β€” can be combined with a preceding -d option.

πŸŽ€ FILES πŸŽ€

A .tgz file of the form

DBGINFO-<year>-<month>-<day>-<hours>-<minutes>-<seconds>-<hostname>-<processorid>.tgz

is generated and placed in the /tmp directory or in the directory specified by the -d option.


πŸ”₯ EXAMPLE πŸ”₯

Sample invocation:

[root@host]# dbginfo.sh -d /data-collection
dbginfo.sh: Debug information script version %S390_TOOLS_VERSION%
Copyright IBM Corp. 2002, 2024

Hardware platform     = s390x
Runtime environment   = z/VM - DPM: NO
Kernel version        = 5.14.0 (5.14.0-427.13.1.el9_4.s390x)
OS version / distro   = Red Hat Enterprise Linux 9.4 (Plow)
Date and time of info = 2024-07-11-11-11-11

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 z/VM - 5s output

7 of 20: Collecting z/VM output

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: Collecting container host output

 Kubernetes ...
16 of 20: Collecting NVME storage output

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:
 >>  /data-collection/DBGINFO-2024-07-11-11-11-11-host-012345.tgz  <<
Please review all collected data before sending to your service
organization.

πŸ’œ HINTS πŸ’œ

  • Run the script with root authority.
  • For Linux on z/VM, only z/VM guest virtual machines with class B privileges yield the complete debug information.

bestie, fr fr review all the collected data before sending it to your service organization. no cap. πŸ’–

πŸ’Œ from s390-tools, dated 07 2024 β€” catch u later, icon πŸ’…βœ¨

πŸ“¦ where this page comes from