File contents sflow Error Analysis
Triage Flow
Identify category from the error message (see table below)Locate source -- check the file/line hint or task logApply fix from the quick-fix table or error-catalog.md
Error Categories
Category
Marker
Where to Look
Config loading
Configuration error:, File not found:CLI output / sflow.log
YAML syntax
Error parsing YAMLCLI output
Expression
Undefined variable, Invalid expression syntaxCLI output
Artifact
Artifact path validation failedCLI output / dry-run
Merge conflict
Version conflict, Workflow name conflictCLI output (multi-file)
SLURM
salloc failed, sbatch failedCLI / sbatch stderr
Probe timeout
Task stuck waiting
<task>/<task>.log
Task failure
Traceback, non-zero exit<task>/<task>.log
Batch/CSV
CSV file, sflow_config_file columnCLI output
Log Locations
<output_dir>/<run_id>/
sflow.log # orchestrator log
<task_name>/<task_name>.log # task stdout/stderr
<task_name>_0/ # replica 0
Batch jobs: also check the .sh script and sbatch stdout/stderr files.
Quick-Fix Table
Error Text
Fix
Configuration file not found: <path>Check -f path
Error parsing YAML configuration: <detail>Fix YAML syntax at indicated line
Configuration validation failed: <detail>Check field types/values (schema-reference.md)
Variable '<key>' specified in overrides is not definedDeclare variable in YAML first
Undefined variable in expressionFix spelling; ensure variable is declared
Invalid expression syntaxFix ${{ }} Jinja2 syntax
Artifact path validation failedFix fs:// path or create it
Version conflictAll files must use version: "0.1"
Probe timeout (task hangs)
Check task log; adjust regex_pattern / timeout
Traceback in task logRead traceback for root cause
salloc failedCheck partition/account/availability
CSV file must contain a 'sflow_config_file' columnAdd required column to CSV
Quick Diagnostic Commands
# Validate config without executing
sflow run -f config.yaml --dry-run
# See resolved expressions
sflow compose file1.yaml file2.yaml --resolve -o merged.yaml
# Check SLURM environment
sinfo -p <partition>
sacctmgr show account <name>
# Parse errors from log
python scripts/parse_sflow_errors.py <sflow.log>
python scripts/parse_sflow_errors.py - < <(sflow run -f config.yaml --dry-run 2>&1)
# Summarize a run's output
python scripts/summarize_run.py <output_dir>/<run_id>/
Common Runtime Issues
OOM : Reduce batch size, TP/DP, or model sizePort conflict : Kill stale processes or adjust port offsetsContainer not found : Verify image URI and registry accessNCCL errors : Set NCCL_SOCKET_IFNAME, check inter-node networkProbe mismatch : Server output doesn't match regex_pattern
Additional Resources
Source: NVIDIA/nv-sflow — distributed by TomeVault .
1 --- 2 name: nvidia-nv-sflow-nv-sflow 3 description: sflow Error Analysis 4 --- 5 6 # sflow Error Analysis 7 8 ## Triage Flow 9 10 1. **Identify category** from the error message (see table below) 11 2. **Locate source** -- check the file/line hint or task log 12 3. **Apply fix** from the quick-fix table or [error-catalog.md](error-catalog.md) 13 14 ## Error Categories 15 16 | Category | Marker | Where to Look | 17 |---------------------|--------------------------------------------------|---------------------------| 18 | Config loading | `Configuration error:`, `File not found:` | CLI output / sflow.log | 19 | YAML syntax | `Error parsing YAML` | CLI output | 20 | Expression | `Undefined variable`, `Invalid expression syntax`| CLI output | 21 | Artifact | `Artifact path validation failed` | CLI output / dry-run | 22 | Merge conflict | `Version conflict`, `Workflow name conflict` | CLI output (multi-file) | 23 | SLURM | `salloc failed`, `sbatch failed` | CLI / sbatch stderr | 24 | Probe timeout | Task stuck waiting | `<task>/<task>.log` | 25 | Task failure | `Traceback`, non-zero exit | `<task>/<task>.log` | 26 | Batch/CSV | `CSV file`, `sflow_config_file column` | CLI output | 27 28 ## Log Locations 29 30 ``` 31 <output_dir>/<run_id>/ 32 sflow.log # orchestrator log 33 <task_name>/<task_name>.log # task stdout/stderr 34 <task_name>_0/ # replica 0 35 ``` 36 37 Batch jobs: also check the `.sh` script and sbatch stdout/stderr files. 38 39 ## Quick-Fix Table 40 41 | Error Text | Fix | 42 |---------------------------------------------------------|----------------------------------------------------| 43 | `Configuration file not found: <path>` | Check `-f` path | 44 | `Error parsing YAML configuration: <detail>` | Fix YAML syntax at indicated line | 45 | `Configuration validation failed: <detail>` | Check field types/values (schema-reference.md) | 46 | `Variable '<key>' specified in overrides is not defined` | Declare variable in YAML first | 47 | `Undefined variable in expression` | Fix spelling; ensure variable is declared | 48 | `Invalid expression syntax` | Fix `${{ }}` Jinja2 syntax | 49 | `Artifact path validation failed` | Fix `fs://` path or create it | 50 | `Version conflict` | All files must use `version: "0.1"` | 51 | Probe timeout (task hangs) | Check task log; adjust `regex_pattern` / `timeout` | 52 | `Traceback` in task log | Read traceback for root cause | 53 | `salloc failed` | Check partition/account/availability | 54 | `CSV file must contain a 'sflow_config_file' column` | Add required column to CSV | 55 56 ## Quick Diagnostic Commands 57 58 ```bash 59 # Validate config without executing 60 sflow run -f config.yaml --dry-run 61 62 # See resolved expressions 63 sflow compose file1.yaml file2.yaml --resolve -o merged.yaml 64 65 # Check SLURM environment 66 sinfo -p <partition> 67 sacctmgr show account <name> 68 69 # Parse errors from log 70 python scripts/parse_sflow_errors.py <sflow.log> 71 python scripts/parse_sflow_errors.py - < <(sflow run -f config.yaml --dry-run 2>&1) 72 73 # Summarize a run's output 74 python scripts/summarize_run.py <output_dir>/<run_id>/ 75 ``` 76 77 ## Common Runtime Issues 78 79 - **OOM**: Reduce batch size, TP/DP, or model size 80 - **Port conflict**: Kill stale processes or adjust port offsets 81 - **Container not found**: Verify image URI and registry access 82 - **NCCL errors**: Set `NCCL_SOCKET_IFNAME`, check inter-node network 83 - **Probe mismatch**: Server output doesn't match `regex_pattern` 84 85 ## Additional Resources 86 87 - Exhaustive error patterns: [error-catalog.md](error-catalog.md) 88 - Full docs: [faq](https://nvidia.github.io/nv-sflow/docs/user/faq), 89 [cli](https://nvidia.github.io/nv-sflow/docs/user/cli), 90 [configuration](https://nvidia.github.io/nv-sflow/docs/user/configuration), 91 [backends](https://nvidia.github.io/nv-sflow/docs/user/backends) 92 93 --- 94 > Source: [NVIDIA/nv-sflow](https://github.com/NVIDIA/nv-sflow) — distributed by [TomeVault](https://tomevault.io). 95 <!-- tomevault:4.0:skill_md:2026-06-19 -->
commit 69bddb6285
Frequently asked questions How do I install the Nvidia Nv Sflow Nv Sflow skill? Run npx skillmds@latest add tomevault-io/nvidia-nv-sflow-nv-sflow in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.
What does the Nvidia Nv Sflow Nv Sflow skill do? sflow Error Analysis It is listed under Coding & Dev Tools on SkillMD.
Is Nvidia Nv Sflow Nv Sflow safe to use? This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.
Which AI agents work with Nvidia Nv Sflow Nv Sflow? This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.
Is Nvidia Nv Sflow Nv Sflow free to use? Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.
Who published Nvidia Nv Sflow Nv Sflow? tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.
tomevault-io