Summary: | Frequent recent job environment issues | ||
---|---|---|---|
Product: | Slurm | Reporter: | Josko Plazonic <plazonic> |
Component: | slurmd | Assignee: | David Bigagli <david> |
Status: | RESOLVED INFOGIVEN | QA Contact: | |
Severity: | 3 - Medium Impact | ||
Priority: | --- | CC: | brian, da |
Version: | 14.03.7 | ||
Hardware: | Linux | ||
OS: | Linux | ||
Site: | Princeton (PICSciE) | Alineos Sites: | --- |
Atos/Eviden Sites: | --- | Confidential Site: | --- |
Coreweave sites: | --- | Cray Sites: | --- |
DS9 clusters: | --- | HPCnow Sites: | --- |
HPE Sites: | --- | IBM Sites: | --- |
NOAA SIte: | --- | OCF Sites: | --- |
Recursion Pharma Sites: | --- | SFW Sites: | --- |
SNIC sites: | --- | Linux Distro: | --- |
Machine Name: | CLE Version: | ||
Version Fixed: | Target Release: | --- | |
DevPrio: | --- | Emory-Cloud Sites: | --- |
Description
Josko Plazonic
2014-09-27 03:47:25 MDT
OK, I think I know what went on and slurm looks to be just an unfortunate victim. According to this: http://fedoramagazine.org/shellshock-how-does-it-actually-work/ exported functions (like module in our case) are now prefixed with BASH_FUNC_ and have () at the end. So if a user submitted a job with old shell (including the case where they have been logged in prior to shell upgrade) then this will not be done and functions will not be picked up in (new version of) bash shell launched by slurm. Therefore a temporary glitch until users log out and log back in and submit new jobs. So probably nothing for you guys to do - I'd close but waiting on user confirmation. OK, it looks like it was entirely due to bash update. We have instructed users to login anew and resubmit jobs and so far that seems to be fixing the problem. Thanks Josko, this is very good to know. David |