On Jul 16, 2006, at 1:54 PM, Pool, Lee, Mr <14117614_at_[hidden]> wrote:
> I'm having some trouble with getting mpiJava to work with
> lam-7.1.2! I gives me a segmentation error and says that one of the
> nodes did not call mpi_init, which cannot be the case! Is there any
> reason to suspect a problem with the signal SIGIO?
Can you run C MPI applications with your installation of LAM/MPI? If
not, it would be useful to know how those are failing.
The LAM message that one process didn't call MPI_INIT is pretty hard
to argue with -- according to LAM, at least one process didn't get
far enough through MPI_INIT to register itself as an MPI process.
This happens fairly early in MPI_INIT and is usually indicative of a
failure before MPI_INIT. Although it can occasionally indicate a
failure within LAM. We don't normally test with mpiJava, so I can't
say if there are potential issues there. What makes you think there
is a SIGIO issue? You mention it, but don't include any output that
would suggest an issue there.
Brian
--
Brian Barrett
LAM/MPI developer and all around nice guy
Have a LAM/MPI day: http://www.lam-mpi.org/
|
