Diagnostic logs from Compute virtual machines (VMs) help you troubleshoot issues with VM operations, networking and workloads. We strongly recommend collecting logs while the issue is still occurring, because they capture more information about the broken state than logs collected after the issue has been resolved.Documentation Index
Fetch the complete documentation index at: https://docs.nebius.com/llms.txt
Use this file to discover all available pages before exploring further.
Types of logs
This guide describes how to collect the following types of logs for troubleshooting:- GPU logs:
nvidia-bug-report.sh. - General system logs, including more context about system services and package versions:
sos report. - NVIDIA® Mellanox® adapter (InfiniBand™/NVSwitch/Ethernet) logs:
sysinfo-snapshot.
Prerequisites
Make sure that you have configured SSH access to the VM.How to collect logs
- Connect to the VM by using SSH.
-
Generate GPU logs:
This command usually runs for about five minutes and generates
nvidia-bug-report.log.gzin the current working directory. If the command stops responding, run it in safe mode: -
If you need more system information, generate general system logs:
This command generates an archive in the following format:
/tmp/sosreport-<VM_ID>-<date>-<random_ID>.tar.gz. -
If you are troubleshooting Mellanox adapter issues, generate Mellanox adapter logs:
This command generates an archive in the following format:
/tmp/sysinfo-snapshot-<VM_ID>-<date>-<random_ID>.tgz.
How to get generated log files
-
Check that the files were generated on your VM by running the following commands:
-
To check for GPU logs:
-
To check for general system logs or Mellanox adapter logs:
-
To check for GPU logs:
-
From your local shell, run the following command to copy the files from the VM to the current directory:
In the command, specify the path to the generated file on the VM, for example:
nvidia-bug-report.log.gz,/tmp/sosreport-*.tar.gzor/tmp/sysinfo-snapshot-*.tgz. If copying files from the/tmpdirectory fails due to a permission error, this usually means the generated file is owned by root. To fix this issue, proceed to the next step. -
Reconnect to the VM and set permissions to grant read access to non-root users. After that, you can rerun the
scpcommand.If you successfully copied the generated log file, skip this step.In the command, set theremote_file_pathto/tmp/sosreport-*.tar.gzor/tmp/sysinfo-snapshot-*.tgz. - Find the copied log files in your local directory.