rocmtechsupport

KO | EN

gitlite — search

#javascript #python #hacktoberfest #typescript #android #rust #macos #windows #cli #kubernetes #security #pytorch #openai #open-source

rocmtechsupport

(★ 14)

Utilities for ROCm Tech Support Log Collections

rocmtechsupport Latest Version Download

Download Latest Version (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

***
## rocm_techsupport.sh V1.41 Utility to Collect ROCm TechSupport Logs
***
Shell Utility for Ubuntu/CentOS/SLES bare metal or docker container to collect logs for support/troubleshooting purpose.
Collects logs from last 3 boots (please enable persistent boot logs.)
### NOTE: To enable persistent boot logs across reboots, please run:  
```
  sudo mkdir -p /var/log/journal
  sudo systemctl restart systemd-journald.service
```
### Step 1: Download rocm_techsupport.sh shell script using:
```
wget -O rocm_techsupport.sh --no-cache --no-cookies --no-check-certificate  https://raw.githubusercontent.com/amddcgpuce/rocmtechsupport/master/rocm_techsupport.sh
```
### Step 2: Run the script, redirect output to a file
```
sudo sh ./rocm_techsupport.sh > `hostname`.`date +"%y-%m-%d-%H-%M-%S"`.rocm_techsupport.log 2>&1
```
**NOTE:** Use ROCM_VERSION environment variable to specify the path to the installed ROCM (if not installed in default location)
**NOTE:** Without `sudo`, certain data such as verbose `lspci`, `dmidecode` may not get captured in the logs but the script can be run without `sudo` in environments where `sudo` access is not permitted.
### Step 3 (Optional): Collect `journalctl` or `dmesg` (for containers) logs
```
sudo journalctl -b > `hostname`.`date +"%y-%m-%d-%H-%M-%S"`.journalctl.log
```
Attach the collected logs to the support request along with the description of the incident.

#### Example Usage (run with `sudo`: preferred but not required):
```
mkdir  downloads
cd  downloads
wget -O rocm_techsupport.sh --no-cache --no-cookies --no-check-certificate https://raw.githubusercontent.com/amddcgpuce/rocmtechsupport/master/rocm_techsupport.sh

# Redirect output to file with hostname and timestamp
sudo sh ./rocm_techsupport.sh > `hostname`.`date +"%y-%m-%d-%H-%M-%S"`.rocm_techsupport.log 2>&1

#### (Optional) Collect journalctl or dmesg logs
sudo journalctl -b > `hostname`.`date +"%y-%m-%d-%H-%M-%S"`.journalctl.log

#Redirect output to file with SYSTEM_NAME_or_ISSUEID
sudo sh ./rocm_techsupport.sh > SYSTEM_NAME_or_ISSUEID.rocm_techsupport.log 2>&1

# Use ROCM_VERSION environment variable to specify which installed ROCm to use when
# collecting logs, for example, ROCM_VERSION=/opt/rocm-5.0.0 to use ROCm 5.0.0 GA version
# Use ROCM_VERSION to specify installed ROCM path and redirect output to a file with hostname and timestamp
sudo ROCM_VERSION=/opt/rocm-5.2.3 sh ./rocm_techsupport.sh > `hostname`.`date +"%y-%m-%d-%H-%M-%S"`.rocm_techsupport.log 2>&1

#Redirect output to file with SYSTEM_NAME_or_ISSUEID
sudo ROCM_VERSION=/opt/rocm-5.0.0 sh ./rocm_techsupport.sh > SYSTEM_NAME_or_ISSUE_ID.rocm_techsupport.log 2>&1

# Without sudo, certain data such as verbose lspci, dmidecode may not
# get captured in the logs

Compress/Zip the output file and include with reported issue.
```

rocmtechsupport

rocmtechsupport Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

rocmtechsupport

rocmtechsupport Latest Version Download

Today's picks

Was this content helpful?

Recent Feedback

Download README