<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Just a quick follow up, that I could resolve the issue. Maybe this helps someone in the future.<div class=""><br class=""></div><div class=""> $BASH_ENV was pointing to a deprecated script, resetting the module environment. This only is an issue for non-interactive, non-login shells (i.e. sbatch) and the issue was therefore not seen when running in an interactive slurm session. </div><div class=""><br class=""></div><div class="">I addition „ldd“ seems to create a subprocess/shell? Using </div><div class=""><br class=""></div><div class="">/usr/lib64/ld-linux-x86-64.so.2 --list /path/to/binary</div><div class=""><br class=""></div><div class=""> did not have the described issue. </div><div class=""><br class=""></div><div class="">Concerning other self-compile binaries, which seemed to work fine: those had a set an RPATH and were therefore always finding the correct MPI libs.</div><div class=""><br class=""></div><div class="">Kind regards</div><div class="">Sebastian<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">Am 30.03.2022 um 18:08 schrieb Sebastian Potthoff <<a href="mailto:s.potthoff@uni-muenster.de" class="">s.potthoff@uni-muenster.de</a>>:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Noam,<div class=""><br class=""></div><div class="">Thanks for your suggestion - I already did this and confirmed the modules and LD_LIBARARY_PATH are set correctly. Also if there was something wrong here, all of this would not work with self-compiled binaries, which it does… which baffles me :-/</div><div class=""><br class=""></div><div class=""><div class=""><br class=""><blockquote type="cite" class=""><div class="">Am 30.03.2022 um 17:51 schrieb Bernstein, Noam CIV USN NRL (6393) Washington DC (USA) <<a href="mailto:noam.bernstein@nrl.navy.mil" class="">noam.bernstein@nrl.navy.mil</a>>:</div><br class="Apple-interchange-newline"><div class=""><meta charset="UTF-8" class=""><span style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none; float: none; display: inline !important;" class="">One possibility is that something about the environment in the running batch job is making the "module load" commands fail, which they can do without any error (for old fashioned tcl-based env modules). Do "module list" after, and echo $LD_LIBRARY_PATH, to confirm that it really is being set correctly in the batch job.</span><br class="" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;"></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></body></html>