[mpich-discuss] hydra_pmi_proxy: error while loading shared libraries: libimf.so: cannot open shared object file: No such file or directory (Reuti)
Marcelo C. R. Melo
melomcr at gmail.com
Tue Sep 4 15:09:39 CDT 2012
Yes Reuti, the LD_LIBRARY_PATH is configured correctly.
I can use the software normally when logged into any node.
The problem is that when I Spawn another executable from my initial
launcher program, the spawned executable does not see the environment that
the launcher received.
Is there any portable way to pass the environment variables to Spawned
processes?
I posted this question on stack overflow a few days ago:
http://stackoverflow.com/questions/12252490/why-cant-and-environment-variable-be-seen-by-an-executable-if-it-is-run-on-two/12252584#comment16448588_12252584
Best regards,
Marcelo
On 4 September 2012 14:00, <mpich-discuss-request at mcs.anl.gov> wrote:
>
> Today's Topics:
>
> 1. Re: hydra_pmi_proxy: error while loading shared libraries:
> libimf.so: cannot open shared object file: No such file or
> directory (Marcelo C. R. Melo)
> 2. Re: hydra_pmi_proxy: error while loading shared libraries:
> libimf.so: cannot open shared object file: No such file or
> directory (Reuti)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 3 Sep 2012 15:33:03 -0300
> From: "Marcelo C. R. Melo" <melomcr at gmail.com>
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [mpich-discuss] hydra_pmi_proxy: error while loading
> shared libraries: libimf.so: cannot open shared object file: No
> such
> file or directory
> Message-ID:
> <
> CAAO08KuiPENRYDY_aUx9KPeaESQZA5MwN18g+FQVjxT39co16w at mail.gmail.com>
> Content-Type: text/plain; charset=ISO-8859-1
>
> Hello to all,
>
> Has there been any advances in this topic? Any solutions found?
>
> I am having the exact same problem. When I ask for just one node, my
> software runs fine. If I ask for two or more, even though I just use
> one, I get the "missing library" error.
>
> I tried an "ssh node2 ls
> /opt/intel/composerxe-2011.3.174/compiler/lib/intel64/libimf.so >>
> $log_file " inside my PBS script and the lib exists in a folder that
> the node can see.
>
> Best regards,
>
> Marcelo
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 3 Sep 2012 20:40:29 +0200
> From: Reuti <reuti at staff.uni-marburg.de>
> To: mpich-discuss at mcs.anl.gov
> Subject: Re: [mpich-discuss] hydra_pmi_proxy: error while loading
> shared libraries: libimf.so: cannot open shared object file: No
> such
> file or directory
> Message-ID:
> <57548BBE-C25F-4447-B33D-E3316DCA60E2 at staff.uni-marburg.de>
> Content-Type: text/plain; charset=us-ascii
>
> Am 03.09.2012 um 20:33 schrieb Marcelo C. R. Melo:
>
> > Hello to all,
> >
> > Has there been any advances in this topic? Any solutions found?
> >
> > I am having the exact same problem. When I ask for just one node, my
> > software runs fine. If I ask for two or more, even though I just use
> > one, I get the "missing library" error.
> >
> > I tried an "ssh node2 ls
> > /opt/intel/composerxe-2011.3.174/compiler/lib/intel64/libimf.so >>
> > $log_file " inside my PBS script and the lib exists in a folder that
> > the node can see.
>
> Is the LD_LIBRARY_PATH also set in your ~/.bashrc that it can be loaded
> automatically when you `ssh` to the node?
>
> -- Reuti
>
>
> > Best regards,
> >
> > Marcelo
> > _______________________________________________
> > mpich-discuss mailing list mpich-discuss at mcs.anl.gov
> > To manage subscription options or unsubscribe:
> > https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
>
>
> ------------------------------
>
> _______________________________________________
> mpich-discuss mailing list
> mpich-discuss at mcs.anl.gov
> https://lists.mcs.anl.gov/mailman/listinfo/mpich-discuss
>
>
> End of mpich-discuss Digest, Vol 48, Issue 1
> ********************************************
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20120904/49e2c110/attachment.html>
More information about the mpich-discuss
mailing list