[slurm-dev] Re: rpmbuild from tarball

2017-06-18 Thread Andrew Elwell
yes - The *schedmd* suppliied tarballs (as you point to in the wiki page) work fine. The *github* ones dont. if you compare them, the github ones have a different slurm.spec, hence my asking if there was another script needed to sed them On 19 June 2017 at 14:01, Ole Holm Nielsen wrote: > On

[slurm-dev] Re: Can't get formatted sinfo to work...

2017-06-18 Thread Loris Bennett
Hi Mehmet, "Belgin, Mehmet" writes: > I’m troubleshooting an issue that causes NHC to fail to offline a bad > node. The node offline script uses formatted “sinfo" to identify the > node status, which returns blank for some reason. Interestingly, sinfo > works without custom formatting. > > Coul

[slurm-dev] rpmbuild from tarball

2017-06-18 Thread Andrew Elwell
I've just tried and failed to get the github release (https://github.com/SchedMD/slurm/releases) of 16.05.10-2 to build using the 'rpmbuild -ta tarball' trick - it's failing on line 88 of the spec ie > Name:see META file > Version: see META file > Release: see META file however the tarball f

[slurm-dev] Re: Resource limits in new partition

2017-06-18 Thread Jagga Soorma
Hi Guys, I can't get this to work: # sacctmgr modify account account=cig set GrpTRES=gres/gpu=8 Unknown option: GrpTRES=gres/gpu=8 Use keyword 'where' to modify condition The GrpTRES=cpu=x option works but for some reason GrpTRES=gres/gpu=x does not. Is there some config option I am missing

[slurm-dev] Re: Resource limits in new partition

2017-06-18 Thread Jagga Soorma
Hey Barry, The problem is that the following command does not work for me: -- # sacctmgr modify account where Partition=gred set grptres=gres/gpu=8 Unknown option: grptres=gres/gpu=8 Use keyword 'where' to modify condition -- Keeps saying that the grptres=gres/gpu=8 is a unknown option. Am I

[slurm-dev] Incorrect error message?

2017-06-18 Thread Hugues Moreau
Hi all, I stumbled upon this stackoverflow issue , the user gets the error below. Please note I'm not asking for help about the error, I'm pointing to an issue with the error message itself: > slurmctld -cD slurmc