For nordic and european frontier-training and hpc slurm engineers
Separate Slurm cgroup evictions from InfiniBand stalls on Nordic clusters.
Distinguish host RAM cgroup kills, parallel Lustre/WEKA checkpoint stalls, and InfiniBand HCA drops on high-density H100 pods.
Free 30-day Team evaluation. No card or automatic subscription. Work email verification required.
Replay a Nordic H100 Slurm multi-node stall
Upload your log file. Review the selected evidence and masking, then run diagnosis. Keep the original log for any follow-up questions.
Before uploading, review cloud data handling and local options.
Upload your log file. Large files are processed in your browser. Only selected evidence is submitted when you run diagnosis.
Try Denpex for 30 days. FREE.
No credit card. No automatic subscription. See whether Denpex helps with an incident you already understand.
Start your free 30-day Team evaluation
Up to 50 diagnoses a day for 30 days. Verify your work email to activate an eligible company evaluation, then replay a resolved incident and compare the evidence and next steps with your team's confirmed cause.
What a useful evaluation should establish
Avoid wasted Slurm queue wait time by escalating only verified failing nodes or tuning host DataLoader memory overhead.
Use Denpex alongside your existing telemetry tools to investigate submitted incident evidence. With monitoring configured on a supported plan, detected failures can trigger alerts and an automatic diagnosis from the captured evidence.
Inside Denpex
See the evidence, not just the claim
Follow the causal chain, inspect the quoted evidence and prepare the next handoff. These actual product captures use founder-account examples and the VS Code extension, with the source identified under each image. Open a capture to inspect it at full size.
Follow the failure through the cascade

Prepare the hardware escalation

Ask for the evidence that is missing

Keep the investigation in the editor

Verne & Nordic H100 Clusters - Observed Runtime Evidence
Incident pattern summary
A 16-node training job in Finland stops advancing when one worker hits a host cgroup memory kill while checkpointing to parallel storage, causing surviving ranks to emit NCCL timeouts.
slurmstepd: error: Detected 1 oom_kill event in StepId=219044.0. Some of the step tasks have been OOM Killed.
[E ProcessGroupNCCL.cpp:915] [Rank 0] Watchdog caught collective operation timeout: WorkNCCL(SeqNum=982, OpType=ALLREDUCE)Recommended verification flags
Set these environment flags in your training container or launch script to capture high-resolution collective logs:
NCCL_DEBUG=INFONCCL_IB_HCA=mlx5TORCH_NCCL_DUMP_ON_TIMEOUT=1TORCH_NCCL_TRACE_BUFFER_SIZE=2000Diagnostic Scope Boundary
Denpex evaluates exported Slurm, dmesg, and training logs without requiring cluster admin root access.
Other GPU Cloud Failure Workflows
Compare evidence patterns across multi-node fabrics, Kubernetes pods, and bare-metal environments.