On Thu, 2004-03-11 at 17:57, Ritesh Tiwari wrote:
> hello: error while loading shared libraries: libcr.so.0: cannot open
> shared object file: No such file or directory
> -----------------------------------------------------------------------------
> It seems that [at least] one of the processes that was started with
> mpirun did not invoke MPI_INIT before quitting (it is possible that
> more than one process did not invoke MPI_INIT -- mpirun was only
> notified of the first one, which was on node n0).
>
> mpirun can *only* be used with MPI programs (i.e., programs that
> invoke MPI_INIT and MPI_FINALIZE). You can use the "lamexec" program
> to run non-MPI programs over the lambooted nodes.
> -----------------------------------------------------------------------------
>
> Although as i told earlier program runs with no error in a single node
> cluster, i have checked it individually with all nodes.I have checked the
> lam/mpi mailing-list but i am not able to find out the problem.
>
> For your information, previously when i installed BLCR i gave following
> command to confiure the blcr
>
> $ ./configure --with-linux=/usr/src/linux-2.4.20-8/
> --with-system-map=/boot/System.map --prefix=/home/BLCR
>
> BLCR directory contains lib subdir* which further contains blcr subdir*
> and all lib.* files.
>
> Now i configure lam/mpi with the following command
> $ ./configure --with-blcr=/home/BLCR --with-rpi=crtcp --with-rsh="ssh -x"
>
> then..
> $ make
> $ make all install
>
> I have added following lines in .bash_profile
> LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/home/BLCR/lib
> export LD_LIBRARY_PATH
Ritesh,
I am assuming all nodes have LAM/BLCR properly installed. Then, my
guess is that your .bash_profile is not being read when you run your
program. If your $HOME is shared across the nodes, you can try to create
the file $HOME/.ssh/environment with the following lines:
PATH=/home/BLCR/bin:/usr/local/bin:/bin:/usr/bin:/usr/X11R6/bin
LD_LIBRARY_PATH=/home/BLCR/lib
MANPATH=/home/BLCR/man
Creating this file you don't need that lines int your .bash_profile.
Try this and tell if it worked, ok?
Regards,
-- Ulisses
|
