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

I do not succeed to correctly setup password-less ssh
by Moshe Goldstein 09 Oct '15

09 Oct '15

_______________________________________________ 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 spawning processes in mpich-3.2rc1
by Min Si 08 Oct '15

08 Oct '15

Hi Siegmar, It seems you already enabled the most detailed error outputs. We could not think out any clue for now. If you can give us access to your machine, we are glad to help you debug on it. Min On 10/8/15 12:02 AM, Siegmar Gross wrote: > Hi Min, > > thank you very much for your answer. > >> We cannot reproduce this error on our test machines (Solaris i386, >> Ubuntu x86_64) by using your programs. And unfortunately we do not have >> Solaris Sparc machine thus could not verify it. > > The programs work fine on my Solaris x86_64 and Linux machines > as well. I only have a problem on Solaris Sparc. > > >> Sometime, it can happen that you need to add "./" in front of the >> program path, could you try it ? >> >> For example, in spawn_master.c MPI: A Message-Passing Interface Standard >>> #define SLAVE_PROG "./spawn_slave" > > No, it wil not work, because the programs are stored in a > different directory ($HOME/{SunOS, Linux}/{sparc, x86_64}/bin) > which is part of PATH (as well as "."). > > Can I do anything to track the source of the error? > > > Kind regards > > Siegmar > >> >> Min >> >> On 10/7/15 5:03 AM, Siegmar Gross wrote: >>> Hi, >>> >>> today I've built mpich-3.2rc1 on my machines (Solaris 10 Sparc, >>> Solaris 10 x86_64, and openSUSE Linux 12.1 x86_64) with gcc-5.1.0 >>> and Sun C 5.13. I still get the following errors on my Sparc machine >>> which I'd already reported September 8th. "mpiexec" is aliased to >>> 'mpiexec -genvnone'. It still doesn't matter if I use my cc- or >>> gcc-version of MPICH. >>> >>> >>> tyr spawn 119 mpichversion >>> MPICH Version: 3.2rc1 >>> MPICH Release date: Wed Oct 7 00:00:33 CDT 2015 >>> MPICH Device: ch3:nemesis >>> MPICH configure: --prefix=/usr/local/mpich-3.2_64_cc >>> --libdir=/usr/local/mpich-3.2_64_cc/lib64 >>> --includedir=/usr/local/mpich-3.2_64_cc/include64 CC=cc CXX=CC F77=f77 >>> FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 >>> -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 --enable-fortran=yes >>> --enable-cxx --enable-romio --enable-debuginfo --enable-smpcoll >>> --enable-threads=multiple --with-thread-package=posix --enable-shared >>> MPICH CC: cc -m64 -O2 >>> MPICH CXX: CC -m64 -O2 >>> MPICH F77: f77 -m64 >>> MPICH FC: f95 -m64 -O2 >>> tyr spawn 120 >>> >>> >>> >>> tyr spawn 111 mpiexec -np 1 spawn_master >>> >>> Parent process 0 running on tyr.informatik.hs-fulda.de >>> I create 4 slave processes >>> >>> Fatal error in MPI_Comm_spawn: Unknown error class, error stack: >>> MPI_Comm_spawn(144)...........: MPI_Comm_spawn(cmd="spawn_slave", >>> argv=0, maxprocs=4, MPI_INFO_NULL, root=0, MPI_COMM_WORLD, >>> intercomm=ffffffff7fffde50, errors=0) failed >>> MPIDI_Comm_spawn_multiple(274): >>> MPID_Comm_accept(153).........: >>> MPIDI_Comm_accept(1057).......: >>> MPIR_Bcast_intra(1287)........: >>> MPIR_Bcast_binomial(310)......: Failure during collective >>> >>> >>> >>> >>> tyr spawn 112 mpiexec -np 1 spawn_multiple_master >>> >>> Parent process 0 running on tyr.informatik.hs-fulda.de >>> I create 3 slave processes. >>> >>> Fatal error in MPI_Comm_spawn_multiple: Unknown error class, error >>> stack: >>> MPI_Comm_spawn_multiple(162)..: MPI_Comm_spawn_multiple(count=2, >>> cmds=ffffffff7fffde08, argvs=ffffffff7fffddf8, >>> maxprocs=ffffffff7fffddf0, infos=ffffffff7fffdde8, root=0, >>> MPI_COMM_WORLD, intercomm=ffffffff7fffdde4, errors=0) failed >>> MPIDI_Comm_spawn_multiple(274): >>> MPID_Comm_accept(153).........: >>> MPIDI_Comm_accept(1057).......: >>> MPIR_Bcast_intra(1287)........: >>> MPIR_Bcast_binomial(310)......: Failure during collective >>> >>> >>> >>> >>> tyr spawn 113 mpiexec -np 1 spawn_intra_comm >>> Parent process 0: I create 2 slave processes >>> Fatal error in MPI_Comm_spawn: Unknown error class, error stack: >>> MPI_Comm_spawn(144)...........: MPI_Comm_spawn(cmd="spawn_intra_comm", >>> argv=0, maxprocs=2, MPI_INFO_NULL, root=0, MPI_COMM_WORLD, >>> intercomm=ffffffff7fffded4, errors=0) failed >>> MPIDI_Comm_spawn_multiple(274): >>> MPID_Comm_accept(153).........: >>> MPIDI_Comm_accept(1057).......: >>> MPIR_Bcast_intra(1287)........: >>> MPIR_Bcast_binomial(310)......: Failure during collective >>> tyr spawn 114 >>> >>> >>> I would be grateful if somebody can fix the problem. Thank you very >>> much for any help in advance. I've attached my programs. Please let >>> me know if you need anything else. >>> >>> >>> Kind regards >>> >>> Siegmar >>> >>> >>> _______________________________________________ >>> discuss mailing listdiscuss(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

1 0

Re: [mpich-discuss] Can the MPICH job pause and resumed
by Rob Latham 08 Oct '15

08 Oct '15

On 10/08/2015 08:18 AM, Jeff Hammond wrote: > Nodes and cores are *hardware* concepts. If you need to add hardware > resources to your job, that is a resource manager issue. If you want to > create new MPI processes _that will run on those new nodes/cores_, you > can use MPI_Comm_spawn for that. > > As for pausing a job, I'm not sure why you want to do that. Are you > trying to suspect the job until the new hardware resources become available? Probably not what Wahi has in mind, but back on the old Crays (old vector-era crays, I mean), when checkpoint/restart was an os-level service, the job scheduler used that feature: new job comes in with higher priority, checkpoint the old job. when new job finishes, restart old job. ==rob > > On Wed, Oct 7, 2015 at 10:08 PM, wahi <wahi(a)sci.am <mailto:[email protected]>> > wrote: > > Hi Jeff, > > Thank you for your reply, I think the MPI_COMM_Spawn is for > generating new processes but I need to add more node or cores after > pausing the job, am I right ? > > > On 10/08/2015 08:11 AM, Jeff Hammond wrote: >> See MPI_Comm_spawn(_multiple). >> >> Jeff >> >> On Wednesday, October 7, 2015, Zhao, Xin >> <<mailto:[email protected]>xinzhao3(a)illinois.edu >> <mailto:[email protected]>> wrote: >> >> Hi Wahi, >> >> Do you mean you want to change number of hosts during one MPI >> execution? If so, we think that is not possible. >> >> Xin >> ________________________________________ >> From: wahi [wahi(a)sci.am] >> Sent: Wednesday, October 07, 2015 2:43 AM >> To: discuss(a)mpich.org >> Subject: [mpich-discuss] Can the MPICH job pause and resumed >> >> Hi, >> >> I would like to know if there is possibility to pause the >> MPICH job and >> restart it with more node numbers ? >> >> >> >> Thanks in advance for any help or suggestion. >> >> >> >> >> >> Regards, >> Wahi >> _______________________________________________ >> 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 <mailto:[email protected]> >> http://jeffhammond.github.io/ >> >> >> _______________________________________________ >> discuss mailing listdiscuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > http://jeffhammond.github.io/ > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Rob Latham Mathematics and Computer Science Division Argonne National Lab, IL USA _______________________________________________ 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] Can the MPICH job pause and resumed
by wahi 08 Oct '15

08 Oct '15

Hi Jeff, Yes I want to pause the job to have more resources available, so maybe I need to think about SLURM as a scheduler. On 10/08/2015 05:18 PM, Jeff Hammond wrote: > Nodes and cores are *hardware* concepts. If you need to add hardware > resources to your job, that is a resource manager issue. If you want > to create new MPI processes _that will run on those new nodes/cores_, > you can use MPI_Comm_spawn for that. > > As for pausing a job, I'm not sure why you want to do that. Are you > trying to suspect the job until the new hardware resources become > available? > > On Wed, Oct 7, 2015 at 10:08 PM, wahi <wahi(a)sci.am > <mailto:[email protected]>> wrote: > > Hi Jeff, > > Thank you for your reply, I think the MPI_COMM_Spawn is for > generating new processes but I need to add more node or cores > after pausing the job, am I right ? > > > On 10/08/2015 08:11 AM, Jeff Hammond wrote: >> See MPI_Comm_spawn(_multiple). >> >> Jeff >> >> On Wednesday, October 7, 2015, Zhao, Xin <xinzhao3(a)illinois.edu >> <mailto:[email protected]>> wrote: >> >> Hi Wahi, >> >> Do you mean you want to change number of hosts during one MPI >> execution? If so, we think that is not possible. >> >> Xin >> ________________________________________ >> From: wahi [wahi(a)sci.am] >> Sent: Wednesday, October 07, 2015 2:43 AM >> To: discuss(a)mpich.org >> Subject: [mpich-discuss] Can the MPICH job pause and resumed >> >> Hi, >> >> I would like to know if there is possibility to pause the >> MPICH job and >> restart it with more node numbers ? >> >> >> >> Thanks in advance for any help or suggestion. >> >> >> >> >> >> Regards, >> Wahi >> _______________________________________________ >> 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 <mailto:[email protected]> >> http://jeffhammond.github.io/ >> >> >> _______________________________________________ >> discuss mailing listdiscuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > 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

Re: [mpich-discuss] Issue with MPI_Comm_spawn_multiple
by Antonio J. Peña 08 Oct '15

08 Oct '15

Thanks a lot Sangmin! On 10/08/2015 03:43 PM, Seo, Sangmin wrote: > Hi Toni, > > I confirmed the problem and am looking into it. I will get back to you after I resolve it. > > Regards, > Sangmin > > >> On Oct 6, 2015, at 7:23 AM, Antonio J. Peña <antonio.pena(a)bsc.es> wrote: >> >> >> Right, but I do need to use the hosts key to get control of where the processes are spawned. Any clue? >> >> >> On 10/02/2015 07:32 PM, Thakur, Rajeev wrote: >>> Looks like it is related to the hosts key. Works without that. >>> >>> Rajeev >>> >>>> On Oct 2, 2015, at 10:34 AM, Antonio J. Peña <antonio.pena(a)bsc.es> wrote: >>>> >>>> Hi folks! >>>> >>>> I've been facing an issue with MPI_Comm_spawn_multiple when all the >>>> following conditions are met: >>>> >>>> 1. 'count' is > 1 >>>> 2. Any value of 'array_of_maxprocs' is > 1 >>>> 3. Setting the "hosts" info key >>>> >>>> What I'm finding is that the spawned processes hang at MPI_Init. Find >>>> attached a test case. You can reproduce my issue with -np 1. >>>> >>>> Is there anything I'm doing wrong? I'm using MPICH master at 1e6c4d8. I >>>> haven't found a pending ticket, xfail test, or test case covering this >>>> situation. >>>> >>>> All the best, >>>> Toni >>>> >>>> [P.S.: It still feels weird to be on the other side of discuss(a)mpich.org] >>>> >>>> -- >>>> Antonio J. Peña >>>> Senior Researcher >>>> Barcelona Supercomputing Center >>>> >>>> >>>> >>>> WARNING / LEGAL TEXT: This message is intended only for the use of the >>>> individual or entity to which it is addressed and may contain >>>> information which is privileged, confidential, proprietary, or exempt >>>> from disclosure under applicable law. If you are not the intended >>>> recipient or the person responsible for delivering the message to the >>>> intended recipient, you are strictly prohibited from disclosing, >>>> distributing, copying, or in any way using this message. If you have >>>> received this communication in error, please notify the sender and >>>> destroy and delete any copies you may have received. >>>> >>>> http://www.bsc.es/disclaimer<spawn_multiple.c>_______________________________________________ >>>> 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 >> -- >> Antonio J. Peña >> Senior Researcher >> Barcelona Supercomputing Center >> >> >> WARNING / LEGAL TEXT: This message is intended only for the use of the >> individual or entity to which it is addressed and may contain >> information which is privileged, confidential, proprietary, or exempt >> from disclosure under applicable law. If you are not the intended >> recipient or the person responsible for delivering the message to the >> intended recipient, you are strictly prohibited from disclosing, >> distributing, copying, or in any way using this message. If you have >> received this communication in error, please notify the sender and >> destroy and delete any copies you may have received. >> >> http://www.bsc.es/disclaimer >> _______________________________________________ >> 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 -- Antonio J. Peña Senior Researcher Barcelona Supercomputing Center WARNING / LEGAL TEXT: This message is intended only for the use of the individual or entity to which it is addressed and may contain information which is privileged, confidential, proprietary, or exempt from disclosure under applicable law. If you are not the intended recipient or the person responsible for delivering the message to the intended recipient, you are strictly prohibited from disclosing, distributing, copying, or in any way using this message. If you have received this communication in error, please notify the sender and destroy and delete any copies you may have received. http://www.bsc.es/disclaimer _______________________________________________ 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] Issue with MPI_Comm_spawn_multiple
by Seo, Sangmin 08 Oct '15

08 Oct '15

Hi Toni, I confirmed the problem and am looking into it. I will get back to you after I resolve it. Regards, Sangmin > On Oct 6, 2015, at 7:23 AM, Antonio J. Peña <antonio.pena(a)bsc.es> wrote: > > > Right, but I do need to use the hosts key to get control of where the processes are spawned. Any clue? > > > On 10/02/2015 07:32 PM, Thakur, Rajeev wrote: >> Looks like it is related to the hosts key. Works without that. >> >> Rajeev >> >>> On Oct 2, 2015, at 10:34 AM, Antonio J. Peña <antonio.pena(a)bsc.es> wrote: >>> >>> Hi folks! >>> >>> I've been facing an issue with MPI_Comm_spawn_multiple when all the >>> following conditions are met: >>> >>> 1. 'count' is > 1 >>> 2. Any value of 'array_of_maxprocs' is > 1 >>> 3. Setting the "hosts" info key >>> >>> What I'm finding is that the spawned processes hang at MPI_Init. Find >>> attached a test case. You can reproduce my issue with -np 1. >>> >>> Is there anything I'm doing wrong? I'm using MPICH master at 1e6c4d8. I >>> haven't found a pending ticket, xfail test, or test case covering this >>> situation. >>> >>> All the best, >>> Toni >>> >>> [P.S.: It still feels weird to be on the other side of discuss(a)mpich.org] >>> >>> -- >>> Antonio J. Peña >>> Senior Researcher >>> Barcelona Supercomputing Center >>> >>> >>> >>> WARNING / LEGAL TEXT: This message is intended only for the use of the >>> individual or entity to which it is addressed and may contain >>> information which is privileged, confidential, proprietary, or exempt >>> from disclosure under applicable law. If you are not the intended >>> recipient or the person responsible for delivering the message to the >>> intended recipient, you are strictly prohibited from disclosing, >>> distributing, copying, or in any way using this message. If you have >>> received this communication in error, please notify the sender and >>> destroy and delete any copies you may have received. >>> >>> http://www.bsc.es/disclaimer<spawn_multiple.c>_______________________________________________ >>> 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 > > -- > Antonio J. Peña > Senior Researcher > Barcelona Supercomputing Center > > > WARNING / LEGAL TEXT: This message is intended only for the use of the > individual or entity to which it is addressed and may contain > information which is privileged, confidential, proprietary, or exempt > from disclosure under applicable law. If you are not the intended > recipient or the person responsible for delivering the message to the > intended recipient, you are strictly prohibited from disclosing, > distributing, copying, or in any way using this message. If you have > received this communication in error, please notify the sender and > destroy and delete any copies you may have received. > > http://www.bsc.es/disclaimer > _______________________________________________ > 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] Can the MPICH job pause and resumed
by Jeff Hammond 08 Oct '15

08 Oct '15

Nodes and cores are *hardware* concepts. If you need to add hardware resources to your job, that is a resource manager issue. If you want to create new MPI processes _that will run on those new nodes/cores_, you can use MPI_Comm_spawn for that. As for pausing a job, I'm not sure why you want to do that. Are you trying to suspect the job until the new hardware resources become available? On Wed, Oct 7, 2015 at 10:08 PM, wahi <wahi(a)sci.am> wrote: > Hi Jeff, > > Thank you for your reply, I think the MPI_COMM_Spawn is for generating new > processes but I need to add more node or cores after pausing the job, am I > right ? > > > On 10/08/2015 08:11 AM, Jeff Hammond wrote: > > See MPI_Comm_spawn(_multiple). > > Jeff > > On Wednesday, October 7, 2015, Zhao, Xin < <xinzhao3(a)illinois.edu> > xinzhao3(a)illinois.edu> wrote: > >> Hi Wahi, >> >> Do you mean you want to change number of hosts during one MPI execution? >> If so, we think that is not possible. >> >> Xin >> ________________________________________ >> From: wahi [wahi(a)sci.am] >> Sent: Wednesday, October 07, 2015 2:43 AM >> To: discuss(a)mpich.org >> Subject: [mpich-discuss] Can the MPICH job pause and resumed >> >> Hi, >> >> I would like to know if there is possibility to pause the MPICH job and >> restart it with more node numbers ? >> >> >> >> Thanks in advance for any help or suggestion. >> >> >> >> >> >> Regards, >> Wahi >> _______________________________________________ >> 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] Can the MPICH job pause and resumed
by wahi 08 Oct '15

08 Oct '15

Hi Jeff, Thank you for your reply, I think the MPI_COMM_Spawn is for generating new processes but I need to add more node or cores after pausing the job, am I right ? On 10/08/2015 08:11 AM, Jeff Hammond wrote: > See MPI_Comm_spawn(_multiple). > > Jeff > > On Wednesday, October 7, 2015, Zhao, Xin <xinzhao3(a)illinois.edu > <mailto:[email protected]>> wrote: > > Hi Wahi, > > Do you mean you want to change number of hosts during one MPI > execution? If so, we think that is not possible. > > Xin > ________________________________________ > From: wahi [wahi(a)sci.am <javascript:;>] > Sent: Wednesday, October 07, 2015 2:43 AM > To: discuss(a)mpich.org <javascript:;> > Subject: [mpich-discuss] Can the MPICH job pause and resumed > > Hi, > > I would like to know if there is possibility to pause the MPICH > job and > restart it with more node numbers ? > > > > Thanks in advance for any help or suggestion. > > > > > > Regards, > Wahi > _______________________________________________ > discuss mailing list discuss(a)mpich.org <javascript:;> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org <javascript:;> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > -- > Jeff Hammond > jeff.science(a)gmail.com <mailto:[email protected]> > 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

Re: [mpich-discuss] error spawning processes in mpich-3.2rc1
by Siegmar Gross 08 Oct '15

08 Oct '15

Hi Min, thank you very much for your answer. > We cannot reproduce this error on our test machines (Solaris i386, > Ubuntu x86_64) by using your programs. And unfortunately we do not have > Solaris Sparc machine thus could not verify it. The programs work fine on my Solaris x86_64 and Linux machines as well. I only have a problem on Solaris Sparc. > Sometime, it can happen that you need to add "./" in front of the > program path, could you try it ? > > For example, in spawn_master.c MPI: A Message-Passing Interface Standard >> #define SLAVE_PROG "./spawn_slave" No, it wil not work, because the programs are stored in a different directory ($HOME/{SunOS, Linux}/{sparc, x86_64}/bin) which is part of PATH (as well as "."). Can I do anything to track the source of the error? Kind regards Siegmar > > Min > > On 10/7/15 5:03 AM, Siegmar Gross wrote: >> Hi, >> >> today I've built mpich-3.2rc1 on my machines (Solaris 10 Sparc, >> Solaris 10 x86_64, and openSUSE Linux 12.1 x86_64) with gcc-5.1.0 >> and Sun C 5.13. I still get the following errors on my Sparc machine >> which I'd already reported September 8th. "mpiexec" is aliased to >> 'mpiexec -genvnone'. It still doesn't matter if I use my cc- or >> gcc-version of MPICH. >> >> >> tyr spawn 119 mpichversion >> MPICH Version: 3.2rc1 >> MPICH Release date: Wed Oct 7 00:00:33 CDT 2015 >> MPICH Device: ch3:nemesis >> MPICH configure: --prefix=/usr/local/mpich-3.2_64_cc >> --libdir=/usr/local/mpich-3.2_64_cc/lib64 >> --includedir=/usr/local/mpich-3.2_64_cc/include64 CC=cc CXX=CC F77=f77 >> FC=f95 CFLAGS=-m64 CXXFLAGS=-m64 FFLAGS=-m64 FCFLAGS=-m64 LDFLAGS=-m64 >> -L/usr/lib/sparcv9 -R/usr/lib/sparcv9 --enable-fortran=yes >> --enable-cxx --enable-romio --enable-debuginfo --enable-smpcoll >> --enable-threads=multiple --with-thread-package=posix --enable-shared >> MPICH CC: cc -m64 -O2 >> MPICH CXX: CC -m64 -O2 >> MPICH F77: f77 -m64 >> MPICH FC: f95 -m64 -O2 >> tyr spawn 120 >> >> >> >> tyr spawn 111 mpiexec -np 1 spawn_master >> >> Parent process 0 running on tyr.informatik.hs-fulda.de >> I create 4 slave processes >> >> Fatal error in MPI_Comm_spawn: Unknown error class, error stack: >> MPI_Comm_spawn(144)...........: MPI_Comm_spawn(cmd="spawn_slave", >> argv=0, maxprocs=4, MPI_INFO_NULL, root=0, MPI_COMM_WORLD, >> intercomm=ffffffff7fffde50, errors=0) failed >> MPIDI_Comm_spawn_multiple(274): >> MPID_Comm_accept(153).........: >> MPIDI_Comm_accept(1057).......: >> MPIR_Bcast_intra(1287)........: >> MPIR_Bcast_binomial(310)......: Failure during collective >> >> >> >> >> tyr spawn 112 mpiexec -np 1 spawn_multiple_master >> >> Parent process 0 running on tyr.informatik.hs-fulda.de >> I create 3 slave processes. >> >> Fatal error in MPI_Comm_spawn_multiple: Unknown error class, error stack: >> MPI_Comm_spawn_multiple(162)..: MPI_Comm_spawn_multiple(count=2, >> cmds=ffffffff7fffde08, argvs=ffffffff7fffddf8, >> maxprocs=ffffffff7fffddf0, infos=ffffffff7fffdde8, root=0, >> MPI_COMM_WORLD, intercomm=ffffffff7fffdde4, errors=0) failed >> MPIDI_Comm_spawn_multiple(274): >> MPID_Comm_accept(153).........: >> MPIDI_Comm_accept(1057).......: >> MPIR_Bcast_intra(1287)........: >> MPIR_Bcast_binomial(310)......: Failure during collective >> >> >> >> >> tyr spawn 113 mpiexec -np 1 spawn_intra_comm >> Parent process 0: I create 2 slave processes >> Fatal error in MPI_Comm_spawn: Unknown error class, error stack: >> MPI_Comm_spawn(144)...........: MPI_Comm_spawn(cmd="spawn_intra_comm", >> argv=0, maxprocs=2, MPI_INFO_NULL, root=0, MPI_COMM_WORLD, >> intercomm=ffffffff7fffded4, errors=0) failed >> MPIDI_Comm_spawn_multiple(274): >> MPID_Comm_accept(153).........: >> MPIDI_Comm_accept(1057).......: >> MPIR_Bcast_intra(1287)........: >> MPIR_Bcast_binomial(310)......: Failure during collective >> tyr spawn 114 >> >> >> I would be grateful if somebody can fix the problem. Thank you very >> much for any help in advance. I've attached my programs. Please let >> me know if you need anything else. >> >> >> Kind regards >> >> Siegmar >> >> >> _______________________________________________ >> discuss mailing listdiscuss(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

1 0

Re: [mpich-discuss] Can the MPICH job pause and resumed
by Jeff Hammond 07 Oct '15

07 Oct '15

See MPI_Comm_spawn(_multiple). Jeff On Wednesday, October 7, 2015, Zhao, Xin <xinzhao3(a)illinois.edu> wrote: > Hi Wahi, > > Do you mean you want to change number of hosts during one MPI execution? > If so, we think that is not possible. > > Xin > ________________________________________ > From: wahi [wahi(a)sci.am <javascript:;>] > Sent: Wednesday, October 07, 2015 2:43 AM > To: discuss(a)mpich.org <javascript:;> > Subject: [mpich-discuss] Can the MPICH job pause and resumed > > Hi, > > I would like to know if there is possibility to pause the MPICH job and > restart it with more node numbers ? > > > > Thanks in advance for any help or suggestion. > > > > > > Regards, > Wahi > _______________________________________________ > discuss mailing list discuss(a)mpich.org <javascript:;> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ > discuss mailing list discuss(a)mpich.org <javascript:;> > 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