problem with Mich2 installing

mahdi109 · 11-06-2011, 01:49 PM

i am trying install MPICH2 in SLES (SUSE Linux Enterprise Server 10 sp2).
now i have this error...

linux-k10z:~ # mpd &
[1] 20593
linux-k10z:~ # bash: mpd: command not found

[1]+ Exit 127 mpd
linux-k10z:~ #

what should i do?

corp769 · 11-06-2011, 01:53 PM

Hello,

I am very confused; You state you are trying to install mpich2, yet you are running mpd? What are you trying to accomplish?

Cheers,

Josh

Nylex · 11-06-2011, 01:57 PM

mpd is part of MPI implementations (such as MPICH); you need to run it before running MPI based programs (as otherwise, they'll just run in serial).

As far as the error is concerned, how did you install MPICH2 (i.e. from SLES packages or from source, if that is available)? Did the installation complete without problems? If so, it looks like the directory containing mpd isn't in your PATH.

corp769 · 11-06-2011, 02:06 PM

Quote:

Originally Posted by Nylex

mpd is part of MPI implementations (such as MPICH); you need to run it before running MPI based programs (as otherwise, they'll just run in serial).

As far as the error is concerned, how did you install MPICH2 (i.e. from SLES packages or from source, if that is available)? Did the installation complete without problems? If so, it looks like the directory containing mpd isn't in your PATH.

Ahh ok, I see what he means now. You pretty much nailed that one....

mahdi109 · 11-07-2011, 02:26 AM

thanks
i use source package (mpich2-1.4.1p1.tar.gz). i install it in the root.

# cd mpich2-1.4.1
# ./configure --prefix=/usr/local/mpich2 CC=icc CXX=icpc F77=ifort FC=ifort
# make all install

installation completed without problem. and then :

i found MPICH2 installation Guide in internet, that say to do this:
Add the MPICH2 binary directory to the system path. To add the directory to all users' PATH variables, add the following line to the /etc/profile file.
This requires root permissions and must be included prior to the "export PATH" line.
PATH=/usr/local/mpich2/bin:$PATH

i opened /ect/profile by this command:
# gedit /ect/profile
but i didn`t find right place to add " PATH=/usr/local/mpich2/bin:$PATH "
so i continue and:

# echo "secretword=TheSecretWordFoo" > /etc/mpd.conf
# chmod 600 /etc/mpd.conf

this is all i do...

Nylex · 11-07-2011, 02:34 AM

Does your /etc/profile already contain a line to set the PATH variable? If so, just add the directory to the end of it. If not, you can add the line anywhere, though you'll need the line "export PATH" somewhere after it. If you're unsure, post your /etc/profile.

colucix · 11-07-2011, 02:51 AM

You can create a script /etc/profile.d/mpich2.sh with this line inside:

Code:

export PATH=/usr/local/mpich2/bin:$PATH

The script will be automatically sourced at each login and the code providing this functionality is inside /etc/profile.

mahdi109 · 11-08-2011, 02:39 AM

Quote:

Originally Posted by Nylex

Does your /etc/profile already contain a line to set the PATH variable? If so, just add the directory to the end of it. If not, you can add the line anywhere, though you'll need the line "export PATH" somewhere after it. If you're unsure, post your /etc/profile.

this is my /ect/profile

where should i add that line?

mahdi109 · 11-08-2011, 02:42 AM

Quote:

Originally Posted by colucix

You can create a script /etc/profile.d/mpich2.sh with this line inside:

Code:

export PATH=/usr/local/mpich2/bin:$PATH

The script will be automatically sourced at each login and the code providing this functionality is inside /etc/profile.

i do that, it dosent work.

colucix · 11-08-2011, 03:16 AM

Quote:

Originally Posted by mahdi109

i do that, it dosent work.

Strange. These are the relevant statements in your /etc/profile:

Code:

#
# Source profile extensions for certain packages
#
if test -d /etc/profile.d -a -z "$PROFILEREAD" ; then
    for s in /etc/profile.d/*.sh ; do
        test -r $s && . $s
    done
    unset s
fi

This means you can put a file with extension .sh into /etc/profile.d and give it read permissions to all users, then the file will be sourced. Please, post the output of the following commands:

Code:

ls -l /etc/profile.d/mpich2.sh
cat /etc/profile.d/mpich2.sh

mahdi109 · 11-08-2011, 03:32 AM

Quote:

Originally Posted by colucix

Strange. These are the relevant statements in your /etc/profile:

Code:

#
# Source profile extensions for certain packages
#
if test -d /etc/profile.d -a -z "$PROFILEREAD" ; then
    for s in /etc/profile.d/*.sh ; do
        test -r $s && . $s
    done
    unset s
fi

This means you can put a file with extension .sh into /etc/profile.d and give it read permissions to all users, then the file will be sourced. Please, post the output of the following commands:

Code:

ls -l /etc/profile.d/mpich2.sh
cat /etc/profile.d/mpich2.sh

thanks
i make a file mpich2.sh in /etc/profile.d folder and Add export PATH=/usr/local/mpich2/bin:$PATH in it and then i do source /etc/profile.d/mpich2.sh but it dosent solve my problem.

this is the output:

linux-k10z:~ # ls -l /etc/profile.d/mpich2.sh
-rw-r--r-- 1 root root 40 Nov 8 02:38 /etc/profile.d/mpich2.sh
linux-k10z:~ # cat /etc/profile.d/mpich2.sh
export PATH=/usr/local/mpich2/bin:$PATH
linux-k10z:~ #

colucix · 11-08-2011, 05:12 AM

Ok, sorry. I was focused on the export PATH problem. Actually the mpd daemon is not installed by default, unless you specify it during the configure process. This is due to the fact you can still run your MPI jobs using mpiexec, but if you want mpd you can add the following option to the ./configure command line:

Code:

--with-pm=mpi

or

Code:

--with-pm=hydra:mpd:gforker

to build all the three process managers, as suggested in the ./configure --help documentation.

mahdi109 · 11-08-2011, 11:59 AM

Quote:

Originally Posted by colucix

Ok, sorry. I was focused on the export PATH problem. Actually the mpd daemon is not installed by default, unless you specify it during the configure process. This is due to the fact you can still run your MPI jobs using mpiexec, but if you want mpd you can add the following option to the ./configure command line:

Code:

--with-pm=mpi

or

Code:

--with-pm=hydra:mpd:gforker

to build all the three process managers, as suggested in the ./configure --help documentation.

finaly, i dont understand what to do?
dose mpiexec work?

colucix · 11-08-2011, 01:43 PM

Quote:

Originally Posted by mahdi109

finaly, i dont understand what to do?
dose mpiexec work?

If you want to run the mpd daemon you need to re-compile from mpich2-1.4.1p1.tar.gz adding the option suggested above. If you want to use mpd as the runtime environment, you need to start it before submitting your job with mpiexec or mpirun. For details, take a look at the mpich2 documentation, here.

mahdi109 · 11-09-2011, 02:05 AM

Quote:

Originally Posted by colucix

If you want to run the mpd daemon you need to re-compile from mpich2-1.4.1p1.tar.gz adding the option suggested above. If you want to use mpd as the runtime environment, you need to start it before submitting your job with mpiexec or mpirun. For details, take a look at the mpich2 documentation, here.

when i want run "mpiexec", this error appear: