Re: [slurm-users] ProEpiLogInterfacePlugin -> PerilogueInterfacePlugin (E.A. Schneider @ CMU'76?)
On Fri, Feb 21, 2020 at 12:38 AM Benjamin Redling wrote: > If there isn't already a better name, I suggest > "PerilogueInterfacePlugin", because of the following possible historical > IT-roots: > > As "prologue" comes from the Greek "προ", meaning "before", and as > "epilogue" comes from the Greek "επι", meaning "after", so "perilogue" > comes from the Greek "περι", meaning "around/about". Perfectly logical, I love it. Cheers, -- Kilian
Re: [slurm-users] RHEL8 support - Missing Symbols in SelectType libraries
On 21/2/20 9:02 am, Tina Friedrich wrote: In case that's of interest - this is actually SLURM 18.08.3 that I've now gotten to run (I haven't quite managed to upgrade to 19 yet). I've made minor modifications to the spec file - the unhardening of the flags and the the python dependency. From what I can see there's a fix in for 20.02 (the same change you've added from what I can see), but it's not (yet) backported to earlier releases. commit d3b308aae6d63a9acecd50c0d63a5c8e3ff0086f Author: Tim McMullan Date: Fri Feb 14 08:25:06 2020 -0500 slurm.spec - disable "hardening" flags Disable the "hardening" flags - '-z,relro' or '-z,now' that RHEL8/Fedora inject by default which break Slurm's plugin stack. Bug 8499. -- Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA
Re: [slurm-users] Is it safe to convert cons_res to cons_tres on a running system?
Hi Chris, If it just requires restarting slurmctld and the slurmd processes on the nodes, I will be happy! Can you confirm that no running or pending jobs were lost in the transition? Thanks, Nate On Thu, Feb 20, 2020 at 6:54 PM Chris Samuel wrote: > On 20/2/20 2:16 pm, Nathan R Crawford wrote: > > >I interpret this as, in general, changing SelectType will nuke > > existing jobs, but that since cons_tres uses the same state format as > > cons_res, it should work. > > We got caught with just this on our GPU nodes (though it was fixed > before I got to see what was going on) - it seems that the format of the > RPCs changes when you go from cons_res to cons_tres and we were having > issues until we restarted slurmd on the compute nodes as well. > > My memory is that this was causing issues for starting new jobs (in a > failing completely type of manner), I'm not sure what the consequences > were for running jobs (though I suspect it would not have been great for > them). > > If Doug sees this he may remember this (he caught and fixed it). > > All the best, > Chris > -- > Chris Samuel : http://www.csamuel.org/ : Berkeley, CA, USA > > -- Dr. Nathan Crawford nathan.crawf...@uci.edu Director of Scientific Computing School of Physical Sciences 164 Rowland Hall Office: 2101 Natural Sciences II University of California, Irvine Phone: 949-824-4508 Irvine, CA 92697-2025, USA
Re: [slurm-users] RHEL8 support - Missing Symbols in SelectType libraries
Hi James, thank you! I can confirm that 'fixes' it. slurmd now starts, the node joins the cluster, I can at least get an interactive session on it (haven't tried anything else). In case that's of interest - this is actually SLURM 18.08.3 that I've now gotten to run (I haven't quite managed to upgrade to 19 yet). I've made minor modifications to the spec file - the unhardening of the flags and the the python dependency. Tina On 21/02/2020 15:47, Erwin, James wrote: > Hi Tina, > > I also recently encountered symbol errors with slurmd on RHEL 8 , and the > work-around posted here solved the problem: > > https://klmlinks.wordpress.com/2017/11/18/bug-2443-slurmd-does-not-start-when-built-in-hardened-environment/ > > > I simply added this to the slurm.spec file: > > %undefine _hardened_build > %global _hardened_cflags “-Wl,-z,lazy” > %global _hardened_ldflags “-Wl,-z,lazy” > > > > -James > > -Original Message- > From: slurm-users On Behalf Of Tina > Friedrich > Sent: Friday, February 21, 2020 10:40 AM > To: slurm-users@lists.schedmd.com > Subject: Re: [slurm-users] RHEL8 support - Missing Symbols in SelectType > libraries > > Hello, > > shame this seems to be the last message in this thread! > > I'm currently banging against the same problem on a test system. > > Did anyone get that to run? If yes, how exactly did you build the packages? > > Tina > > On 01/11/2019 18:19, Michael Jennings wrote: >> On Friday, 01 November 2019, at 10:41:26 (-0700), Brian Andrus wrote: >> >>> That's pretty much how I did it too. >>> >>> But... >>> >>> When you try to run slurmd, it chokes on the missing symbols issue. >> >> I don't yet have a full RHEL8 cluster to test on, and this isn't >> really my area of expertise, but have you tried disabling "-Wl,-z,now" >> from $LDFLAGS during the RPM build? Since the powercap symbols are >> defined in slurmctld but not slurmd, I suspect that the symbol >> problems are related to the disabling of lazy symbol bindings. >> >> I could be completely wrong, of course, but that's what I'd try. :-) >> >> Michael >>
Re: [slurm-users] RHEL8 support - Missing Symbols in SelectType libraries
Hi Tina, I also recently encountered symbol errors with slurmd on RHEL 8 , and the work-around posted here solved the problem: https://klmlinks.wordpress.com/2017/11/18/bug-2443-slurmd-does-not-start-when-built-in-hardened-environment/ I simply added this to the slurm.spec file: %undefine _hardened_build %global _hardened_cflags “-Wl,-z,lazy” %global _hardened_ldflags “-Wl,-z,lazy” -James -Original Message- From: slurm-users On Behalf Of Tina Friedrich Sent: Friday, February 21, 2020 10:40 AM To: slurm-users@lists.schedmd.com Subject: Re: [slurm-users] RHEL8 support - Missing Symbols in SelectType libraries Hello, shame this seems to be the last message in this thread! I'm currently banging against the same problem on a test system. Did anyone get that to run? If yes, how exactly did you build the packages? Tina On 01/11/2019 18:19, Michael Jennings wrote: > On Friday, 01 November 2019, at 10:41:26 (-0700), Brian Andrus wrote: > >> That's pretty much how I did it too. >> >> But... >> >> When you try to run slurmd, it chokes on the missing symbols issue. > > I don't yet have a full RHEL8 cluster to test on, and this isn't > really my area of expertise, but have you tried disabling "-Wl,-z,now" > from $LDFLAGS during the RPM build? Since the powercap symbols are > defined in slurmctld but not slurmd, I suspect that the symbol > problems are related to the disabling of lazy symbol bindings. > > I could be completely wrong, of course, but that's what I'd try. :-) > > Michael >
Re: [slurm-users] RHEL8 support - Missing Symbols in SelectType libraries
Hello, shame this seems to be the last message in this thread! I'm currently banging against the same problem on a test system. Did anyone get that to run? If yes, how exactly did you build the packages? Tina On 01/11/2019 18:19, Michael Jennings wrote: > On Friday, 01 November 2019, at 10:41:26 (-0700), > Brian Andrus wrote: > >> That's pretty much how I did it too. >> >> But... >> >> When you try to run slurmd, it chokes on the missing symbols issue. > > I don't yet have a full RHEL8 cluster to test on, and this isn't > really my area of expertise, but have you tried disabling "-Wl,-z,now" > from $LDFLAGS during the RPM build? Since the powercap symbols are > defined in slurmctld but not slurmd, I suspect that the symbol > problems are related to the disabling of lazy symbol bindings. > > I could be completely wrong, of course, but that's what I'd try. :-) > > Michael >
[slurm-users] ProEpiLogInterfacePlugin -> PerilogueInterfacePlugin (E.A. Schneider @ CMU'76?)
Hello everybody, only yesterday I had time to review: https://slurm.schedmd.com/SLUG19/Slurm_20.02_and_Beyond.pdf " If you have a good name for this plugin type, I haven't found a good name - "ProEpiLogInterfacePlugin" is a bit unwieldy " So, I searched for a hypernym of "prologue" and "epilog" and couldn't directly find something. But IMO, I found something very closely related. If there isn't already a better name, I suggest "PerilogueInterfacePlugin", because of the following possible historical IT-roots: https://jdebp.eu/FGA/function-perilogues.html " Yes, "perilogue" is a real word — sort of. It's only ever been used as a technical term in computing, and was first used by Edward Anton Schneider of Carnegie-Mellon University in 1976 to mean the start or finish of an operation. Clearly this is a useful term for the combination of a prologue and an epilogue, which are inseparable from each other when it comes to discussions of compiled functions in computer languages, and lack another word for their combination. As "prologue" comes from the Greek "προ", meaning "before", and as "epilogue" comes from the Greek "επι", meaning "after", so "perilogue" comes from the Greek "περι", meaning "around/about". Indeed, the word "περιλεγειν" actually exists in Classical Greek, in the writings of Hermippus, meaning "to talk around" something. " Regards, Benjamin -- FSU Jena | JULIELab.de/Staff/Redling
