Re: [slurm-users] wckey specification error

2018-05-02 Thread Chris Samuel
On Wednesday, 2 May 2018 8:50:12 PM AEST John Hearns wrote:

> One learning pointgrep -i   is a good default option.  This ignores the
> case of the search, so you would have found WCKey a bit faster.

Also if you need to search recursively below a point then:

git grep --no-index -i ${PATTERN}

will do git's grep with no need to have a git repository.  Plus it paginates, 
etc, for you.  Also pretty fast. :-)

-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC




Re: [slurm-users] wckey specification error

2018-05-02 Thread John Hearns
Mahmood, good to hear you have a solution.

One learning pointgrep -i   is a good default option.  This ignores the
case of the search, so you would have found WCKey a bit faster.


On 2 May 2018 at 04:26, Mahmood Naderan  wrote:

> Thanks Trevor for pointing out that there is an option for such thing
> is slurm.conf. Although I previously greped for *wc* and found
> nothing, the correct name is TrackWCKey which is set to "yes" by
> default. After setting that to "no", the error disappeared.
>
> About the comments on Rocks and the Slurm roll... in my experiences,
> rocks 7 is very good and the unofficial slurm roll provided by Werner
> is also very good. It is worth to give them a try. Although I had some
> experiences with manual slurm installation on an ubuntu cluster some
> years ago, the automatic installation of the roll was very nice
> indeed! All the commands and configurations can be extracted from the
> roll. So there is no dark point about that. Limited issues about
> slurm, e.g. installation, are directly related to Werner. Most of the
> other question are related to the slurm itself. For example accounting
> and other things.
>
>
> Regards,
> Mahmood
>
>
>
>
>
> On Tue, May 1, 2018 at 9:35 PM, Cooper, Trevor  wrote:
> >
> >> On May 1, 2018, at 2:58 AM, John Hearns  wrote:
> >>
> >> Rocks 7 is now available, which is based on CentOS 7.4
> >> I hate to be uncharitable, but I am not a fan of Rocks. I speak from
> experience, having installed my share of Rocks clusters.
> >> The philosophy just does not fit in with the way I look at the world.
> >>
> >> Anyway, to install extra software on Rocks you need a 'Roll'   Mahmood
> Looks like you are using this Roll
> >> https://sourceforge.net/projects/slurm-roll/
> >> It seems pretty mpdern as it installs Slurm 17.11.3
> >>
> >>
> >> On 1 May 2018 at 11:40, Chris Samuel  wrote:
> >> On Tuesday, 1 May 2018 2:45:21 PM AEST Mahmood Naderan wrote:
> >>
> >> > The wckey explanation in the manual [1] is not meaningful at the
> >> > moment. Can someone explain that?
> >>
> >> I've never used it, but it sounds like you've configured your system to
> require
> >> it (or perhaps Rocks has done that?).
> >>
> >> https://slurm.schedmd.com/wckey.html
> >>
> >> Good luck,
> >> Chris
> >> --
> >>  Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC
> >>
> >>
> >
> > The slurm-roll hosted on sourceforge is developed and supported by
> Werner Saar not by developers of Rocks and/or other Rocks application rolls
> (e.g. SDSC).
> >
> > There is ample documentation on sourceforge[1] on how to configure your
> Rocks cluster to properly deploy the slurm-roll components and update your
> Slurm configuration.
> >
> > There is also an active discussion group for the slurm-roll on
> sourceforge[2] where Werner supports users of the slurm-roll for Rocks.
> >
> > While we don't use Werner's slurm-roll on our Rocks/Slurm based systems
> I have installed it on test system and can say that it works as
> expected/documented.
> >
> > In the default configuration WCKeys were NOT enabled so this something
> that you must have added to your Slurm configuration.
> >
> > If you don't need the WCKeys capability of Slurm perhaps you could
> simply disable it in your Slurm configuration.
> >
> > Hope this helps,
> > Trevor
> >
> > [1] - https://sourceforge.net/projects/slurm-roll/files/
> release-7.0.0-17.11.05/slurm-roll.pdf
> > [2] - https://sourceforge.net/p/slurm-roll/discussion/
> >
> > --
> > Trevor Cooper
> > HPC Systems Programmer
> > San Diego Supercomputer Center, UCSD
> > 9500 Gilman Drive, 0505
> > La Jolla, CA 92093-0505
> >
>
>


Re: [slurm-users] wckey specification error

2018-05-01 Thread Mahmood Naderan
Thanks Trevor for pointing out that there is an option for such thing
is slurm.conf. Although I previously greped for *wc* and found
nothing, the correct name is TrackWCKey which is set to "yes" by
default. After setting that to "no", the error disappeared.

About the comments on Rocks and the Slurm roll... in my experiences,
rocks 7 is very good and the unofficial slurm roll provided by Werner
is also very good. It is worth to give them a try. Although I had some
experiences with manual slurm installation on an ubuntu cluster some
years ago, the automatic installation of the roll was very nice
indeed! All the commands and configurations can be extracted from the
roll. So there is no dark point about that. Limited issues about
slurm, e.g. installation, are directly related to Werner. Most of the
other question are related to the slurm itself. For example accounting
and other things.


Regards,
Mahmood





On Tue, May 1, 2018 at 9:35 PM, Cooper, Trevor  wrote:
>
>> On May 1, 2018, at 2:58 AM, John Hearns  wrote:
>>
>> Rocks 7 is now available, which is based on CentOS 7.4
>> I hate to be uncharitable, but I am not a fan of Rocks. I speak from 
>> experience, having installed my share of Rocks clusters.
>> The philosophy just does not fit in with the way I look at the world.
>>
>> Anyway, to install extra software on Rocks you need a 'Roll'   Mahmood Looks 
>> like you are using this Roll
>> https://sourceforge.net/projects/slurm-roll/
>> It seems pretty mpdern as it installs Slurm 17.11.3
>>
>>
>> On 1 May 2018 at 11:40, Chris Samuel  wrote:
>> On Tuesday, 1 May 2018 2:45:21 PM AEST Mahmood Naderan wrote:
>>
>> > The wckey explanation in the manual [1] is not meaningful at the
>> > moment. Can someone explain that?
>>
>> I've never used it, but it sounds like you've configured your system to 
>> require
>> it (or perhaps Rocks has done that?).
>>
>> https://slurm.schedmd.com/wckey.html
>>
>> Good luck,
>> Chris
>> --
>>  Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC
>>
>>
>
> The slurm-roll hosted on sourceforge is developed and supported by Werner 
> Saar not by developers of Rocks and/or other Rocks application rolls (e.g. 
> SDSC).
>
> There is ample documentation on sourceforge[1] on how to configure your Rocks 
> cluster to properly deploy the slurm-roll components and update your Slurm 
> configuration.
>
> There is also an active discussion group for the slurm-roll on sourceforge[2] 
> where Werner supports users of the slurm-roll for Rocks.
>
> While we don't use Werner's slurm-roll on our Rocks/Slurm based systems I 
> have installed it on test system and can say that it works as 
> expected/documented.
>
> In the default configuration WCKeys were NOT enabled so this something that 
> you must have added to your Slurm configuration.
>
> If you don't need the WCKeys capability of Slurm perhaps you could simply 
> disable it in your Slurm configuration.
>
> Hope this helps,
> Trevor
>
> [1] - 
> https://sourceforge.net/projects/slurm-roll/files/release-7.0.0-17.11.05/slurm-roll.pdf
> [2] - https://sourceforge.net/p/slurm-roll/discussion/
>
> --
> Trevor Cooper
> HPC Systems Programmer
> San Diego Supercomputer Center, UCSD
> 9500 Gilman Drive, 0505
> La Jolla, CA 92093-0505
>



Re: [slurm-users] wckey specification error

2018-05-01 Thread Cooper, Trevor

> On May 1, 2018, at 2:58 AM, John Hearns  wrote:
> 
> Rocks 7 is now available, which is based on CentOS 7.4
> I hate to be uncharitable, but I am not a fan of Rocks. I speak from 
> experience, having installed my share of Rocks clusters.
> The philosophy just does not fit in with the way I look at the world.
> 
> Anyway, to install extra software on Rocks you need a 'Roll'   Mahmood Looks 
> like you are using this Roll
> https://sourceforge.net/projects/slurm-roll/
> It seems pretty mpdern as it installs Slurm 17.11.3
> 
> 
> On 1 May 2018 at 11:40, Chris Samuel  wrote:
> On Tuesday, 1 May 2018 2:45:21 PM AEST Mahmood Naderan wrote:
> 
> > The wckey explanation in the manual [1] is not meaningful at the
> > moment. Can someone explain that?
> 
> I've never used it, but it sounds like you've configured your system to 
> require 
> it (or perhaps Rocks has done that?).
> 
> https://slurm.schedmd.com/wckey.html
> 
> Good luck,
> Chris
> -- 
>  Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC
> 
> 

The slurm-roll hosted on sourceforge is developed and supported by Werner Saar 
not by developers of Rocks and/or other Rocks application rolls (e.g. SDSC).

There is ample documentation on sourceforge[1] on how to configure your Rocks 
cluster to properly deploy the slurm-roll components and update your Slurm 
configuration.

There is also an active discussion group for the slurm-roll on sourceforge[2] 
where Werner supports users of the slurm-roll for Rocks.

While we don't use Werner's slurm-roll on our Rocks/Slurm based systems I have 
installed it on test system and can say that it works as expected/documented.

In the default configuration WCKeys were NOT enabled so this something that you 
must have added to your Slurm configuration.

If you don't need the WCKeys capability of Slurm perhaps you could simply 
disable it in your Slurm configuration.

Hope this helps,
Trevor

[1] - 
https://sourceforge.net/projects/slurm-roll/files/release-7.0.0-17.11.05/slurm-roll.pdf
[2] - https://sourceforge.net/p/slurm-roll/discussion/

--
Trevor Cooper
HPC Systems Programmer
San Diego Supercomputer Center, UCSD
9500 Gilman Drive, 0505
La Jolla, CA 92093-0505



Re: [slurm-users] wckey specification error

2018-05-01 Thread John Hearns
I quickly downloaded that roll and unpacked the RPMs.
I cannot quite see how SLurm is configured, so to my shame I gave up (I did
say that Rocks was not my thing)

On 1 May 2018 at 11:58, John Hearns  wrote:

> Rocks 7 is now available, which is based on CentOS 7.4
> I hate to be uncharitable, but I am not a fan of Rocks. I speak from
> experience, having installed my share of Rocks clusters.
> The philosophy just does not fit in with the way I look at the world.
>
> Anyway, to install extra software on Rocks you need a 'Roll'   Mahmood
> Looks like you are using this Roll
> https://sourceforge.net/projects/slurm-roll/
> It seems pretty mpdern as it installs Slurm 17.11.3
>
>
>
>
> On 1 May 2018 at 11:40, Chris Samuel  wrote:
>
>> On Tuesday, 1 May 2018 2:45:21 PM AEST Mahmood Naderan wrote:
>>
>> > The wckey explanation in the manual [1] is not meaningful at the
>> > moment. Can someone explain that?
>>
>> I've never used it, but it sounds like you've configured your system to
>> require
>> it (or perhaps Rocks has done that?).
>>
>> https://slurm.schedmd.com/wckey.html
>>
>> Good luck,
>> Chris
>> --
>>  Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC
>>
>>
>>
>


Re: [slurm-users] wckey specification error

2018-05-01 Thread Chris Samuel
On Tuesday, 1 May 2018 2:45:21 PM AEST Mahmood Naderan wrote:

> The wckey explanation in the manual [1] is not meaningful at the
> moment. Can someone explain that?

I've never used it, but it sounds like you've configured your system to require 
it (or perhaps Rocks has done that?).

https://slurm.schedmd.com/wckey.html

Good luck,
Chris
-- 
 Chris Samuel  :  http://www.csamuel.org/  :  Melbourne, VIC




[slurm-users] wckey specification error

2018-04-30 Thread Mahmood Naderan
Hi,
I can not figure out why the following mpi script failed to start.

[siadati@rocks7 ~]$ sacctmgr list association
format=partition,account,user,grptres | grep siadati
   othersem1siadati  cpu=6,mem=8G
[siadati@rocks7 ~]$ cat slurm_script.sh
#!/bin/bash
#SBATCH --output=test.out
#SBATCH --job-name=lam
#SBATCH --ntasks=6
#SBATCH --partition=OTHERS
/share/apps/lammps-16Mar18/src/lmp_mpi < /share/apps/lammps-16Mar18/bench/in.lj
[siadati@rocks7 ~]$ sbatch slurm_script.sh
sbatch: error: Batch job submission failed: Invalid wckey specification
[siadati@rocks7 ~]$


The wckey explanation in the manual [1] is not meaningful at the
moment. Can someone explain that?

[1] https://slurm.schedmd.com/squeue.html

Regards,
Mahmood