Hi there, I've got a test box that's been running SLURM 2.2.7, emulating a two rack Blue Gene /P that I'm attempting to upgrade to SLURM 2.3.1 (to test things before we do this upgrade on our actual Blue Gene). But I'm having a bit of trouble getting things going. I didn't think I had to make any changes to the slurm.conf file (attached) to bring up 2.3.1, but when starting the daemons (all of which are on the same box) slurmctld complains with the following when slurmd tries to connect:
slurmctld: error: Registration message from unknown node bgp000 slurmctld: error: _slurm_rpc_node_registration node=bgp000: Invalid node name specified slurmctld: debug: Spawning registration agent for slurm-dev 1 hosts slurmctld: error: Registration message from unknown node bgp000 slurmctld: error: _slurm_rpc_node_registration node=bgp000: Invalid node name specified This seems to leave the midplanes in the UNKNOWN state, and I can't get them out of this state using: scontrol update nodename=bgp000 state=idle. It responds with "slurm_update error: Invalid node state specified" The RELEASE_NOTES mention the addition of front end node configuration options so I tried adding the following to the slurm.conf file: # FRONTEND NODES #FrontendName=DEFAULT FrontendName=slurm-dev FrontendAddr=slurm-dev This didn't help though - I still had the same errors as above with the midplanes in the UNKNOWN state. Is there some other change that I have to make to the slurm.conf file for the upgrade to SLURM 2.3? Many thanks! Mark Nelson.
slurm.conf
Description: Binary data
