Hello. I'm getting some odd error messages in certain situations associated with the btl components (happens with both 1.0.2 and 1.1). When certain btl components are NOT loaded, openMPI issues error messages associated with those very components. For instance, consider an application that is built with an openMPI installation that was configured with mvapi and mx (in addition to tcp,sm,self). If that application is taken to a system that does not have mvapi and mx interconnects installed and is explicitly started for TCP by using "--mca btl self,tcp,sm", then the following comes from openMPI:
[devi01:01659] mca: base: component_find: unable to open: libvapi.so: cannot open shared object file: No such file or directory (ignored) [devi01:01659] mca: base: component_find: unable to open: libvapi.so: cannot open shared object file: No such file or directory (ignored) [devi01:01659] mca: base: component_find: unable to open: libmyriexpress.so: cannot open shared object file: No such file or directory (ignored) [devi02:31845] mca: base: component_find: unable to open: libvapi.so: cannot open shared object file: No such file or directory (ignored) [devi02:31845] mca: base: component_find: unable to open: libvapi.so: cannot open shared object file: No such file or directory (ignored) [devi02:31845] mca: base: component_find: unable to open: libmyriexpress.so: cannot open shared object file: No such file or directory (ignored)
These are not fatal, but they definitely give the wrong impression that something is not right. The "--mca btl self,tcp,sm" option should tell openMPI only to load loopback, tcp, and shared memory components (as these are the only btl components that should be operational on the system). The mvapi and mx components (which need libvapi.so and libmyriexpress.so, respectively), should not be loaded and thus libvapi.so and libmyriexpress.so should not be needed or even searched for. The same thing happens with "--mca btl ^mvapi,mx". Interestingly, even on a system that does have MX, the libmyriexpress.so errors show up if the mx btl component is not loaded.
Does anyone know (a) why openMPI is complaining about a shared library from a component that isn't even loaded, and (b) how to avoid the seemingly superfluous error messages? Any help is greatly appreciated.
-Patrick
<<attachment: pj.vcf>>
