[Aces-support] mpich/1.2.7p1/pgi error

Huajian Yao hjyao at MIT.EDU
Sun Jul 29 17:14:26 EDT 2007


Hi all,

I got a problem when I use mpich/1.2.7p1/pgi mpif90 to run a code
on cluster. The error info are :
----------------------------------------------------------------------------
gnu/3.3.3(34):ERROR:150: Module 'gnu/3.3.3' conflicts with the currently loaded
module(s) 'pgi/5.2'
gnu/3.3.3(34):ERROR:102: Tcl command execution failed: conflict pgi

./nas.rayl: /net/geo/u/local/pkg/pgi/pgi-5.2/linux86/5.2/lib/libpthread.so.0:
version `GLIBC_2.3.3' not found (required by /lib/tls/
librt.so.1)
mpiexec: Warning: task 0 exited with status 1.
----------------------------------------------------------------------------

The original codes were complied with pgi/pgf90 and mpich/1.2.7p1/pgi/mpif90.
And I do not load gnu/3.3.3, so I cannot figure out why Module 'gnu/3.3.3'
conflicts with the currently loaded module(s) 'pgi/5.2'. Does anybody know how
I can fix this problem. Thanks a lot!


Besides I attach my pbs file below:

*************************************************************************
#----------------------------------------------
# o User notification
# -m {a|b|e}
# Send mail to the user when:
# job aborts: "a", job begins running: "b", job ends: "e"

#PBS -m ae

# To ask for N nodes use "nodes=N"
# To ask for 2 processor per node use ":ppn=2", otherwise ":ppn=1"
# after the nodes=N. Preferably use ppn=2 and ask for less nodes.
# To ask for Myrinet use ":myrinet", for Gigabit Ethernet use ":gigabit"
# after the nodes=N:ppn=M
# To specify total wallclock time use "walltime=hh:mm:ss"

#PBS -l nodes=16:ppn=2

#----------------------------------------------
# o stderr/out combination
# -j {eo|oe}
# Causes the standard error and standard output to be combined in one file.
# For standard output to be added to standard error use "eo"
# For standard error to be added to standard output  use "oe"
#
# o stderr/out (specify them instead if getting script.[oe]$PBS_JOBID
# -e standard error file
# -o standard output file
# You can append ${PBS_JOBID} to ensure distict filenames

#PBS -e myrunMPICH.stderr
#PBS -o myrunMPICH.stdout

#----------------------------------------------
# o Starting time
# -a time
# Declares the time after which the job is eligible for execution.

#----------------------------------------------
# o User notification
# -m {a|b|e}
# Send mail to the user when:
# job aborts: "a", job begins running: "b", job ends: "e"

#PBS -m ae

#----------------------------------------------
# o Exporting of environment
# -V export all my environment var's

#PBS -V

#----------------------------------------------

# Begin execution

#
# Check the environment variables
#
#printenv

#module load pgi
#
# Get the right MPICH module
# Different modules for the Intel, Portland Group or GNU compilers
#
#module add mpich/1.2.6/intel
#module add mpich/1.2.6/gnu
#module add mpich/1.2.7p1/intel
module add mpich/1.2.7p1/pgi
#module add mpich/1.2.7p1/gnu
# Need this!
module add mpiexec
setenv PBS_DEFAULT `echo $PBS_NODEFILE | awk -F. '{print $2}'`
#
# get PBS node info
#
echo $PBS_NODEFILE
cat  $PBS_NODEFILE

#----------------------------------------------
# cd to the working directory from which the job was submitted
#
cd $PBS_O_WORKDIR

# How many procs do I have?
setenv NP `wc -l $PBS_NODEFILE | awk '{print $1}'`

# Create uniq hostfile for use in hybrid (MPI/OpenMP) codes and for rsh-script
use
uniq $PBS_NODEFILE > machinefile.uniq.$PBS_JOBID

# How many nodes do I have?
setenv NPU `wc -l machinefile.uniq.$PBS_JOBID | awk '{print $1}'`

#
# Run the MPI code called "executable", provided it is in PBS_O_WORKDIR
#
#mpiexec -comm p4 -n $NP ./executable
# or if you want to use all processors anyway in which case you do not
# have to figure out what NP is above:
mpiexec -comm p4 ./nas.rayl < input.Moho46.in

# Cleanup
# Remove the unique machinefiles
rm $PBS_O_WORKDIR/machinefile.uniq.$PBS_JOBID

#
# Exit (not strictly necessary)
#
exit


-- 
54-521, MIT, 77 Mass. Ave.
Cambridge MA, USA, 02139
Tel: 617-253-6389
Email: hjyao at mit.edu






More information about the Aces-support mailing list