<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
</head>
<body dir="ltr">
<div id="divtagdefaultwrapper" dir="ltr" style="font-size:12pt; color:rgb(0,0,0); font-family:Calibri,Helvetica,sans-serif,EmojiFont,"Apple Color Emoji","Segoe UI Emoji",NotoColorEmoji,"Segoe UI Symbol","Android Emoji",EmojiSymbols">
<p style="margin-top:0; margin-bottom:0">Thank you for your reply. You're correct, the systemd commands aren't invoked, however upgrading the slurm rpm effectively pulls the rug from under /usr/sbin/slurmctld. The v17.02 slurm rpm provides /usr/sbin/slurmctld,
but from v17.11 that executable is provided by the slurm-slurmctld rpm. </p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">In other words, doing a minimal install of just the slurm and the slurmdbd rpms deletes the slurmctld executable. I haven't explicitly tested this, however I tested the upgrade on a compute node and experimented with
the slurmd -- the logic should be the same. </p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">I guess that the question that comes to mind is.. Is it a really big deal if the slurmctld process is down whilst the slurmdbd is being upgraded? Bearing in mind that I will probably opt to suspend all run jobs and stop
the partitions during the upgrade.</p>
<p style="margin-top:0; margin-bottom:0"><br>
</p>
<p style="margin-top:0; margin-bottom:0">Best regards,</p>
<p style="margin-top:0; margin-bottom:0">David</p>
<br>
<div style="color:rgb(0,0,0)">
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>From:</b> slurm-users <slurm-users-bounces@lists.schedmd.com> on behalf of Chris Samuel <chris@csamuel.org><br>
<b>Sent:</b> 26 September 2018 11:26<br>
<b>To:</b> slurm-users@lists.schedmd.com<br>
<b>Subject:</b> Re: [slurm-users] Upgrading a slurm on a cluster, 17.02 --> 18.08</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt">
<div class="PlainText">On Tuesday, 25 September 2018 11:54:31 PM AEST Baker D. J. wrote:<br>
<br>
> That will certainly work, however the slurmctld (or in the case of my test<br>
> node, the slurmd) will be killed. The logic is that at v17.02 the slurm rpm<br>
> provides slurmctld and slurmd. So upgrading that rpm will destroy/kill the<br>
> existing slurmctld or slurmd processes.<br>
<br>
If you do that with the --noscripts then will it really kill the process? <br>
Nothing should invoke the systemd commands with that, should it? Or do you <br>
mean taking the libraries, etc, away out underneath of the running process <br>
will cause it to crash?<br>
<br>
Might be worth testing that on on a VM to see if it will happen.<br>
<br>
Best of luck!<br>
Chris<br>
-- <br>
Chris Samuel : <a href="https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csamuel.org%2F&data=01%7C01%7Cd.j.baker%40soton.ac.uk%7C8b7cb9ecbbfe4644d3fa08d6239b7821%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=hdM3hZuFetDEqdCYj4VCrgCZ8hOC2FGsBuS8Ql74Ly0%3D&reserved=0" id="LPlnk112718" class="OWAAutoLink" previewremoved="true">
https://emea01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.csamuel.org%2F&data=01%7C01%7Cd.j.baker%40soton.ac.uk%7C8b7cb9ecbbfe4644d3fa08d6239b7821%7C4a5378f929f44d3ebe89669d03ada9d8%7C1&sdata=hdM3hZuFetDEqdCYj4VCrgCZ8hOC2FGsBuS8Ql74Ly0%3D&reserved=0</a>
: Melbourne, VIC<br>
<br>
<br>
<br>
<br>
</div>
</span></font></div>
</div>
</div>
</body>
</html>