Thanks Paul!

—
Christopher Coffey
High-Performance Computing
Northern Arizona University
928-523-1167
 

On 8/24/18, 12:26 PM, "slurm-users on behalf of Paul Edmon" 
<slurm-users-boun...@lists.schedmd.com on behalf of ped...@cfa.harvard.edu> 
wrote:

    There was a bug filed on this here:
    
    
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fbugs.schedmd.com%2Fshow_bug.cgi%3Fid%3D5615&amp;data=02%7C01%7Cchris.coffey%40nau.edu%7Cee3c1c1892ba492870ca08d609f77245%7C27d49e9f89e14aa099a3d35b57b2ba03%7C0%7C0%7C636707355720176333&amp;sdata=zMDdlf53FUFePgiICDI5VVjSXI8%2FToWMJisPIwPtOZg%3D&amp;reserved=0
    
    It will be fixed in 17.11.10.
    
    -Paul Edmon-
    
    
    On 08/24/2018 02:55 PM, Christopher Benjamin Coffey wrote:
    > Odd that no one has this issue. Must be a site issue then? If so, can't 
think of what that would be. I suppose we may wait for .10 to be released where 
it looks like this may be corrected.
    >
    > Best,
    > Chris
    >
    > —
    > Christopher Coffey
    > High-Performance Computing
    > Northern Arizona University
    > 928-523-1167
    >   
    >
    > On 8/20/18, 1:21 PM, "slurm-users on behalf of Christopher Benjamin 
Coffey" <slurm-users-boun...@lists.schedmd.com on behalf of 
chris.cof...@nau.edu> wrote:
    >
    >      Hi,
    >      
    >      We've just recently installed slurm 17.11.9 and noticed an issue 
with sshare:
    >      
    >      sshare: error: plugin_load_from_file: 
dlopen(/usr/lib64/slurm/priority_multifactor.so): 
/usr/lib64/slurm/priority_multifactor.so: undefined symbol: sort_part_tier
    >      sshare: error: Couldn't load specified plugin name for 
priority/multifactor: Dlopen of plugin file failed
    >      sshare: error: cannot create priority context for 
priority/multifactor
    >      
    >      Seems to be caused by new line added to:
    >      
    >      src/plugins/priority/multifactor/priority_multifactor.c
    >      
    >      list_sort(job_ptr->part_ptr_list, sort_part_tier);
    >      
    >      
    >      Looks like maybe this is a bug fixed in next slurm 17.11.10 ?
    >      
    >      
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FSchedMD%2Fslurm%2Fcommit%2F67a82c369a7530ce7838e6294973af0082d8905b%23diff-34750311c0168c98230ff16d01ea5e9b&amp;data=02%7C01%7Cchris.coffey%40nau.edu%7Cee3c1c1892ba492870ca08d609f77245%7C27d49e9f89e14aa099a3d35b57b2ba03%7C0%7C0%7C636707355720176333&amp;sdata=0yhHwGsh1OiAgJOwYUDBFdRiudfht74WNFmx7yHesQo%3D&amp;reserved=0
    >      
    >      
    >      Anyone else run into this?
    >      
    >      Best,
    >      Chris
    >      
    >      —
    >      Christopher Coffey
    >      High-Performance Computing
    >      Northern Arizona University
    >      928-523-1167
    >       
    >      
    >      
    >
    
    
    

Reply via email to