Lachlan, I note that you have dropped the slurmdm and started again with an
empty database. This sounds serious!
The only thing I would suggest is an strace of the slurmctld
I often run straces when I have a proble. They never usually tell me much
but a lot of pretty text flies past ont he screen.
On 31 May 2018 at 17:00, Ole Holm Nielsen
wrote:
> Hi Lachlan,
>
> Slurm upgrades on CentOS 7.5 should run without problems. It seems to me
> that your problems are unrelated to the Slurm RPMs. FWIW, I documented the
> Munge and Slurm installation as well as upgrade process in my Wiki page
> ht
Hi,
I haven't done this upgrade but generally if I were you I would start by
verifying the simple things.
Is munge working independent of slurm? ( There is a munge encode/decode
command line floating around on the slurm web page for testing. Is munge
looking for the keys in the right place AND i
Hi Lachlan,
Slurm upgrades on CentOS 7.5 should run without problems. It seems to
me that your problems are unrelated to the Slurm RPMs. FWIW, I
documented the Munge and Slurm installation as well as upgrade process
in my Wiki page https://wiki.fysik.dtu.dk/niflheim/Slurm_installation
Hope
After last night's announcement, I decided to start the upgrade process.
Build went fine - once I worked out where munge went - and installation
also seemed fine.
slurmctld won't restart though.
In the logs I'm seeing:
[2018-05-31T15:20:50.810] debug: Munge encode failed: Failed to access
"xxx
