LAM/MPI logo

LAM/MPI General User's Mailing List Archives

  |   Home   |   Download   |   Documentation   |   FAQ   |   all just in this list

From: Vishal Sahay (vsahay_at_[hidden])
Date: 2004-03-20 17:11:37


This thread was taken off list. To tie up the thread here, the problem was
because of improper LAM installation, building LAM again solved the
problem.

-Vishal

On Fri, 20 Feb 2004, Pirabhu Raman wrote:

# Hey Vishal,
#
# The error in earlier mail was typo. I had actually used ./configure
# --with-blcr=/usr/local --with-rpi=crtcp. I double checked with config.log.
# The error with cr_restart was also my mistake. I did the right thing and
# typed the wrong thing in mail. I did use the file name.
#
# The output of laminfo is given below :
# LAM/MPI: 7.0.4
# Prefix: /usr/local
# Architecture: i686-pc-linux-gnu
# Configured by: root
# Configured on: Tue Feb 17 13:04:10 CST 2004
# Configure host: ft0
# C bindings: yes
# C++ bindings: yes
# Fortran bindings: yes
# C profiling: yes
# C++ profiling: yes
# Fortran profiling: yes
# ROMIO support: yes
# IMPI support: no
# Debug support: no
# Purify clean: no
# SSI boot: globus (Module v0.5)
# SSI boot: rsh (Module v1.0)
# SSI coll: lam_basic (Module v7.0)
# SSI coll: smp (Module v1.0)
# SSI rpi: crtcp (Module v1.0.1)
# SSI rpi: lamd (Module v7.0)
# SSI rpi: sysv (Module v7.0)
# SSI rpi: tcp (Module v7.0)
# SSI rpi: usysv (Module v7.0)
# SSI cr: blcr (Module v1.0.1)
#
# It seem to say blcr is installed. I am a little lost :) I am attaching the
# config.log files.
#
# Thanks in Advance,
# Pirabhu
#
# ----Original Message Follows----
# From: Vishal Sahay <vsahay_at_[hidden]>
# Reply-To: General LAM/MPI mailing list <lam_at_[hidden]>
# To: General LAM/MPI mailing list <lam_at_[hidden]>
# Subject: Re: LAM: BLCR help
# Date: Thu, 19 Feb 2004 20:22:10 -0500 (EST)
#
# Hi --
#
# Some more pointers --
#
# - The output of "laminfo" will give you complete list of the modules that
# have been installed. This will help you to track whether cr with blcr
# module was built or not.
#
# - For the cr_restart command, the argument is a context file (context.pid)
# and not "pid".
#
# -Vishal
#
# On Thu, 19 Feb 2004, Vishal Sahay wrote:
#
# # Hi --
# #
# # # Since I did not specify prefix option BLCR was installed in default
# # # /usr/local folder. Then I installed lam with commands
# # # configure --with-blcr=/usr/local --with-rpi-crtcp
# #
# # The configure switch to enable crtcp as default is --with-rpi=crtcp (NOTE
# # "equals" -- not a "dash")
# #
# # For blcr to work, atleast "gm" or "crtcp" rpi should be set as default. In
# # your case, --with-rpi-crtcp did not work, and hence blcr module was not
# # configured (as you saw in the error message you got while using -ssi cr
# # blcr). You can check the output of config.log to confirm this.
# #
# # I think this lead to all other problems you got after that.
#
# #
# # If your problem persists, send across the config.log, which can help
# # pinpoint the problem.
# #
# # Hope this helps...
# #
# # -Vishal
# #
# # #
# # # Now when I do check point of ordinary processes using blcr it works
# fine. I
# # # started lamboot and then I invoked a parallel process with command
# # # mpirun -ssi rpi crtcp -ssi cr blcr -np 4 ./ring
# # # This produces error stating blcr module in CR kind was not found. This
# # # typically means you have misspelled the module name.
# # #
# # # So I ran the program with command
# # # mpirun -ssi rpi crtcp -np 4 ./ring
# # # and it works fine. Now I checkpoint with the command
# # # cr_checkpoint 23245 where 23245 is PID of mpirun. One file named
# # # context.23245 is created and no other files are created (Should other
# files
# # # be created). This file is created on node where I run command
# cr_checkpoint.
# # # (Note I don't have NFS on my test cluster)
# # #
# # # When I try to restart the original program from context file with
# command
# # # cr_restart 23245 I get the error
# # # mpirun (rpwait) : bad file descriptor. (Note: The original process has
# # # already completed execution)
# # #
# # # Please let me know if these errors are due to some lapse in installation
# or
# # # if I am missing some options.
# # #
# # # Thanks in Advance,
# # # Pirabhu
# # #
# # # _________________________________________________________________
# # # Masterpieces made affordable! Buy art prints.
# # # http://go.msnserver.com/IN/42736.asp MSN Shopping.
# # #
# # # _______________________________________________
# # # This list is archived at http://www.lam-mpi.org/MailArchives/lam/
# # #
# # _______________________________________________
# # This list is archived at http://www.lam-mpi.org/MailArchives/lam/
# #
# _______________________________________________
# This list is archived at http://www.lam-mpi.org/MailArchives/lam/
#
# _________________________________________________________________
# Easiest Money Transfer to India . Send Money To 6000 Indian Towns.
# http://go.msnserver.com/IN/42198.asp Easiest Way To Send Money Home!
#