Yes you are right. I missed some options.
About --mem, it seems that without specifying that option, the srun
won't work and it says about QOS policy error. I have set an upper
limit (8G) for the user in the account. So, I expect that when I don't
specify --mem, slurm will handle that and will abor
Mahmood,
You need to put all the options to srun before the executable that you
want to run, which in this case is /bin/bash. So, it should look more like:
srun -l -a em1 -p IACTIVE --mem=4GB --pty -u /bin/bash
The way you have it most of your srun options are being interpreted as
bash argum
I tried the following command but it failed
[mahmood@rocks7 ~]$ srun --pty -u /bin/bash -l -a em1 -p IACTIVE --mem=4GB
srun: error: Unable to allocate resources: Invalid account or
account/partition combination specified
[mahmood@rocks7 ~]$ scontrol show partition IACTIVE
PartitionName=IACTIVE
On Saturday, 12 May 2018 3:35:39 PM AEST Mahmood Naderan wrote:
> Although I specified one compute node in an interactive partition, the
> salloc doesn't ssh to that node.
salloc doesn't do that.
We use a 2 line script called "sinteractive" to do this, it's really simple.
#!/bin/bash
exec srun
Hi,
Although I specified one compute node in an interactive partition, the
salloc doesn't ssh to that node. See below
[mahmood@rocks7 ~]$ scontrol show partition IACTIVE
PartitionName=IACTIVE
AllowGroups=ALL AllowAccounts=em1 AllowQos=ALL
AllocNodes=rocks7 Default=NO QoS=N/A
DefaultTime=
