Interesting thing I found!
As I checked the log, I saw
part_policy_valid_acct: job's account not permitted to use this
partition (RUBY allows Y8 not y8)
However, in the command I use "-A Y8" and I am sure about that. The
parts file contains
PartitionName=RUBY AllowAccounts=Y8 Nodes=compute-
Yes they are the same.
[root@rocks7 ~]# cp /etc/slurm/slurm.conf rocks7
[root@rocks7 ~]# scp compute-0-0:/etc/slurm/slurm.conf compute-0-0
slurm.conf
100% 2465 3.6MB/s 00:00
[root@rocks7 ~]# scp compute-0-1:/etc/slurm/slurm.conf compute-0-1
slurm.conf
100% 2465 4.7MB/s 00:00
[root@
Mahmood,
you should check that the slurm.conf files are identical on the head node
and the compute nodes after you run the rocks sync.
On 16 May 2018 at 11:07, Mahmood Naderan wrote:
> Yes I did that prior to my first email. However, I thought that is
> similar to the service restart bug in
Yes I did that prior to my first email. However, I thought that is
similar to the service restart bug in the roll.
As you can see below, still the configuration is said to be not available
[mahmood@rocks7 ~]$ su
Password:
[root@rocks7 mahmood]# rocks sync slurm
[root@rocks7 mahmood]# exit
exit
[
Hi Mahmood,
this question is related to the slurm-roll.
The command rocks sync slurm has more tasks:
1. Rebuild of 411 is forced
2. on compute nodes, the command /etc/slurm/slurm-prep.sh start is executed
3. on compute nodes, slurmd is restarted
4. slurmctld is restarted.
Step 1 and 2 are requi
Hi,
After creating an account and a partition, I get an error that
requested partition configuration not available now. Although I
restarted the services on all nodes, I wonder why that happen?
[root@rocks7 ~]# rocks run host compute-0-0 "systemctl restart slurmd"
[root@rocks7 ~]# rocks run host c
