January 2015 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Problem installing MPICH
by 朱学明 19 Jan '15

19 Jan '15

Hello Balaji and all, I am trying to install MPICH-3.1 on our supercomputer with linux system. I have got the same error as Sahar Amir as follow. It sounds like that Sahar had worked with the option "--disable-maintainer-mode", but it still can not work for me. Anyone can give me some suggestions? I would like to appreciate to you very much. Regards. *Xueming Zhu 朱学明* Key Laboratory of Research on Marine Hazards Forecasting (*LoMF*), SOA National Marine Environmental Forecasting Center (*NMEFC*) No.8 Dahuisi Road, Haidian District, Beijing, 100081 People's Republic of China Tel: +86-10-82481923 在 2014/8/5 23:17, Sahar Amir 写道: > > Good morning, > > I am trying to install MPICH on my mac. however when I try to apply > the instruction make 2>&1 | tee m.log > > It gives: > CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh > /Data_1/mpich-3.1.2/confdb/missing aclocal-1.14 -I confdb > /Data_1/mpich-3.1.2/confdb/missing: line 81: aclocal-1.14: command not > found > WARNING: 'aclocal-1.14' is missing on your system. > You should only need it if you modified 'acinclude.m4' or > 'configure.ac <http://configure.ac>' or m4 files included by > 'configure.ac <http://configure.ac>'. > The 'aclocal' program is part of the GNU Automake package: > <http://www.gnu.org/software/automake> > It also requires GNU Autoconf, GNU m4 and Perl in order to run: > <http://www.gnu.org/software/autoconf> > <http://www.gnu.org/software/m4/> > <http://www.perl.org/> > make: *** [aclocal.m4] Error 127 > > > Regards, > Sahar > > ------------------------------------------------------------------------ > This message and its contents, including attachments are intended > solely for the original recipient. If you are not the intended > recipient or have received this message in error, please notify me > immediately and delete this message from your computer system. Any > unauthorized use or distribution is prohibited. Please consider the > environment before printing this email. > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH 2 script to MPICH 3
by Balaji, Pavan 19 Jan '15

19 Jan '15

FYI, mpd uses ssh also, so that shouldn't be an issue. I wouldn't recommend the manual launch. It's only meant for tools developers who build stuff on top of Hydra. AFAICT, you can remove most of the mpd management code in your script and simply pass the host list to mpiexec in Hydra: http://wiki.mpich.org/mpich/index.php/Using_the_Hydra_Process_Manager If Condor stores the host list allocated for your job somewhere, try passing it to Hydra with the "-f" option to mpiexec. -- Pavan > On Jan 19, 2015, at 10:04 AM, Kenneth Raffenetti <raffenet(a)mcs.anl.gov> wrote: > > Hi Livan, > > It should be possible to convert your script to use Hydra. Hydra has 2 main components. The first is the main hydra executable - mpiexec. The other is the hydra_pmi_proxy. > > In a normal ssh launched scenario, mpiexec will launch proxies on all nodes being used for the job, and those proxies will launch the mpi processes. > > If ssh is not possible in your setup, you should be able to utilize the hydra manual laucher (mpiexec -launcher manual). When you run mpiexec with that parameter, it will output the proxy launch commands that can be used to connect to it. It will then wait for all the proxies to connect. Here's an example: > > raffenet@doom:mpich/ $ mpiexec -launcher manual -n 3 -hosts a,b,c /bin/hostname > HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 0 > HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 1 > HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 2 > HYDRA_LAUNCH_END > > Let me know if you have other questions. > > Ken > > On 01/19/2015 05:39 AM, Livan Valladares wrote: >> Hello, >> I have been using Htcondor with MPICH 2 but I update MPICH 2 to MPICH 3 and now the MPD process manager has been deprecated and Hydra is de default process manager. >> The script I was using use some commands like mpdtrace, mpdallexit but they are not supported anymore. >> Here is my script, is it any possibility to change this script code to be able to work with Hydra? >> Thank you very much, >> Livan Valladares Martell >> Script: >> >> #!/bin/sh >> >> ##************************************************************** >> ## >> ## Copyright (C) 1990-2014, Condor Team, Computer Sciences Department, >> ## University of Wisconsin-Madison, WI. >> ## >> ## Licensed under the Apache License, Version 2.0 (the "License"); you >> ## may not use this file except in compliance with the License. You may >> ## obtain a copy of the License at >> ## >> ## http://www.apache.org/licenses/LICENSE-2.0 >> ## >> ## Unless required by applicable law or agreed to in writing, software >> ## distributed under the License is distributed on an "AS IS" BASIS, >> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. >> ## See the License for the specific language governing permissions and >> ## limitations under the License. >> ## >> ##************************************************************** >> >> >> # Set this to the bin directory of MPICH installation >> MPDIR=/opt/local/bin >> PATH=$MPDIR:.:$PATH >> export PATH >> >> _CONDOR_PROCNO=$_CONDOR_PROCNO >> _CONDOR_NPROCS=$_CONDOR_NPROCS >> >> # Remove the contact file, so if we are held and released >> # it can be recreated anew >> >> rm -f $CONDOR_CONTACT_FILE >> >> PATH=`condor_config_val libexec`/:$PATH >> >> # mpd needs a conf file, and it must be >> # permissions 0700 >> mkdir tmp >> MPD_CONF_FILE=`pwd`/tmp/mpd_conf_file >> export MPD_CONF_FILE >> >> ulimit -c 0 >> >> # If you have a shared file system, maybe you >> # want to put the mpd.conf file in your home >> # directory >> >> echo "password=somepassword" > $MPD_CONF_FILE >> chmod 0700 $MPD_CONF_FILE >> >> # If on the head node, start mpd, get the port and host, >> # and condor_chirp it back into the ClassAd >> # so the non-head nodes can find the head node. >> >> if [ $_CONDOR_PROCNO -eq 0 ] >> then >> mpd > mpd.out.$_CONDOR_PROCNO 2>&1 & >> sleep 1 >> host=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $1}'` >> port=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $2}'` >> >> condor_chirp set_job_attr MPICH_PORT $port >> condor_chirp set_job_attr MPICH_HOST \"$host\" >> >> num_hosts=1 >> retries=0 >> while [ $num_hosts -ne $_CONDOR_NPROCS ] >> do >> num_hosts=`mpdtrace | wc -l` >> sleep 2 >> retries=`expr $retries + 1` >> if [ $retries -gt 100 ] >> then >> echo "Too many retries, could not start all $_CONDOR_NPROCS nodes, only started $num_hosts, giving up. Here are the hosts I could start " >> mpdtrace >> exit 1 >> fi >> done >> >> ## run the actual mpi job, which was the command line argument >> ## to the invocation of this shell script >> mpiexec -n $_CONDOR_NPROCS $@ >> e=$? >> >> mpdallexit >> sleep 20 >> echo $e >> else >> # If NOT the head node, acquire the host and port of >> # the head node >> retries=0 >> host=UNDEFINED >> while [ $host == "UNDEFINED" ] >> do >> host=`condor_chirp get_job_attr MPICH_HOST` >> sleep 2 >> retries=`expr $retries + 1` >> if [ $retries -gt 100 ]; then >> echo "Too many retries, could not get mpd host from condor_chirp, giving up." >> exit 1 >> fi >> done >> >> port=`condor_chirp get_job_attr MPICH_PORT` >> host=`echo $host | tr -d '"'` >> mpd --host=$host --port=$port > mpd.out.$_CONDOR_PROCNO 2>&1 >> fi >> >> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Pavan Balaji ✉️ http://www.mcs.anl.gov/~balaji _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] error installing mpich-master-v3.2a2-113-g7d59d14d on Linux
by Junchao Zhang 19 Jan '15

19 Jan '15

One more thing: after updating your automake to 1.15, you also need to re-run autogen.sh --Junchao Zhang On Mon, Jan 19, 2015 at 10:44 AM, Junchao Zhang <jczhang(a)mcs.anl.gov> wrote: > Update to automake 1.15 will solve the problem. > > --Junchao Zhang > > On Mon, Jan 19, 2015 at 10:24 AM, Siegmar Gross < > Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > >> Hi, >> >> today I tried to install mpich-master-v3.2a2-113-g7d59d14d on my >> machines (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux >> 12.1 x86_64) with gcc-4.9.2 and Sun C 5.13. I succedded on both >> Solaris machines with both compilers and got the following error >> on Linux for both compilers. >> >> tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 304 cat >> log.make.Linux.x86_64.64_gcc >> if test ! -h ./src/include/mpio.h ; then \ >> rm -f ./src/include/mpio.h ; \ >> ( cd ./src/include && \ >> ln -s ../mpi/romio/include/mpio.h ) ; \ >> fi >> make all-recursive >> make[1]: Entering directory >> `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' >> make[1]: execvp: /bin/sh: Argument list too long >> make[1]: *** [all-recursive] Error 127 >> make[1]: Leaving directory >> `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' >> make: *** [all] Error 2 >> tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 305 >> >> >> I used the following "configure" command. >> >> ../mpich-master-v3.2a2-113-g7d59d14d/configure >> --prefix=/usr/local/mpich-3.2_64_gcc \ >> --libdir=/usr/local/mpich-3.2_64_gcc/lib64 \ >> --includedir=/usr/local/mpich-3.2_64_gcc/include64 \ >> CC="gcc" CXX="g++" F77="gfortran" FC="gfortran" \ >> CFLAGS="-m64" CXXFLAGS="-m64" FFLAGS="-m64" FCFLAGS="-m64" \ >> LDFLAGS="-m64 -L/usr/lib/sparcv9 -Wl,-rpath -Wl,/usr/lib/sparcv9" \ >> --enable-f77 --enable-fc --enable-cxx --enable-romio \ >> --enable-debuginfo --enable-smpcoll \ >> --enable-threads=runtime --with-thread-package=posix \ >> --enable-shared \ >> |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc >> >> >> I would be grateful if somebody can fix the problem. Thank you very >> much for any help in advance. >> >> >> Kind regards >> >> Siegmar >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] error installing mpich-master-v3.2a2-113-g7d59d14d on Linux
by Junchao Zhang 19 Jan '15

19 Jan '15

Update to automake 1.15 will solve the problem. --Junchao Zhang On Mon, Jan 19, 2015 at 10:24 AM, Siegmar Gross < Siegmar.Gross(a)informatik.hs-fulda.de> wrote: > Hi, > > today I tried to install mpich-master-v3.2a2-113-g7d59d14d on my > machines (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux > 12.1 x86_64) with gcc-4.9.2 and Sun C 5.13. I succedded on both > Solaris machines with both compilers and got the following error > on Linux for both compilers. > > tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 304 cat > log.make.Linux.x86_64.64_gcc > if test ! -h ./src/include/mpio.h ; then \ > rm -f ./src/include/mpio.h ; \ > ( cd ./src/include && \ > ln -s ../mpi/romio/include/mpio.h ) ; \ > fi > make all-recursive > make[1]: Entering directory > `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' > make[1]: execvp: /bin/sh: Argument list too long > make[1]: *** [all-recursive] Error 127 > make[1]: Leaving directory > `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' > make: *** [all] Error 2 > tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 305 > > > I used the following "configure" command. > > ../mpich-master-v3.2a2-113-g7d59d14d/configure > --prefix=/usr/local/mpich-3.2_64_gcc \ > --libdir=/usr/local/mpich-3.2_64_gcc/lib64 \ > --includedir=/usr/local/mpich-3.2_64_gcc/include64 \ > CC="gcc" CXX="g++" F77="gfortran" FC="gfortran" \ > CFLAGS="-m64" CXXFLAGS="-m64" FFLAGS="-m64" FCFLAGS="-m64" \ > LDFLAGS="-m64 -L/usr/lib/sparcv9 -Wl,-rpath -Wl,/usr/lib/sparcv9" \ > --enable-f77 --enable-fc --enable-cxx --enable-romio \ > --enable-debuginfo --enable-smpcoll \ > --enable-threads=runtime --with-thread-package=posix \ > --enable-shared \ > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc > > > I would be grateful if somebody can fix the problem. Thank you very > much for any help in advance. > > > Kind regards > > Siegmar > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] discuss Digest, Vol 27, Issue 12
by Livan Valladares 19 Jan '15

19 Jan '15

Thank you very much Ken for your help. I am a newie without the knowledge to recode the script. I contacted with Htcondor admin about it. Let me see if I am lucky and they can help. My best regards, Livan Valladares Martell. > On Jan 19, 2015, at 6:24 PM, discuss-request(a)mpich.org wrote: > > Send discuss mailing list submissions to > discuss(a)mpich.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.mpich.org/mailman/listinfo/discuss > or, via email, send a message with subject or body 'help' to > discuss-request(a)mpich.org > > You can reach the person managing the list at > discuss-owner(a)mpich.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of discuss digest..." > > > Today's Topics: > > 1. Re: MPICH 2 script to MPICH 3 (Kenneth Raffenetti) > 2. error installing mpich-master-v3.2a2-113-g7d59d14d on Linux > (Siegmar Gross) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Mon, 19 Jan 2015 10:04:47 -0600 > From: Kenneth Raffenetti <raffenet(a)mcs.anl.gov> > To: <discuss(a)mpich.org> > Subject: Re: [mpich-discuss] MPICH 2 script to MPICH 3 > Message-ID: <54BD2B1F.7010106(a)mcs.anl.gov> > Content-Type: text/plain; charset="utf-8"; format=flowed > > Hi Livan, > > It should be possible to convert your script to use Hydra. Hydra has 2 > main components. The first is the main hydra executable - mpiexec. The > other is the hydra_pmi_proxy. > > In a normal ssh launched scenario, mpiexec will launch proxies on all > nodes being used for the job, and those proxies will launch the mpi > processes. > > If ssh is not possible in your setup, you should be able to utilize the > hydra manual laucher (mpiexec -launcher manual). When you run mpiexec > with that parameter, it will output the proxy launch commands that can > be used to connect to it. It will then wait for all the proxies to > connect. Here's an example: > > raffenet@doom:mpich/ $ mpiexec -launcher manual -n 3 -hosts a,b,c > /bin/hostname > HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port > doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries > 10 --usize -2 --proxy-id 0 > HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port > doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries > 10 --usize -2 --proxy-id 1 > HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port > doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries > 10 --usize -2 --proxy-id 2 > HYDRA_LAUNCH_END > > Let me know if you have other questions. > > Ken > > On 01/19/2015 05:39 AM, Livan Valladares wrote: >> Hello, >> I have been using Htcondor with MPICH 2 but I update MPICH 2 to MPICH 3 and now the MPD process manager has been deprecated and Hydra is de default process manager. >> The script I was using use some commands like mpdtrace, mpdallexit but they are not supported anymore. >> Here is my script, is it any possibility to change this script code to be able to work with Hydra? >> Thank you very much, >> Livan Valladares Martell >> Script: >> >> #!/bin/sh >> >> ##************************************************************** >> ## >> ## Copyright (C) 1990-2014, Condor Team, Computer Sciences Department, >> ## University of Wisconsin-Madison, WI. >> ## >> ## Licensed under the Apache License, Version 2.0 (the "License"); you >> ## may not use this file except in compliance with the License. You may >> ## obtain a copy of the License at >> ## >> ## http://www.apache.org/licenses/LICENSE-2.0 >> ## >> ## Unless required by applicable law or agreed to in writing, software >> ## distributed under the License is distributed on an "AS IS" BASIS, >> ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. >> ## See the License for the specific language governing permissions and >> ## limitations under the License. >> ## >> ##************************************************************** >> >> >> # Set this to the bin directory of MPICH installation >> MPDIR=/opt/local/bin >> PATH=$MPDIR:.:$PATH >> export PATH >> >> _CONDOR_PROCNO=$_CONDOR_PROCNO >> _CONDOR_NPROCS=$_CONDOR_NPROCS >> >> # Remove the contact file, so if we are held and released >> # it can be recreated anew >> >> rm -f $CONDOR_CONTACT_FILE >> >> PATH=`condor_config_val libexec`/:$PATH >> >> # mpd needs a conf file, and it must be >> # permissions 0700 >> mkdir tmp >> MPD_CONF_FILE=`pwd`/tmp/mpd_conf_file >> export MPD_CONF_FILE >> >> ulimit -c 0 >> >> # If you have a shared file system, maybe you >> # want to put the mpd.conf file in your home >> # directory >> >> echo "password=somepassword" > $MPD_CONF_FILE >> chmod 0700 $MPD_CONF_FILE >> >> # If on the head node, start mpd, get the port and host, >> # and condor_chirp it back into the ClassAd >> # so the non-head nodes can find the head node. >> >> if [ $_CONDOR_PROCNO -eq 0 ] >> then >> mpd > mpd.out.$_CONDOR_PROCNO 2>&1 & >> sleep 1 >> host=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $1}'` >> port=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $2}'` >> >> condor_chirp set_job_attr MPICH_PORT $port >> condor_chirp set_job_attr MPICH_HOST \"$host\" >> >> num_hosts=1 >> retries=0 >> while [ $num_hosts -ne $_CONDOR_NPROCS ] >> do >> num_hosts=`mpdtrace | wc -l` >> sleep 2 >> retries=`expr $retries + 1` >> if [ $retries -gt 100 ] >> then >> echo "Too many retries, could not start all $_CONDOR_NPROCS nodes, only started $num_hosts, giving up. Here are the hosts I could start " >> mpdtrace >> exit 1 >> fi >> done >> >> ## run the actual mpi job, which was the command line argument >> ## to the invocation of this shell script >> mpiexec -n $_CONDOR_NPROCS $@ >> e=$? >> >> mpdallexit >> sleep 20 >> echo $e >> else >> # If NOT the head node, acquire the host and port of >> # the head node >> retries=0 >> host=UNDEFINED >> while [ $host == "UNDEFINED" ] >> do >> host=`condor_chirp get_job_attr MPICH_HOST` >> sleep 2 >> retries=`expr $retries + 1` >> if [ $retries -gt 100 ]; then >> echo "Too many retries, could not get mpd host from condor_chirp, giving up." >> exit 1 >> fi >> done >> >> port=`condor_chirp get_job_attr MPICH_PORT` >> host=`echo $host | tr -d '"'` >> mpd --host=$host --port=$port > mpd.out.$_CONDOR_PROCNO 2>&1 >> fi >> >> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > > > ------------------------------ > > Message: 2 > Date: Mon, 19 Jan 2015 17:24:22 +0100 (CET) > From: Siegmar Gross <Siegmar.Gross(a)informatik.hs-fulda.de> > To: discuss(a)mpich.org > Subject: [mpich-discuss] error installing > mpich-master-v3.2a2-113-g7d59d14d on Linux > Message-ID: <201501191624.t0JGOMgd017579(a)tyr.informatik.hs-fulda.de> > Content-Type: text/plain; charset="us-ascii" > > Hi, > > today I tried to install mpich-master-v3.2a2-113-g7d59d14d on my > machines (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux > 12.1 x86_64) with gcc-4.9.2 and Sun C 5.13. I succedded on both > Solaris machines with both compilers and got the following error > on Linux for both compilers. > > tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 304 cat log.make.Linux.x86_64.64_gcc > if test ! -h ./src/include/mpio.h ; then \ > rm -f ./src/include/mpio.h ; \ > ( cd ./src/include && \ > ln -s ../mpi/romio/include/mpio.h ) ; \ > fi > make all-recursive > make[1]: Entering directory `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' > make[1]: execvp: /bin/sh: Argument list too long > make[1]: *** [all-recursive] Error 127 > make[1]: Leaving directory `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' > make: *** [all] Error 2 > tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 305 > > > I used the following "configure" command. > > ../mpich-master-v3.2a2-113-g7d59d14d/configure --prefix=/usr/local/mpich-3.2_64_gcc \ > --libdir=/usr/local/mpich-3.2_64_gcc/lib64 \ > --includedir=/usr/local/mpich-3.2_64_gcc/include64 \ > CC="gcc" CXX="g++" F77="gfortran" FC="gfortran" \ > CFLAGS="-m64" CXXFLAGS="-m64" FFLAGS="-m64" FCFLAGS="-m64" \ > LDFLAGS="-m64 -L/usr/lib/sparcv9 -Wl,-rpath -Wl,/usr/lib/sparcv9" \ > --enable-f77 --enable-fc --enable-cxx --enable-romio \ > --enable-debuginfo --enable-smpcoll \ > --enable-threads=runtime --with-thread-package=posix \ > --enable-shared \ > |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc > > > I would be grateful if somebody can fix the problem. Thank you very > much for any help in advance. > > > Kind regards > > Siegmar >

1 0

error installing mpich-master-v3.2a2-113-g7d59d14d on Linux
by Siegmar Gross 19 Jan '15

19 Jan '15

Hi, today I tried to install mpich-master-v3.2a2-113-g7d59d14d on my machines (Solaris 10 Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1 x86_64) with gcc-4.9.2 and Sun C 5.13. I succedded on both Solaris machines with both compilers and got the following error on Linux for both compilers. tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 304 cat log.make.Linux.x86_64.64_gcc if test ! -h ./src/include/mpio.h ; then \ rm -f ./src/include/mpio.h ; \ ( cd ./src/include && \ ln -s ../mpi/romio/include/mpio.h ) ; \ fi make all-recursive make[1]: Entering directory `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' make[1]: execvp: /bin/sh: Argument list too long make[1]: *** [all-recursive] Error 127 make[1]: Leaving directory `/export2/src/mpich-3.2/mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc' make: *** [all] Error 2 tyr mpich-master-v3.2a2-113-g7d59d14d-Linux.x86_64.64_gcc 305 I used the following "configure" command. ../mpich-master-v3.2a2-113-g7d59d14d/configure --prefix=/usr/local/mpich-3.2_64_gcc \ --libdir=/usr/local/mpich-3.2_64_gcc/lib64 \ --includedir=/usr/local/mpich-3.2_64_gcc/include64 \ CC="gcc" CXX="g++" F77="gfortran" FC="gfortran" \ CFLAGS="-m64" CXXFLAGS="-m64" FFLAGS="-m64" FCFLAGS="-m64" \ LDFLAGS="-m64 -L/usr/lib/sparcv9 -Wl,-rpath -Wl,/usr/lib/sparcv9" \ --enable-f77 --enable-fc --enable-cxx --enable-romio \ --enable-debuginfo --enable-smpcoll \ --enable-threads=runtime --with-thread-package=posix \ --enable-shared \ |& tee log.configure.$SYSTEM_ENV.$MACHINE_ENV.64_gcc I would be grateful if somebody can fix the problem. Thank you very much for any help in advance. Kind regards Siegmar _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPICH 2 script to MPICH 3
by Kenneth Raffenetti 19 Jan '15

19 Jan '15

Hi Livan, It should be possible to convert your script to use Hydra. Hydra has 2 main components. The first is the main hydra executable - mpiexec. The other is the hydra_pmi_proxy. In a normal ssh launched scenario, mpiexec will launch proxies on all nodes being used for the job, and those proxies will launch the mpi processes. If ssh is not possible in your setup, you should be able to utilize the hydra manual laucher (mpiexec -launcher manual). When you run mpiexec with that parameter, it will output the proxy launch commands that can be used to connect to it. It will then wait for all the proxies to connect. Here's an example: raffenet@doom:mpich/ $ mpiexec -launcher manual -n 3 -hosts a,b,c /bin/hostname HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 0 HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 1 HYDRA_LAUNCH: /sandbox/mpich/i/bin/hydra_pmi_proxy --control-port doom:36311 --rmk user --launcher manual --demux poll --pgid 0 --retries 10 --usize -2 --proxy-id 2 HYDRA_LAUNCH_END Let me know if you have other questions. Ken On 01/19/2015 05:39 AM, Livan Valladares wrote: > Hello, > I have been using Htcondor with MPICH 2 but I update MPICH 2 to MPICH 3 and now the MPD process manager has been deprecated and Hydra is de default process manager. > The script I was using use some commands like mpdtrace, mpdallexit but they are not supported anymore. > Here is my script, is it any possibility to change this script code to be able to work with Hydra? > Thank you very much, > Livan Valladares Martell > Script: > > #!/bin/sh > > ##************************************************************** > ## > ## Copyright (C) 1990-2014, Condor Team, Computer Sciences Department, > ## University of Wisconsin-Madison, WI. > ## > ## Licensed under the Apache License, Version 2.0 (the "License"); you > ## may not use this file except in compliance with the License. You may > ## obtain a copy of the License at > ## > ## http://www.apache.org/licenses/LICENSE-2.0 > ## > ## Unless required by applicable law or agreed to in writing, software > ## distributed under the License is distributed on an "AS IS" BASIS, > ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. > ## See the License for the specific language governing permissions and > ## limitations under the License. > ## > ##************************************************************** > > > # Set this to the bin directory of MPICH installation > MPDIR=/opt/local/bin > PATH=$MPDIR:.:$PATH > export PATH > > _CONDOR_PROCNO=$_CONDOR_PROCNO > _CONDOR_NPROCS=$_CONDOR_NPROCS > > # Remove the contact file, so if we are held and released > # it can be recreated anew > > rm -f $CONDOR_CONTACT_FILE > > PATH=`condor_config_val libexec`/:$PATH > > # mpd needs a conf file, and it must be > # permissions 0700 > mkdir tmp > MPD_CONF_FILE=`pwd`/tmp/mpd_conf_file > export MPD_CONF_FILE > > ulimit -c 0 > > # If you have a shared file system, maybe you > # want to put the mpd.conf file in your home > # directory > > echo "password=somepassword" > $MPD_CONF_FILE > chmod 0700 $MPD_CONF_FILE > > # If on the head node, start mpd, get the port and host, > # and condor_chirp it back into the ClassAd > # so the non-head nodes can find the head node. > > if [ $_CONDOR_PROCNO -eq 0 ] > then > mpd > mpd.out.$_CONDOR_PROCNO 2>&1 & > sleep 1 > host=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $1}'` > port=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $2}'` > > condor_chirp set_job_attr MPICH_PORT $port > condor_chirp set_job_attr MPICH_HOST \"$host\" > > num_hosts=1 > retries=0 > while [ $num_hosts -ne $_CONDOR_NPROCS ] > do > num_hosts=`mpdtrace | wc -l` > sleep 2 > retries=`expr $retries + 1` > if [ $retries -gt 100 ] > then > echo "Too many retries, could not start all $_CONDOR_NPROCS nodes, only started $num_hosts, giving up. Here are the hosts I could start " > mpdtrace > exit 1 > fi > done > > ## run the actual mpi job, which was the command line argument > ## to the invocation of this shell script > mpiexec -n $_CONDOR_NPROCS $@ > e=$? > > mpdallexit > sleep 20 > echo $e > else > # If NOT the head node, acquire the host and port of > # the head node > retries=0 > host=UNDEFINED > while [ $host == "UNDEFINED" ] > do > host=`condor_chirp get_job_attr MPICH_HOST` > sleep 2 > retries=`expr $retries + 1` > if [ $retries -gt 100 ]; then > echo "Too many retries, could not get mpd host from condor_chirp, giving up." > exit 1 > fi > done > > port=`condor_chirp get_job_attr MPICH_PORT` > host=`echo $host | tr -d '"'` > mpd --host=$host --port=$port > mpd.out.$_CONDOR_PROCNO 2>&1 > fi > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

MPICH 2 script to MPICH 3
by Livan Valladares 19 Jan '15

19 Jan '15

Hello, I have been using Htcondor with MPICH 2 but I update MPICH 2 to MPICH 3 and now the MPD process manager has been deprecated and Hydra is de default process manager. The script I was using use some commands like mpdtrace, mpdallexit but they are not supported anymore. Here is my script, is it any possibility to change this script code to be able to work with Hydra? Thank you very much, Livan Valladares Martell Script: #!/bin/sh ##************************************************************** ## ## Copyright (C) 1990-2014, Condor Team, Computer Sciences Department, ## University of Wisconsin-Madison, WI. ## ## Licensed under the Apache License, Version 2.0 (the "License"); you ## may not use this file except in compliance with the License. You may ## obtain a copy of the License at ## ## http://www.apache.org/licenses/LICENSE-2.0 ## ## Unless required by applicable law or agreed to in writing, software ## distributed under the License is distributed on an "AS IS" BASIS, ## WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ## See the License for the specific language governing permissions and ## limitations under the License. ## ##************************************************************** # Set this to the bin directory of MPICH installation MPDIR=/opt/local/bin PATH=$MPDIR:.:$PATH export PATH _CONDOR_PROCNO=$_CONDOR_PROCNO _CONDOR_NPROCS=$_CONDOR_NPROCS # Remove the contact file, so if we are held and released # it can be recreated anew rm -f $CONDOR_CONTACT_FILE PATH=`condor_config_val libexec`/:$PATH # mpd needs a conf file, and it must be # permissions 0700 mkdir tmp MPD_CONF_FILE=`pwd`/tmp/mpd_conf_file export MPD_CONF_FILE ulimit -c 0 # If you have a shared file system, maybe you # want to put the mpd.conf file in your home # directory echo "password=somepassword" > $MPD_CONF_FILE chmod 0700 $MPD_CONF_FILE # If on the head node, start mpd, get the port and host, # and condor_chirp it back into the ClassAd # so the non-head nodes can find the head node. if [ $_CONDOR_PROCNO -eq 0 ] then mpd > mpd.out.$_CONDOR_PROCNO 2>&1 & sleep 1 host=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $1}'` port=`mpdtrace -l | sed 1q | tr '_' ' ' | awk '{print $2}'` condor_chirp set_job_attr MPICH_PORT $port condor_chirp set_job_attr MPICH_HOST \"$host\" num_hosts=1 retries=0 while [ $num_hosts -ne $_CONDOR_NPROCS ] do num_hosts=`mpdtrace | wc -l` sleep 2 retries=`expr $retries + 1` if [ $retries -gt 100 ] then echo "Too many retries, could not start all $_CONDOR_NPROCS nodes, only started $num_hosts, giving up. Here are the hosts I could start " mpdtrace exit 1 fi done ## run the actual mpi job, which was the command line argument ## to the invocation of this shell script mpiexec -n $_CONDOR_NPROCS $@ e=$? mpdallexit sleep 20 echo $e else # If NOT the head node, acquire the host and port of # the head node retries=0 host=UNDEFINED while [ $host == "UNDEFINED" ] do host=`condor_chirp get_job_attr MPICH_HOST` sleep 2 retries=`expr $retries + 1` if [ $retries -gt 100 ]; then echo "Too many retries, could not get mpd host from condor_chirp, giving up." exit 1 fi done port=`condor_chirp get_job_attr MPICH_PORT` host=`echo $host | tr -d '"'` mpd --host=$host --port=$port > mpd.out.$_CONDOR_PROCNO 2>&1 fi _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Threaded Listener
by Jeff Hammond 17 Jan '15

17 Jan '15

I see you work for IBM Research (assuming http://researcher.ibm.com/researcher/view.php?person=br-edrodri is current). If you have access to your company's digital library, you might look up the Blue Gene project, which was a low-power supercomputer running on arguably embedded processors that has no trouble running MPI using a lightweight kernel that does not support fork(), oversubscription or OS-scheduling. The MPI source code for the latest incarnation of Blue Gene (/Q) can be found in the MPICH repo, no less: http://git.mpich.org/mpich.git/tree/HEAD:/src/mpid/pamid. MPI for the previous generation of Blue Gene (/P) can be found on http://git.mpich.org/mpich.git/tree/fbe1f262b3a56898519750228278617f40bb2f3…. Documentation of DCMF is available from http://dcmf.anl-external.org/wiki/index.php/Main_Page. The PAMI source code is part of the open-source BGQ driver, which you can download from https://repo.anl-external.org/repos/bgq-driver/V1R2M2/. That may not be the latest version, but the original maintainer of the BGQ driver source repo has left the Blue Gene family. The BGQ driver source should contain other system software that is used to launch processes on the computer nodes. You might grep for "runjob", as that is the process launcher for Blue Gene/Q. Best, Jeff On Sat, Jan 17, 2015 at 12:23 PM, Eduardo <erocha.ssa(a)gmail.com> wrote: > The system is a micro-OS running in an embedded processor. There will be > multiple of these processors, each one with a single mpi rank. I'm starting > to think that I will have to do what Hydra does myself. Is there any > documentation about what a mpi job expects from hydra? > > Eduardo > > On Sat, Jan 17, 2015 at 5:58 PM, Jeff Hammond <jeff.science(a)gmail.com> > wrote: >> >> How do you create processes on this system? If you are using an MPI >> implementation that has a 1:1 mapping between MPI processes and OS >> processes, you've got to be able to create multiple processes somehow. >> >> Do you have any platform details you can share? >> >> Jeff >> >> On Sat, Jan 17, 2015 at 11:46 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: >> > I tried to use a newer MPICH, but, as you said, Hydra forks as part of >> > mpiexec. Is it possible to launch a job without mpiexec/mpirun ? That >> > should >> > probably work in my environment (assuming that there is no listener as a >> > heavy process as it is the case in the default mpich-1.2.7p1). >> > >> > The problem is not that the fork symbol is missing. The problem is that >> > it >> > is been called. My environment actually has a dummy fork, but that only >> > causes the program to abort if it is called. >> > >> > So in summary, the problem is that I cannot use mpiexec to launch a >> > program, >> > because it calls fork. In mpich-1.2.7p1 , I can launch myself the >> > program as >> > if I was launching a debug (as in section 3.5.6 of the CH_P4 manual). In >> > addition, the mpich cannot issue a fork for a listener like task, only >> > threads. >> > >> > Eduardo >> > >> > On Sat, Jan 17, 2015 at 4:23 PM, Jeff Hammond <jeff.science(a)gmail.com> >> > wrote: >> >> >> >> MPICH shouldn't fork. Hydra probably uses fork to launch processes as >> >> part >> >> of mpiexec. >> >> >> >> Blue Gene doesn't support fork either and MPICH runs there, but the >> >> process launcher is not Hydra. Same for Cray last time I checked. So >> >> I'm >> >> sure that fork isn't required to use MPICH, at least if dynamic >> >> processes >> >> are not used. >> >> >> >> Is the issue that you cannot link an MPI program because the fork >> >> symbol >> >> is missing or that you cannot launch jobs with a Hydra? >> >> >> >> All mainstream MPI implementations use OS processes to implement MPI >> >> processes, but the standard doesn't require this. FG-MPI uses threads >> >> to >> >> implement MPI processes, but as it still uses Hydra (AFAIK), it may or >> >> may >> >> not work for you. >> >> >> >> Can you describe in detail what happens when you try to build and run >> >> MPICH-latest on your system? >> >> >> >> Jeff >> >> >> >> Sent from my iPhone >> >> >> >> On Jan 17, 2015, at 9:41 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: >> >> >> >> I would use a newer version if I could. However, I cannot issue a fork >> >> in >> >> my embedded environment. I can create threads though. >> >> >> >> So, is there any newer versions of mpich that does not create heavy >> >> processes? I can live without MPI_Spawn and the like. >> >> >> >> Regards, >> >> >> >> Eduardo >> >> >> >> On Jan 16, 2015 5:42 PM, "Wesley Bland" <wbland(a)anl.gov> wrote: >> >>> >> >>> Can you try using a more recent version of MPICH. The version you are >> >>> using is years old and we don't support it anymore. Our latest version >> >>> is >> >>> 3.1.3. You might see if the issue is still present there. >> >>> >> >>> Thanks, >> >>> Wesley >> >>> >> >>> On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> >> >>> wrote: >> >>>> >> >>>> Hi, >> >>>> >> >>>> I am trying to compile and use mpich-1.2.7p1 with threaded listener >> >>>> (i.e. configured with --enable-threaded-listener). However, I cannot >> >>>> even >> >>>> run a simple mpi example with the resulting mpich. >> >>>> >> >>>> I need to use threaded listener because the environment I am >> >>>> compiling >> >>>> for (kind of embedded environment) does not have fork (no heavy >> >>>> processes). >> >>>> >> >>>> The error I get with the mpich with threaded listener is: >> >>>> >> >>>> rm_2889: 1103279872: p4_error: listener select: -1 >> >>>> p4_error: latest msg from perror: Bad file descriptor >> >>>> p0_2710: (2.097656) net_recv failed for fd = 5 >> >>>> p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 >> >>>> >> >>>> Has anyone experienced a similar problem? >> >>>> >> >>>> Thanks in advance, >> >>>> Eduardo >> >>> >> >>> >> >>> >> >>> _______________________________________________ >> >>> discuss mailing list discuss(a)mpich.org >> >>> To manage subscription options or unsubscribe: >> >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> _______________________________________________ >> >> discuss mailing list discuss(a)mpich.org >> >> To manage subscription options or unsubscribe: >> >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> >> >> _______________________________________________ >> >> discuss mailing list discuss(a)mpich.org >> >> To manage subscription options or unsubscribe: >> >> https://lists.mpich.org/mailman/listinfo/discuss >> > >> > >> > >> > _______________________________________________ >> > discuss mailing list discuss(a)mpich.org >> > To manage subscription options or unsubscribe: >> > https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> -- >> Jeff Hammond >> jeff.science(a)gmail.com >> http://jeffhammond.github.io/ >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond jeff.science(a)gmail.com http://jeffhammond.github.io/ _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Threaded Listener
by Eduardo 17 Jan '15

17 Jan '15

The system is a micro-OS running in an embedded processor. There will be multiple of these processors, each one with a single mpi rank. I'm starting to think that I will have to do what Hydra does myself. Is there any documentation about what a mpi job expects from hydra? Eduardo On Sat, Jan 17, 2015 at 5:58 PM, Jeff Hammond <jeff.science(a)gmail.com> wrote: > How do you create processes on this system? If you are using an MPI > implementation that has a 1:1 mapping between MPI processes and OS > processes, you've got to be able to create multiple processes somehow. > > Do you have any platform details you can share? > > Jeff > > On Sat, Jan 17, 2015 at 11:46 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > > I tried to use a newer MPICH, but, as you said, Hydra forks as part of > > mpiexec. Is it possible to launch a job without mpiexec/mpirun ? That > should > > probably work in my environment (assuming that there is no listener as a > > heavy process as it is the case in the default mpich-1.2.7p1). > > > > The problem is not that the fork symbol is missing. The problem is that > it > > is been called. My environment actually has a dummy fork, but that only > > causes the program to abort if it is called. > > > > So in summary, the problem is that I cannot use mpiexec to launch a > program, > > because it calls fork. In mpich-1.2.7p1 , I can launch myself the > program as > > if I was launching a debug (as in section 3.5.6 of the CH_P4 manual). In > > addition, the mpich cannot issue a fork for a listener like task, only > > threads. > > > > Eduardo > > > > On Sat, Jan 17, 2015 at 4:23 PM, Jeff Hammond <jeff.science(a)gmail.com> > > wrote: > >> > >> MPICH shouldn't fork. Hydra probably uses fork to launch processes as > part > >> of mpiexec. > >> > >> Blue Gene doesn't support fork either and MPICH runs there, but the > >> process launcher is not Hydra. Same for Cray last time I checked. So I'm > >> sure that fork isn't required to use MPICH, at least if dynamic > processes > >> are not used. > >> > >> Is the issue that you cannot link an MPI program because the fork symbol > >> is missing or that you cannot launch jobs with a Hydra? > >> > >> All mainstream MPI implementations use OS processes to implement MPI > >> processes, but the standard doesn't require this. FG-MPI uses threads to > >> implement MPI processes, but as it still uses Hydra (AFAIK), it may or > may > >> not work for you. > >> > >> Can you describe in detail what happens when you try to build and run > >> MPICH-latest on your system? > >> > >> Jeff > >> > >> Sent from my iPhone > >> > >> On Jan 17, 2015, at 9:41 AM, Eduardo <erocha.ssa(a)gmail.com> wrote: > >> > >> I would use a newer version if I could. However, I cannot issue a fork > in > >> my embedded environment. I can create threads though. > >> > >> So, is there any newer versions of mpich that does not create heavy > >> processes? I can live without MPI_Spawn and the like. > >> > >> Regards, > >> > >> Eduardo > >> > >> On Jan 16, 2015 5:42 PM, "Wesley Bland" <wbland(a)anl.gov> wrote: > >>> > >>> Can you try using a more recent version of MPICH. The version you are > >>> using is years old and we don't support it anymore. Our latest version > is > >>> 3.1.3. You might see if the issue is still present there. > >>> > >>> Thanks, > >>> Wesley > >>> > >>> On Fri, Jan 16, 2015 at 10:54 AM, Eduardo <erocha.ssa(a)gmail.com> > wrote: > >>>> > >>>> Hi, > >>>> > >>>> I am trying to compile and use mpich-1.2.7p1 with threaded listener > >>>> (i.e. configured with --enable-threaded-listener). However, I cannot > even > >>>> run a simple mpi example with the resulting mpich. > >>>> > >>>> I need to use threaded listener because the environment I am compiling > >>>> for (kind of embedded environment) does not have fork (no heavy > processes). > >>>> > >>>> The error I get with the mpich with threaded listener is: > >>>> > >>>> rm_2889: 1103279872: p4_error: listener select: -1 > >>>> p4_error: latest msg from perror: Bad file descriptor > >>>> p0_2710: (2.097656) net_recv failed for fd = 5 > >>>> p0_2710: 3778266880: p4_error: net_recv read, errno = : 104 > >>>> > >>>> Has anyone experienced a similar problem? > >>>> > >>>> Thanks in advance, > >>>> Eduardo > >>> > >>> > >>> > >>> _______________________________________________ > >>> discuss mailing list discuss(a)mpich.org > >>> To manage subscription options or unsubscribe: > >>> https://lists.mpich.org/mailman/listinfo/discuss > >> > >> _______________________________________________ > >> discuss mailing list discuss(a)mpich.org > >> To manage subscription options or unsubscribe: > >> https://lists.mpich.org/mailman/listinfo/discuss > >> > >> > >> _______________________________________________ > >> discuss mailing list discuss(a)mpich.org > >> To manage subscription options or unsubscribe: > >> https://lists.mpich.org/mailman/listinfo/discuss > > > > > > > > _______________________________________________ > > discuss mailing list discuss(a)mpich.org > > To manage subscription options or unsubscribe: > > https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > jeff.science(a)gmail.com > http://jeffhammond.github.io/ > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0