sbatch: error: invalid directive found in batch script: 16

3 min read 10-03-2025

The error message "sbatch: error: invalid directive found in batch script: 16" in Slurm (Simple Linux Utility for Resource Management) indicates a problem within your batch script. Line 16 contains a syntax error that Slurm's sbatch command can't interpret. This article will guide you through troubleshooting and resolving this common issue.

Understanding the Error

The error points directly to line 16 of your .slurm or .sh script. Slurm is complaining about an invalid directive, meaning the command or option on that line doesn't conform to Slurm's syntax rules. This could be due to several reasons:

Typos: Simple spelling mistakes in Slurm directives are a frequent cause.
Incorrect Syntax: Incorrect spacing, punctuation, or the use of unsupported characters can lead to errors.
Unsupported Directives: You might be using a Slurm directive that isn't supported by your Slurm version or cluster configuration.
Missing or Incorrect Parameters: Some Slurm directives require parameters; if these are missing or incorrect, it can cause errors.
Mixing Shell and Slurm Commands: Improperly combining shell commands with Slurm directives can lead to conflicts.

How to Troubleshoot and Fix the Error

Here's a step-by-step guide to diagnosing and resolving the "sbatch: error: invalid directive found in batch script: 16" problem:

1. Locate Line 16

Open your batch script (e.g., my_job.slurm) with a text editor. Carefully examine line 16. Look for:

Spelling Errors: Double-check the spelling of any Slurm directives (e.g., #SBATCH, --ntasks, --cpus-per-task, --mem).
Syntax Issues: Ensure correct spacing, punctuation, and capitalization. Pay attention to the use of equals signs (=), commas (,), and hyphens (-).
Unsupported Characters: Remove any characters that aren't allowed in Slurm directives (e.g., special characters unless properly escaped).

2. Common Culprits on Line 16

Line 16 might contain one of these common mistakes:

Incorrect #SBATCH Directive: Make sure #SBATCH is correctly spelled and at the start of the line. Each #SBATCH directive should be on its own line.
Missing or Extra Arguments: Check that arguments for directives like --ntasks, --mem, --time are correctly formatted. For example, --time=00:30:00 is correct for 30 minutes, while --time 00:30:00 is incorrect.
Conflicting Directives: Verify no directives conflict with each other. For instance, certain options might not be compatible depending on your cluster's configuration.
Incorrect Variable Usage: If using variables, ensure they're correctly defined and expanded.

3. Check Your Slurm Configuration

The available Slurm directives and their syntax may vary across clusters. Consult your cluster's documentation or administrator for details on supported directives and their parameters.

4. Simplify Your Script (Debugging Technique)

If you're struggling to find the error, try temporarily commenting out sections of your script to isolate the problem. Start by commenting out lines after line 16. If the error disappears, the problem lies in the commented-out section. Gradually uncomment lines until you pinpoint the faulty line.

5. Example of a Correct Script Section

Here's an example of a correctly formatted section of a Slurm script:

#!/bin/bash
#SBATCH --job-name=my_job
#SBATCH --ntasks=4
#SBATCH --cpus-per-task=1
#SBATCH --mem=8G
#SBATCH --time=01:00:00
#SBATCH --output=my_job.out
#SBATCH --error=my_job.err

# Your commands here

6. Seek Help

If you've exhausted these troubleshooting steps, seek assistance from your cluster's support team or other experienced users. Provide them with the full error message, your batch script, and the relevant cluster configuration details.

Preventing Future Errors

Follow Best Practices: Use a consistent coding style and carefully review your scripts before submitting them.
Use a Template: Create a template script for common tasks to reduce the risk of errors.
Test Thoroughly: Test your scripts with small, simple jobs before running large, resource-intensive jobs.

By carefully examining line 16 of your script and following these steps, you should be able to identify and fix the "sbatch: error: invalid directive found in batch script: 16" error and successfully run your Slurm jobs. Remember to consult your cluster's documentation for specific directives and their syntax.