slurm-debug

Diagnosing a Slurm job failure involves analyzing job metadata with sacct and scontrol, inspecting StdOut and StdErr logs, and interpreting exit codes to identify the root cause and suggest fixes.

To find out why a Slurm job is stuck pending, analyze job metadata and states using sacct and scontrol to identify scheduling blocks, and apply remediation guidance for resubmission.

Interpreting Slurm exit codes and error logs requires inspecting StdOut and StdErr files to match messages against common error patterns, determining root causes and providing actionable remediation steps.

Troubleshooting a stalled Slurm job across clusters requires end-to-end diagnosis using safe Slurm tools like sacct and scontrol, combined with in-depth log analysis to provide actionable remediation guidance.

To diagnose a Slurm job failure, you need to provide a Slurm JobID or a path to your logs, enabling the tool to read job details, inspect error logs, and provide actionable remediation steps.