Hi,
I understand that the simplest explanation for your problems are the security updates. However, we have done the updates on our test clusters and many other systems already, where no such effect occurred. Besides, slurm packages where not part of the update. So I can only assume that some other changes you have made on the cluster caused this and the effect of it was only visible after the reboot. The only option left for you is to debug the issue.
OK, good to know. I had thought it was odd that Slurm would have been affected, so we will now focus on any changes we had made prior to installing the security update. Thanks! Dave -- David M. Whipp Professor of Geodynamic Modelling Institute of Seismology Helsinki Institute of Sustainability Science (HELSUS) University of Helsinki +358 (0)2 941 51617 www.helsinki.fi/geodynamics
On 20. Sep 2021, at 15.08, Roland Fehrenbacher <rf@q-leap.de> wrote:
"D" == Whipp, David M <david.whipp@helsinki.fi> writes:
Hi Dave,
D> I suppose my feeling was that our cluster was working properly, I D> installed two security updates, and then things that had be D> functioning properly previously were no longer working. I did not D> mask any services myself, so I was thinking that something in the D> security updates may have done so. Given this, and the fact the D> cluster did not return to operating as it had, my view was that D> perhaps this was unexpected behaviour and/or possibly a bug. Both D> points 1 and 2 in my original message, as far as I can tell, are D> issues that appeared after rebooting the head node following the D> security update installations.
I understand that the simplest explanation for your problems are the security updates. However, we have done the updates on our test clusters and many other systems already, where no such effect occurred. Besides, slurm packages where not part of the update. So I can only assume that some other changes you have made on the cluster caused this and the effect of it was only visible after the reboot. The only option left for you is to debug the issue.
Best,
Roland _______________________________________________ Qlustar General mailing list -- qlustar-general@qlustar.org To unsubscribe send an email to qlustar-general-leave@qlustar.org