September 2014 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Does MPICH implements polling mechanism on MPI_Recv?
by Anatoly G 22 Sep '14

22 Sep '14

Dear MPICH. I have a problem with poling MPICH mechanism. I'm working on cluster. There are 2-4 processes on each computer (I can't execute single process per computer because of application requirements). My system has 2 states: Ready - slaves listen to master (but no data flow) Run - masters start communication, then there is data flow. When system in ready state (all processes except master executed MPI_Recv requests on master) but Master process still net sending data I see CPU usage > 100% (more than 1 core used) per process. When 4 processes are in ready state (waiting for data) computer begins to slow down other processes, I think because of polling. I tried to build MPICH with --with-device=ch3:sock, then I get 0% CPU usage in ready state, but I have a problem with Fault tolerance feature. My questions are: 1) Is such behavior expected that build with --with-device=ch3:sock causes Fault tolerance not work? Does Fault tolerance based on polling mechanism? 2) Can I change polling rate to reduce CPU payload? I understand that penalty is transfer rate slow down. 3) Can I use any other MPI APIs to check if message from master is arrived w/o activating polling mechanism? Regards, Anatoly. On Thu, May 8, 2014 at 3:57 PM, Balaji, Pavan <balaji(a)anl.gov> wrote: > > This is expected. Currently, the only way to not have MPICH poll is to > configure with --with-device=ch3:sock. Please note that this can cause > performance loss (the polling is helpful for performance in the common > case). > > We are planning to allow this in the default build as well in the future. > > — Pavan > > On May 8, 2014, at 7:54 AM, Anatoly G <anatolyrishon(a)gmail.com> wrote: > > > Dear MPICH forum. > > I created an endless MPI program. > > In this program each process calls MPI_Recv from other process, w/o any > MPI_Send. > > When I execute this program I see each process takes ~ 100% CPU core. > > Is this behavior (I suppose polling) is normal? > > May I reduce MPI_Recv CPU penalty? > > > > Regards, > > Anatoly. > > <mpi_polling.cpp>_______________________________________________ > > 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] Error Running MPICH for Photochemical Modeling
by Lu, Huiwei 21 Sep '14

21 Sep '14

Abhishek, Could you reduce the example to one single file with less than 300 lines of code that reproduce the problem? Although we would like to help you, but looking at tarball of 147,000 line of Fortran code is too much effort for us. Also, another thing you could try is to use valgrind for detecting memory errors in the application. You can see the instructions of how to build MPICH with valgrind here: http://wiki.mpich.org/mpich/index.php/Support_for_Debugging_Memory_Allocati… (please don’t drop the discuss list) Thanks, — Huiwei On Sep 19, 2014, at 6:45 PM, Abhishek Bhat <abhat(a)trinityconsultants.com> wrote: > Huiwei And Sangmin, > > Please find attached - > 1. The compiled application > 2. Source Code Tarball > 3. The failed job > > Any help is really appreciated > > Thank you > Abhishek > ................................................................................................................ > Abhishek Bhat, PhD, EPI, > Senior Consultant > > > -----Original Message----- > From: Lu, Huiwei [mailto:[email protected]] > Sent: Friday, September 19, 2014 5:30 PM > To: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Error Running MPICH for Photochemical Modeling > > Hi, Abhishek, > > As mentioned in previous email, it looks like the problem lies in the application. Is it possible that you can provide us with a minimum example that fails? So that we can looked at the code and reproduce the problem on our machines. > > Thanks, > - > Huiwei > > On Sep 17, 2014, at 3:29 PM, Abhishek Bhat <abhat(a)trinityconsultants.com> wrote: > >> Sangmin, >> >> Fatal error in MPI_Recv: A process has failed, error stack: >> MPI_Recv(187).............: MPI_Recv(buf=0x7fff21bc04b0, count=644490, >> MPI_REAL, src=1, tag=14131, MPI_COMM_WORLD, status=0x7fff227c47a0) >> failed >> dequeue_and_set_error(865): Communication error with rank 1 >> >> =================================================================================== >> = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES >> = PID 4183 RUNNING AT dfw-camx >> = EXIT CODE: 1 >> = CLEANING UP REMAINING PROCESSES >> = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES >> ====================================================================== >> ============= [proxy:0:4@dfw-camx-n4] HYD_pmcd_pmip_control_cmd_cb >> (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed >> [proxy:0:4@dfw-camx-n4] HYDT_dmxu_poll_wait_for_event >> (tools/demux/demux_poll.c:76): callback returned error status >> [proxy:0:4@dfw-camx-n4] main (pm/pmiserv/pmip.c:206): demux engine >> error waiting for event [proxy:0:2@dfw-camx-n2] >> HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert >> (!closed) failed [proxy:0:2@dfw-camx-n2] HYDT_dmxu_poll_wait_for_event >> (tools/demux/demux_poll.c:76): callback returned error status >> [proxy:0:2@dfw-camx-n2] main (pm/pmiserv/pmip.c:206): demux engine >> error waiting for event [proxy:0:3@dfw-camx-n3] >> HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert >> (!closed) failed [proxy:0:3@dfw-camx-n3] HYDT_dmxu_poll_wait_for_event >> (tools/demux/demux_poll.c:76): callback returned error status >> [proxy:0:3@dfw-camx-n3] main (pm/pmiserv/pmip.c:206): demux engine >> error waiting for event [proxy:0:6@dfw-camx-n6] >> HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert >> (!closed) failed [proxy:0:6@dfw-camx-n6] HYDT_dmxu_poll_wait_for_event >> (tools/demux/demux_poll.c:76): callback returned error status >> [proxy:0:6@dfw-camx-n6] main (pm/pmiserv/pmip.c:206): demux engine >> error waiting for event [proxy:0:5@dfw-camx-n5] >> HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert >> (!closed) failed [proxy:0:5@dfw-camx-n5] HYDT_dmxu_poll_wait_for_event >> (tools/demux/demux_poll.c:76): callback returned error status >> [proxy:0:5@dfw-camx-n5] main (pm/pmiserv/pmip.c:206): demux engine >> error waiting for event [proxy:0:7@dfw-camx-n7] >> HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert >> (!closed) failed [proxy:0:7@dfw-camx-n7] HYDT_dmxu_poll_wait_for_event >> (tools/demux/demux_poll.c:76): callback returned error status >> [proxy:0:7@dfw-camx-n7] main (pm/pmiserv/pmip.c:206): demux engine >> error waiting for event [mpiexec@dfw-camx] >> HYDT_bscu_wait_for_completion (tools/bootstrap/utils/bscu_wait.c:76): >> one of the processes terminated badly; aborting [mpiexec@dfw-camx] >> HYDT_bsci_wait_for_completion (tools/bootstrap/src/bsci_wait.c:23): >> launcher returned error waiting for completion [mpiexec@dfw-camx] >> HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:218): launcher >> returned error waiting for completion [mpiexec@dfw-camx] main >> (ui/mpich/mpiexec.c:344): process manager error waiting for completion >> >> This is what I got from the exitallcodes. >> >> >> Anything helpful?? >> >> Thank you very much for all help >> Abhishek >> >> ................................................................................................................ >> Abhishek Bhat, PhD, EPI, >> Senior Consultant >> >> >> From: Seo, Sangmin [mailto:[email protected]] >> Sent: Wednesday, September 17, 2014 1:17 PM >> To: Abhishek Bhat >> Subject: Re: [mpich-discuss] Error Running MPICH for Photochemical >> Modeling >> >> >> On Sep 17, 2014, at 1:08 PM, Abhishek Bhat <abhat(a)trinityconsultants.com> wrote: >> >> >> Sangmin, >> >> What should be the correct syntax for print all exitcodes - If I use >> >> if( ! { mpiexec -machinefile nodes -np $NUMPROCS -print-all-exitcodes >> $EXEC -mpich-dbg=file -mpich-dbg-class=all -mpich-dbg-level=verbose } >> ) >> >> This is correct. And, the output will be shown on your terminal, not in file, like: >> [mpiexec@host] Exit codes: [host] 0,0 >> >> >> >> I am getting error saying "-print-all-exitcodes" is not a valid local >> parameters >> >> Which version of MPICH are you using? Can you let me know the result of the following? >> $ mpiexec -info >> >> - Sangmin >> >> >> ______________________________________________________________________ >> ___ >> >> The information transmitted is intended only for the person or entity >> to which it is addressed and may contain confidential and/or >> privileged material. Any review, retransmission, dissemination or >> other use of, or taking of any action in reliance upon, this >> information by persons or entities other than the intended recipient >> is prohibited. If you received this in error, please contact the >> sender and delete the material from any computer. >> ______________________________________________________________________ >> ___ _______________________________________________ >> 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 > > -- > _________________________________________________________________________ > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. > _________________________________________________________________________ > <Application.zip> _______________________________________________ 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] Cygwin+Mpich2: Internal Error: Failed to convert MPI_INTEGER value to hex!
by Wesley Bland 21 Sep '14

21 Sep '14

I'm sorry Mengda, but we don't support Windows anymore. You can find out more on our FAQ, but in short, you'll need to try another implementation such as Microsoft MPI or Intel MPI. Thanks, Wesley > On Sep 20, 2014, at 9:50 PM, Mengda Wu <phdggg(a)gmail.com> wrote: > > Hello all, > > I am trying to compile mpich-3.1.2 under Cygwin 64bit. I am using the mingw64- x86_64-gcc-g++ and mingw64-x86_64-gcc-gfortran compilers, i.e. the mingw compilers shipped in the latest Cygwin. I encountered an internal error "Failed to convert MPI_INTEGER value to hex!" when configuring. > > ======================================================== > checking whether real*4 is supported... yes > checking whether real*8 is supported... yes > checking whether real*16 is supported... yes > : integer expression expected: 4 > : integer expression expected: 4 > : integer expression expected: 4 > : integer expression expected: 8 > : integer expression expected: 8 > : integer expression expected: 8 > checking for C type matching Fortran real... unavailable > checking for C type matching Fortran double... unavailable > expr: syntax error > expr: syntax error > expr: non-integer argument > ./configure: line 38715: test: : integer expression expected > ./configure: line 38720: test: -gt: unary operator expected > ./configure: line 38734: test: -lt: unary operator expected > ./configure: line 38715: test: : integer expression expected > ./configure: line 38720: test: -gt: unary operator expected > ./configure: line 38734: test: -lt: unary operator expected > ./configure: line 38715: test: : integer expression expected > ./configure: line 38720: test: -gt: unary operator expected > ./configure: line 38734: test: -lt: unary operator expected > expr: non-integer argument > ./configure: line 38783: test: -ge: unary operator expected > expr: syntax error > expr: syntax error > expr: syntax error > expr: syntax error > configure: error: Internal Error: Failed to convert MPI_INTEGER value to hex! O > riginal value was 0x4c001b > ============================================================= > > In config.log, it shows > ============================================================= > configure:38248: checking for size of Fortran type double precision > configure:38289: gcc -c -O2 -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/mpl/include -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/mpl/include -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/openpa/src -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/openpa/src -D_REENTRANT -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/mpi/romio/include conftest.c >&5 > configure:38289: $? = 0 > configure:38293: mv conftest.o pac_conftest.o > configure:38296: $? = 0 > configure:38323: gfortran -o conftest.exe -O2 conftest.f pac_conftest.o >&5 > configure:38323: $? = 0 > configure:38323: ./conftest.exe > configure:38323: $? = 0 > configure:38361: result: 8 > > configure:38384: checking whether integer*1 is supported > configure:38395: gfortran -c -O2 conftest.f >&5 > configure:38395: $? = 0 > configure:38402: result: yes > configure:38404: checking whether integer*2 is supported > configure:38415: gfortran -c -O2 conftest.f >&5 > configure:38415: $? = 0 > configure:38422: result: yes > configure:38424: checking whether integer*4 is supported > configure:38435: gfortran -c -O2 conftest.f >&5 > configure:38435: $? = 0 > configure:38442: result: yes > configure:38444: checking whether integer*8 is supported > configure:38455: gfortran -c -O2 conftest.f >&5 > configure:38455: $? = 0 > configure:38462: result: yes > configure:38464: checking whether integer*16 is supported > configure:38475: gfortran -c -O2 conftest.f >&5 > configure:38475: $? = 0 > configure:38482: result: yes > configure:38484: checking whether real*4 is supported > configure:38495: gfortran -c -O2 conftest.f >&5 > configure:38495: $? = 0 > configure:38502: result: yes > configure:38504: checking whether real*8 is supported > configure:38515: gfortran -c -O2 conftest.f >&5 > configure:38515: $? = 0 > configure:38522: result: yes > configure:38524: checking whether real*16 is supported > configure:38535: gfortran -c -O2 conftest.f >&5 > configure:38535: $? = 0 > configure:38542: result: yes > configure:38641: checking for C type matching Fortran real > configure:38659: result: unavailable > configure:38664: checking for C type matching Fortran double > configure:38681: result: unavailable > configure:38842: error: Internal Error: Failed to convert MPI_INTEGER value to hex! Original value was 0x4c001b > ============================================================= > > Can you help? > > Thanks, > Mengda > > _______________________________________________ > 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

Cygwin+Mpich2: Internal Error: Failed to convert MPI_INTEGER value to hex!
by Mengda Wu 20 Sep '14

20 Sep '14

Hello all, I am trying to compile mpich-3.1.2 under Cygwin 64bit. I am using the mingw64- x86_64-gcc-g++ and mingw64-x86_64-gcc-gfortran compilers, i.e. the mingw compilers shipped in the latest Cygwin. I encountered an internal error "Failed to convert MPI_INTEGER value to hex!" when configuring. ======================================================== checking whether real*4 is supported... yes checking whether real*8 is supported... yes checking whether real*16 is supported... yes : integer expression expected: 4 : integer expression expected: 4 : integer expression expected: 4 : integer expression expected: 8 : integer expression expected: 8 : integer expression expected: 8 checking for C type matching Fortran real... unavailable checking for C type matching Fortran double... unavailable expr: syntax error expr: syntax error expr: non-integer argument ./configure: line 38715: test: : integer expression expected ./configure: line 38720: test: -gt: unary operator expected ./configure: line 38734: test: -lt: unary operator expected ./configure: line 38715: test: : integer expression expected ./configure: line 38720: test: -gt: unary operator expected ./configure: line 38734: test: -lt: unary operator expected ./configure: line 38715: test: : integer expression expected ./configure: line 38720: test: -gt: unary operator expected ./configure: line 38734: test: -lt: unary operator expected expr: non-integer argument ./configure: line 38783: test: -ge: unary operator expected expr: syntax error expr: syntax error expr: syntax error expr: syntax error configure: error: Internal Error: Failed to convert MPI_INTEGER value to hex! O riginal value was 0x4c001b ============================================================= In config.log, it shows ============================================================= configure:38248: checking for size of Fortran type double precision configure:38289: gcc -c -O2 -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/mpl/include -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/mpl/include -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/openpa/src -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/openpa/src -D_REENTRANT -I/cygdrive/c/Library/mpich2/mpich-3.1.2/src/mpi/romio/include conftest.c >&5 configure:38289: $? = 0 configure:38293: mv conftest.o pac_conftest.o configure:38296: $? = 0 configure:38323: gfortran -o conftest.exe -O2 conftest.f pac_conftest.o >&5 configure:38323: $? = 0 configure:38323: ./conftest.exe configure:38323: $? = 0 configure:38361: result: 8 configure:38384: checking whether integer*1 is supported configure:38395: gfortran -c -O2 conftest.f >&5 configure:38395: $? = 0 configure:38402: result: yes configure:38404: checking whether integer*2 is supported configure:38415: gfortran -c -O2 conftest.f >&5 configure:38415: $? = 0 configure:38422: result: yes configure:38424: checking whether integer*4 is supported configure:38435: gfortran -c -O2 conftest.f >&5 configure:38435: $? = 0 configure:38442: result: yes configure:38444: checking whether integer*8 is supported configure:38455: gfortran -c -O2 conftest.f >&5 configure:38455: $? = 0 configure:38462: result: yes configure:38464: checking whether integer*16 is supported configure:38475: gfortran -c -O2 conftest.f >&5 configure:38475: $? = 0 configure:38482: result: yes configure:38484: checking whether real*4 is supported configure:38495: gfortran -c -O2 conftest.f >&5 configure:38495: $? = 0 configure:38502: result: yes configure:38504: checking whether real*8 is supported configure:38515: gfortran -c -O2 conftest.f >&5 configure:38515: $? = 0 configure:38522: result: yes configure:38524: checking whether real*16 is supported configure:38535: gfortran -c -O2 conftest.f >&5 configure:38535: $? = 0 configure:38542: result: yes configure:38641: checking for C type matching Fortran real configure:38659: result: unavailable configure:38664: checking for C type matching Fortran double configure:38681: result: unavailable configure:38842: error: Internal Error: Failed to convert MPI_INTEGER value to hex! Original value was 0x4c001b ============================================================= Can you help? Thanks, Mengda _______________________________________________ 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] how can I download the tex source of mpi document from mpi forum web
by Wesley Bland 20 Sep '14

20 Sep '14

In an effort to avoid having unofficial versions of that document floating around, the source isn't available outside of those participating in the forum itself. Thanks, Wesley > On Sep 20, 2014, at 4:12 AM, myself <chcdlf(a)126.com> wrote: > > I want to get the tex source of mpi specification. I find the mpi-1 source scripts from argonne ftp server. However, I have no way to get the mpi-3 latex source scripts. Is there any way to download them? > > > _______________________________________________ > 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

how can I download the tex source of mpi document from mpi forum web
by myself 20 Sep '14

20 Sep '14

I want to get the tex source of mpi specification. I find the mpi-1 source scripts from argonne ftp server. However, I have no way to get the mpi-3 latex source scripts. Is there any way to download them? _______________________________________________ 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 Running MPICH for Photochemical Modeling
by Lu, Huiwei 19 Sep '14

19 Sep '14

Hi, Abhishek, As mentioned in previous email, it looks like the problem lies in the application. Is it possible that you can provide us with a minimum example that fails? So that we can looked at the code and reproduce the problem on our machines. Thanks, — Huiwei On Sep 17, 2014, at 3:29 PM, Abhishek Bhat <abhat(a)trinityconsultants.com> wrote: > Sangmin, > > Fatal error in MPI_Recv: A process has failed, error stack: > MPI_Recv(187).............: MPI_Recv(buf=0x7fff21bc04b0, count=644490, MPI_REAL, src=1, tag=14131, MPI_COMM_WORLD, status=0x7fff227c47a0) failed > dequeue_and_set_error(865): Communication error with rank 1 > > =================================================================================== > = BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES > = PID 4183 RUNNING AT dfw-camx > = EXIT CODE: 1 > = CLEANING UP REMAINING PROCESSES > = YOU CAN IGNORE THE BELOW CLEANUP MESSAGES > =================================================================================== > [proxy:0:4@dfw-camx-n4] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed > [proxy:0:4@dfw-camx-n4] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [proxy:0:4@dfw-camx-n4] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event > [proxy:0:2@dfw-camx-n2] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed > [proxy:0:2@dfw-camx-n2] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [proxy:0:2@dfw-camx-n2] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event > [proxy:0:3@dfw-camx-n3] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed > [proxy:0:3@dfw-camx-n3] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [proxy:0:3@dfw-camx-n3] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event > [proxy:0:6@dfw-camx-n6] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed > [proxy:0:6@dfw-camx-n6] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [proxy:0:6@dfw-camx-n6] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event > [proxy:0:5@dfw-camx-n5] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed > [proxy:0:5@dfw-camx-n5] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [proxy:0:5@dfw-camx-n5] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event > [proxy:0:7@dfw-camx-n7] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:885): assert (!closed) failed > [proxy:0:7@dfw-camx-n7] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:76): callback returned error status > [proxy:0:7@dfw-camx-n7] main (pm/pmiserv/pmip.c:206): demux engine error waiting for event > [mpiexec@dfw-camx] HYDT_bscu_wait_for_completion (tools/bootstrap/utils/bscu_wait.c:76): one of the processes terminated badly; aborting > [mpiexec@dfw-camx] HYDT_bsci_wait_for_completion (tools/bootstrap/src/bsci_wait.c:23): launcher returned error waiting for completion > [mpiexec@dfw-camx] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:218): launcher returned error waiting for completion > [mpiexec@dfw-camx] main (ui/mpich/mpiexec.c:344): process manager error waiting for completion > > This is what I got from the exitallcodes. > > > Anything helpful?? > > Thank you very much for all help > Abhishek > > …………………………………………………………………………………………………. > Abhishek Bhat, PhD, EPI, > Senior Consultant > > > From: Seo, Sangmin [mailto:[email protected]] > Sent: Wednesday, September 17, 2014 1:17 PM > To: Abhishek Bhat > Subject: Re: [mpich-discuss] Error Running MPICH for Photochemical Modeling > > > On Sep 17, 2014, at 1:08 PM, Abhishek Bhat <abhat(a)trinityconsultants.com> wrote: > > > Sangmin, > > What should be the correct syntax for print all exitcodes – > If I use > > if( ! { mpiexec -machinefile nodes -np $NUMPROCS -print-all-exitcodes $EXEC -mpich-dbg=file -mpich-dbg-class=all -mpich-dbg-level=verbose } ) > > This is correct. And, the output will be shown on your terminal, not in file, like: > [mpiexec@host] Exit codes: [host] 0,0 > > > > I am getting error saying “-print-all-exitcodes” is not a valid local parameters > > Which version of MPICH are you using? Can you let me know the result of the following? > $ mpiexec -info > > — Sangmin > > > _________________________________________________________________________ > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon, this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. > _________________________________________________________________________ > _______________________________________________ > 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] Question
by Reuti 18 Sep '14

18 Sep '14

Hi, Am 18.09.2014 um 15:20 schrieb Lu, Huiwei: > Hi Mohammad, > > Due to lack of developer resources, MPICH no longer supports the Windows platform. Please refer to our FAQ for more information: > http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can… > > We recommend you use Microsoft MPI, which can be found here: http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx > > If the problem is with MS-MPI, you should try the MS-MPI forum: > http://social.microsoft.com/Forums/en-US/home?forum=windowshpcmpi > or askmpi(a)microsoft.com FWIW: There is a community edition of Platform MPI for Windows http://www.ibm.com/developerworks/downloads/im/mpi/ -- Reuti > Thanks, > > — > Huiwei > > On Sep 18, 2014, at 2:35 AM, Mohammad Nami Nazari <mohammad.naminazari(a)gmail.com> wrote: > >> Hello, >> >> I have tried running MPI with Open MPI but it wouldn't work so I >> switched to MPICH2. My code complies fine in Windows using Visual >> Studio 2010 but when I go to invoke mpiexec -n 2 TEST.exe it runs for >> some time then crashes with the error: >> >> Error while connecting to host, A connection attempt failed because >> the connected party did not properly respond after a period of time, >> or established connection failed because connected host has failed to >> respond. (10060) >> Connect on sock (host=BAHR83M5Z8.resource.ds.bah.com, port=8676) failed, exhause >> d all end points >> Unable to connect to 'BAHR83M5Z8.resource.ds.bah.com:8676', >> sock error: Error = -1 >> Thanks regard >> _______________________________________________ >> 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] Question
by Lu, Huiwei 18 Sep '14

18 Sep '14

Hi Mohammad, Due to lack of developer resources, MPICH no longer supports the Windows platform. Please refer to our FAQ for more information: http://wiki.mpich.org/mpich/index.php/Frequently_Asked_Questions#Q:_Why_can… We recommend you use Microsoft MPI, which can be found here: http://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx If the problem is with MS-MPI, you should try the MS-MPI forum: http://social.microsoft.com/Forums/en-US/home?forum=windowshpcmpi or askmpi(a)microsoft.com Thanks, — Huiwei On Sep 18, 2014, at 2:35 AM, Mohammad Nami Nazari <mohammad.naminazari(a)gmail.com> wrote: > Hello, > > I have tried running MPI with Open MPI but it wouldn't work so I > switched to MPICH2. My code complies fine in Windows using Visual > Studio 2010 but when I go to invoke mpiexec -n 2 TEST.exe it runs for > some time then crashes with the error: > > Error while connecting to host, A connection attempt failed because > the connected party did not properly respond after a period of time, > or established connection failed because connected host has failed to > respond. (10060) > Connect on sock (host=BAHR83M5Z8.resource.ds.bah.com, port=8676) failed, exhause > d all end points > Unable to connect to 'BAHR83M5Z8.resource.ds.bah.com:8676', > sock error: Error = -1 > Thanks regard > _______________________________________________ > 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

Question
by Mohammad Nami Nazari 18 Sep '14

18 Sep '14

Hello, I have tried running MPI with Open MPI but it wouldn't work so I switched to MPICH2. My code complies fine in Windows using Visual Studio 2010 but when I go to invoke mpiexec -n 2 TEST.exe it runs for some time then crashes with the error: Error while connecting to host, A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. (10060) Connect on sock (host=BAHR83M5Z8.resource.ds.bah.com, port=8676) failed, exhause d all end points Unable to connect to 'BAHR83M5Z8.resource.ds.bah.com:8676', sock error: Error = -1 Thanks regard _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0