On Wed, Apr 8, 2015 at 9:58 AM, Andy Riebs <[email protected]> wrote:
> Wow! Using Slurm to update the software on the cluster? And I'll guess > that you frequently ski Tuckerman's Ravine? :-) > > First, there is the possibility that Slurm is entirely innocent here, and > that some other package's update procedure is wiping out things like > context files (especially if they are in /tmp, /var/tmp, /var/run) -- they > shouldn't be doing that, but who knows. > I was just about to reply to my own message. I'm fairly certain the problem is actually that the directory identified by SlurmdSpoolDir (which I have owned by the package) was set to the wrong user. Since correcting that issue, I've run the upgrade process a number of times without incident, even under heavy load. Thanks for the response, however! -- Jon Nelson Dyn / Senior Software Engineer p. +1 (603) 263-8029
