On Friday, 9 November 2018 2:47:51 AM AEDT Aravindh Sampathkumar wrote:
> navtp@console2:~> ssh c07b07 id
> uid=29865(navtp) gid=510(finland) groups=510(finland),508(nav),5001(ghpc)
> context=unconfined_u:unconfined_r:unconfined_t:s0-s0:c0.c1023
Do you have SElinux configured by some chance?
If
On Saturday, 10 November 2018 6:22:26 AM AEDT Brian Andrus wrote:
> There are no firewalls and I have always been able to do 'sacctmgr show
> clusters' as well as things like 'squeue -M ALL' from both the db
> server and the cluster head.
What does "sacctmgr list clusters" say for you?
Remember
There are no firewalls and I have always been able to do 'sacctmgr show
clusters' as well as things like 'squeue -M ALL' from both the db
server and the cluster head.
For now, I will have to restart slurmctld on all the clusters when there
are changes to associations. But that is definitely
Oh, thanks Paddy for your patch, it works very well !!
Miguel A. Sánchez Gómez
System Administrator
Research Programme on Biomedical Informatics - GRIB (IMIM-UPF)
Barcelona Biomedical Research Park (office 4.80)
Doctor Aiguader 88 | 08003 Barcelona (Spain)
Phone: +34/ 93 316 0522 | Fax: +34/ 93 3
The Francis Crick Institute Limited is a registered charity in England and
Wales no. 1140062 and a company registered in England and Wales no. 06885462,
with its registered office at 1 Midland Road London NW1 1AT
--- Begin Message ---
<>--- End Message ---
> On Nov 9, 2018, at 3:14 AM, Bjørn-Helge Mevik wrote:
>
> Noam Bernstein writes:
>
>> Can anyone shed some light on where the _virtual_ memory limit comes from?
>
> Perhaps it comes from a VSizeFactor setting in slurm.conf:
>
> VSizeFactor
> Memory specifications in job re
On Friday, 9 November 2018 2:16:48 PM AEDT Noam Bernstein wrote:
> Can anyone shed some light on where the _virtual_ memory limit comes from?
>
> We're getting jobs killed with the message
> slurmstepd: error: Step 3664.0 exceeded virtual memory limit (79348101120 >
> 72638634393), being killed
Noam Bernstein writes:
> Can anyone shed some light on where the _virtual_ memory limit comes from?
Perhaps it comes from a VSizeFactor setting in slurm.conf:
VSizeFactor
Memory specifications in job requests apply to real memory size
(also known as
resident
