1. 28 Feb, 2012 1 commit
  2. 27 Feb, 2012 1 commit
    • Morris Jette's avatar
      Reduce gres error logging · 670be35a
      Morris Jette authored
      Only report "gres/<name> lacks File parameter" if some nodes define
      File AND this node does not AND (new part here) the GRES count on
      this node is non-zero
      670be35a
  3. 24 Feb, 2012 9 commits
  4. 23 Feb, 2012 1 commit
  5. 22 Feb, 2012 4 commits
  6. 21 Feb, 2012 1 commit
  7. 20 Feb, 2012 2 commits
  8. 06 Feb, 2012 3 commits
    • Danny Auble's avatar
      e3269071
    • Danny Auble's avatar
      The openpty(3) call used by slurmstepd to allocate a pseudo-terminal · 2a1c08b0
      Danny Auble authored
      is a convenience function in BSD and glibc that internally calls
      the equivalent of
      
          int masterfd = open("/dev/ptmx", flags);
          grantpt (masterfd);
          unlockpt (masterfd);
          int slavefd = open (slave, O_RDRW|O_NOCTTY);
      
      (in psuedocode)
      
      On Linux, with some combinations of glibc/kernel (in this
      case glibc-2.14/Linux-3.1), the equivalent of grantpt(3) was failing
      in slurmstepd with EPERM, because the allocated pty was getting
      root ownership instead of the user running the slurm job.
      
      From the POSIX description of grantpt:
      
       "The grantpt() function shall change the mode and ownership of the
        slave pseudo-terminal device... The user ID of the slave shall
        be set to the real UID of the calling process..."
      
       http://pubs.opengroup.org/onlinepubs/007904875/functions/grantpt.html
      
      This means that for POSIX-compliance, the real user id of slurmstepd
      must be the user executing the SLURM job at the time openpty(3) is
      called. Unfortunately, the real user id of slurmstepd at this
      point is still root, and only the effective uid is set to the user.
      
      This patch is a work-around that uses the (non-portable) setresuid(2)
      system call to reset the real and effective uids of the slurmstepd
      process to the job user, but keep the saved uid of root. Then after
      the openpty(3) call, the previous credentials are reestablished
      using the same call.
      2a1c08b0
    • Danny Auble's avatar
      1b1e6196
  9. 03 Feb, 2012 1 commit
    • Morris Jette's avatar
      Fix for srun with --exclude and --nodes · a4551158
      Morris Jette authored
      Fix for srun allocating running within existing allocation with --exclude
      option and --nnodes count small enough to remove more nodes.
      
          > salloc -N 8
          salloc: Granted job allocation 1000008
          > srun -N 2 -n 2 --exclude=tux3 hostname
          srun: error: Unable to create job step: Requested node configuration is not available
      
      Patch from Phil Eckert, LLNL.
      a4551158
  10. 02 Feb, 2012 1 commit
  11. 01 Feb, 2012 5 commits
  12. 31 Jan, 2012 6 commits
    • Danny Auble's avatar
      BLUEGENE - fix for not allowing jobs if all midplanes are drained and all · 1e40f647
      Danny Auble authored
      blocks are in an error state.
      1e40f647
    • Danny Auble's avatar
      Added MaxCPURunMins to sacctmgr --help · 0741a338
      Danny Auble authored
      0741a338
    • Danny Auble's avatar
      whitespace cleanup · a372fc29
      Danny Auble authored
      a372fc29
    • Morris Jette's avatar
      Note nature of latest change · 7189ecaa
      Morris Jette authored
      7189ecaa
    • Didier GAZEN's avatar
      Problem when using srun --uid in conjunction with --jobid (patch included) · e2b39c14
      Didier GAZEN authored
      Hi,
      
      With slurm 2.3.2 (or 2.3.3), I encounter the following error when
      trying to launch as root a command attached to a running user's job
      even if I use the --uid=<user> option :
      
      sila@suse112:~> squeue
         JOBID PARTITION     NAME     USER    STATE      TIME TIMELIMIT
      NODES   CPUS NODELIST(REASON)
           551     debug mysleep.     sila  RUNNING      0:02 UNLIMITED
      1      1 n1
      
      root@suse112:~ # srun --jobid=551 hostname
      srun: error: Unable to create job step: Access/permission denied
      <--normal behaviour
      
      root@suse112:~ # srun --jobid=551 --uid=sila hostname
      srun: error: Unable to create job step: Invalid user id <--problem
      
      By increasing slurmctld verbosity, the log files displays the follwing
      error :
      
      slurmctld: debug2: Processing RPC: REQUEST_JOB_ALLOCATION_INFO_LITE from
      uid=0
      slurmctld: debug:  _slurm_rpc_job_alloc_info_lite JobId=551 NodeList=n1
      usec=1442
      slurmctld: debug2: Processing RPC: REQUEST_JOB_STEP_CREATE from uid=0
      slurmctld: error: Security violation, JOB_STEP_CREATE RPC from uid=0 to
      run as uid 1001
      
      which occurs in function : _slurm_rpc_job_step_create
      (src/slurmctld/proc_req.c)
      
      Here's my patch to prevent the command from failing (but I'm not sure
      that there is no side effects) :
      e2b39c14
    • Danny Auble's avatar
      Fix to the multifactor priority plugin to calculate effective usage earlier · 7d9e3ed2
      Danny Auble authored
      to give a correct priority on the first decay cycle after a restart of the
      slurmctld. Patch from Martin Perry, Bull.
      7d9e3ed2
  13. 27 Jan, 2012 5 commits