Summary: | slurmstepd: error: environment variable SLURM_CPU_BIND is too long | ||
---|---|---|---|
Product: | Slurm | Reporter: | David Gloe <david.gloe> |
Component: | slurmstepd | Assignee: | Michael Steed <msteed> |
Status: | OPEN --- | QA Contact: | |
Severity: | 4 - Minor Issue | ||
Priority: | --- | ||
Version: | 24.05.3 | ||
Hardware: | Linux | ||
OS: | Linux | ||
Site: | CRAY | Alineos Sites: | --- |
Atos/Eviden Sites: | --- | Confidential Site: | --- |
Coreweave sites: | --- | Cray Sites: | Cray Internal |
DS9 clusters: | --- | HPCnow Sites: | --- |
HPE Sites: | --- | IBM Sites: | --- |
NOAA SIte: | --- | NoveTech Sites: | --- |
Nvidia HWinf-CS Sites: | --- | OCF Sites: | --- |
Recursion Pharma Sites: | --- | SFW Sites: | --- |
SNIC sites: | --- | Tzag Elita Sites: | --- |
Linux Distro: | --- | Machine Name: | |
CLE Version: | Version Fixed: | ||
Target Release: | --- | DevPrio: | --- |
Emory-Cloud Sites: | --- |
Description
David Gloe
2025-03-24 09:42:51 MDT
Hi David, The errors about `SLURM_CPU_BIND` and `SLURM_CPU_BIND_LIST` being too long will not prevent job execution, although those variables will remain unset in the job environment. Can you confirm that your jobs still run as expected? The failure to set these environment variables is due to a kernel limitation (128KB per variable). We are looking at updating the logging around this since it won't cause jobs to fail. Related: ticket 644 Michael |