- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Pavan Balaji 13 Jun '13

13 Jun '13

What's "-phrase"? That's not a recognized option. I'm not sure where the /dev/mem check is coming from. Try running ~/main without mpiexec first. -- Pavan On 06/13/2013 06:56 AM, Lee, Eibhlin wrote: > Hello all, > > I am trying to use two raspberry-pi to sample and then process some > data. The first process samples while the second processes and vice > versa. To do this I use gpio and also mpich-3.0.4 with the process > manager smpd. I have successfully run cpi on both machines (from the > master machine). I have also managed to run a similar program but > without the MPI, this involved compiling with gcc and when running > putting sudo in front of the binary file. > > When I combine these two processes I get various error messages. > For input: > mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > Can't open /dev/mem > Did you forget to use 'sudo .. ?' > > For input: > sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > sudo: mpiexec: Command not found > > I therefore put mpiexec into /usr/bin > > now for input: > sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > Can't open /dev/mem > Did you forget to use 'sudo .. ?' > > Does anyone know how I can work around this? > Thanks, > Eibhlin > > > > _______________________________________________ > 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

1 0

Re: [mpich-discuss] Running an mpi program that needs to access /dev/mem
by Jeff Hammond 13 Jun '13

13 Jun '13

Just su to root instead of using sudo. Jeff On Thu, Jun 13, 2013 at 6:56 AM, Lee, Eibhlin <eibhlin.lee10(a)imperial.ac.uk> wrote: > Hello all, > > I am trying to use two raspberry-pi to sample and then process some data. > The first process samples while the second processes and vice versa. To do > this I use gpio and also mpich-3.0.4 with the process manager smpd. I have > successfully run cpi on both machines (from the master machine). I have also > managed to run a similar program but without the MPI, this involved > compiling with gcc and when running putting sudo in front of the binary > file. > > When I combine these two processes I get various error messages. > For input: > mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > Can't open /dev/mem > Did you forget to use 'sudo .. ?' > > For input: > sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > sudo: mpiexec: Command not found > > I therefore put mpiexec into /usr/bin > > now for input: > sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main > the error is: > Can't open /dev/mem > Did you forget to use 'sudo .. ?' > > Does anyone know how I can work around this? > Thanks, > Eibhlin > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Running an mpi program that needs to access /dev/mem
by Lee, Eibhlin 13 Jun '13

13 Jun '13

Hello all, I am trying to use two raspberry-pi to sample and then process some data. The first process samples while the second processes and vice versa. To do this I use gpio and also mpich-3.0.4 with the process manager smpd. I have successfully run cpi on both machines (from the master machine). I have also managed to run a similar program but without the MPI, this involved compiling with gcc and when running putting sudo in front of the binary file. When I combine these two processes I get various error messages. For input: mpiexec -phrase cat -machinefile machinefile -n 2 ~/main the error is: Can't open /dev/mem Did you forget to use 'sudo .. ?' For input: sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main the error is: sudo: mpiexec: Command not found I therefore put mpiexec into /usr/bin now for input: sudo mpiexec -phrase cat -machinefile machinefile -n 2 ~/main the error is: Can't open /dev/mem Did you forget to use 'sudo .. ?' Does anyone know how I can work around this? Thanks, Eibhlin

1 0

Re: [mpich-discuss] Issue on compiling MPICH 3.0.4 with intel compiler on scientific linux
by Zheng Li 12 Jun '13

12 Jun '13

Thank you for comment. Regards, Lee 2013/6/12 Jeff Hammond <jhammond(a)alcf.anl.gov> > A large fraction of compile warnings are for innocuous aspects of the > code. It's appropriate for developers to look at warnings carefully > to ensure that they aren't indicative of problems, but users are > better off just running the test suite to determine if the build is > successful or not. In your case, 797/797 is a very good indication of > a proper build of MPICH. > > Best, > > Jeff > > On Wed, Jun 12, 2013 at 9:20 AM, Zheng Li <seraphzl(a)gmail.com> wrote: > > I did the 'make testing' according to the README in the > mpich-3.0.4.tar.gz > > file. All 797 tests passed, and the log files were attached. Yes, it > seems > > that the build was ok in spite of many warnings in the 'make' step. I > will > > run the cpi example further to test it. Thank you for your help. > > > > 2013/6/12 Rajeev Thakur <thakur(a)mcs.anl.gov> > >> > >> The build seems to have completed. Can you run the example programs? Try > >> running the cpi example in the examples directory. > >> > >> > >> On Jun 12, 2013, at 1:15 AM, Zheng Li wrote: > >> > >> > Dear All, > >> > > >> > I tried to compile the MPICH 3.0.4 with Intel C/C++/Fortran compiler > >> > 13.1.1 on scientific linux 6.4 x64 platform. The building steps were > as > >> > follows: > >> > > >> > export CC=icc CXX=icpc CPP='icc -E' CXXCPP='icpc -E' F77=ifort > FC=ifort > >> > CFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' CXXFLAGS='-O3 > -xHost -ip > >> > -no-prec-div -static-intel' FFLAGS='-O3 -xHost -ip -no-prec-div > >> > -static-intel' > >> > configure --prefix=/home/sl/mpich-3.0.4 --disable-fast 2>&1 | tee > c.log > >> > make 2>&1 | tee m.log > >> > make install 2>&1 | tee mi.log > >> > > >> > The terminal reported many warning of pragma during 'make', such like > >> > the following: > >> > > >> > ../src/binding/f77/fdebug.c(22): warning #20: identifier > >> > "MPIR_IS_BOTTOM" is undefined > >> > #pragma weak MPIR_IS_BOTTOM = mpir_is_bottom_ > >> > ^ > >> > > >> > The log files were attached. How can I resolve this issue? Thanks in > >> > advance. > >> > > >> > > >> > > <c.log><config.log><m.log><mi.log>_______________________________________________ > >> > 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 > Argonne Leadership Computing Facility > University of Chicago Computation Institute > jhammond(a)alcf.anl.gov / (630) 252-5381 > http://www.linkedin.com/in/jeffhammond > https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond > ALCF docs: http://www.alcf.anl.gov/user-guides > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > <seraphzl(a)gmail.com>

1 0

Re: [mpich-discuss] Issue on compiling MPICH 3.0.4 with intel compiler on scientific linux
by Jeff Hammond 12 Jun '13

12 Jun '13

A large fraction of compile warnings are for innocuous aspects of the code. It's appropriate for developers to look at warnings carefully to ensure that they aren't indicative of problems, but users are better off just running the test suite to determine if the build is successful or not. In your case, 797/797 is a very good indication of a proper build of MPICH. Best, Jeff On Wed, Jun 12, 2013 at 9:20 AM, Zheng Li <seraphzl(a)gmail.com> wrote: > I did the 'make testing' according to the README in the mpich-3.0.4.tar.gz > file. All 797 tests passed, and the log files were attached. Yes, it seems > that the build was ok in spite of many warnings in the 'make' step. I will > run the cpi example further to test it. Thank you for your help. > > 2013/6/12 Rajeev Thakur <thakur(a)mcs.anl.gov> >> >> The build seems to have completed. Can you run the example programs? Try >> running the cpi example in the examples directory. >> >> >> On Jun 12, 2013, at 1:15 AM, Zheng Li wrote: >> >> > Dear All, >> > >> > I tried to compile the MPICH 3.0.4 with Intel C/C++/Fortran compiler >> > 13.1.1 on scientific linux 6.4 x64 platform. The building steps were as >> > follows: >> > >> > export CC=icc CXX=icpc CPP='icc -E' CXXCPP='icpc -E' F77=ifort FC=ifort >> > CFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' CXXFLAGS='-O3 -xHost -ip >> > -no-prec-div -static-intel' FFLAGS='-O3 -xHost -ip -no-prec-div >> > -static-intel' >> > configure --prefix=/home/sl/mpich-3.0.4 --disable-fast 2>&1 | tee c.log >> > make 2>&1 | tee m.log >> > make install 2>&1 | tee mi.log >> > >> > The terminal reported many warning of pragma during 'make', such like >> > the following: >> > >> > ../src/binding/f77/fdebug.c(22): warning #20: identifier >> > "MPIR_IS_BOTTOM" is undefined >> > #pragma weak MPIR_IS_BOTTOM = mpir_is_bottom_ >> > ^ >> > >> > The log files were attached. How can I resolve this issue? Thanks in >> > advance. >> > >> > >> > <c.log><config.log><m.log><mi.log>_______________________________________________ >> > 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 > > > > > -- > Dr. Zheng Li > Research Assistant > State Key Laboratory of Environmental Aquatic Chemistry > Research Center for Eco-Environmental Sciences > Chinese Academy of Sciences > P. O. Box 2871, Beijing, 100085 China > seraphzl(a)gmail.com > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss -- Jeff Hammond Argonne Leadership Computing Facility University of Chicago Computation Institute jhammond(a)alcf.anl.gov / (630) 252-5381 http://www.linkedin.com/in/jeffhammond https://wiki.alcf.anl.gov/parts/index.php/User:Jhammond ALCF docs: http://www.alcf.anl.gov/user-guides

1 0

Re: [mpich-discuss] Issue on compiling MPICH 3.0.4 with intel compiler on scientific linux
by Zheng Li 12 Jun '13

12 Jun '13

I did the 'make testing' according to the README in the mpich-3.0.4.tar.gz file. All 797 tests passed, and the log files were attached. Yes, it seems that the build was ok in spite of many warnings in the 'make' step. I will run the cpi example further to test it. Thank you for your help. 2013/6/12 Rajeev Thakur <thakur(a)mcs.anl.gov> > The build seems to have completed. Can you run the example programs? Try > running the cpi example in the examples directory. > > > On Jun 12, 2013, at 1:15 AM, Zheng Li wrote: > > > Dear All, > > > > I tried to compile the MPICH 3.0.4 with Intel C/C++/Fortran compiler > 13.1.1 on scientific linux 6.4 x64 platform. The building steps were as > follows: > > > > export CC=icc CXX=icpc CPP='icc -E' CXXCPP='icpc -E' F77=ifort FC=ifort > CFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' CXXFLAGS='-O3 -xHost -ip > -no-prec-div -static-intel' FFLAGS='-O3 -xHost -ip -no-prec-div > -static-intel' > > configure --prefix=/home/sl/mpich-3.0.4 --disable-fast 2>&1 | tee c.log > > make 2>&1 | tee m.log > > make install 2>&1 | tee mi.log > > > > The terminal reported many warning of pragma during 'make', such like > the following: > > > > ../src/binding/f77/fdebug.c(22): warning #20: identifier > "MPIR_IS_BOTTOM" is undefined > > #pragma weak MPIR_IS_BOTTOM = mpir_is_bottom_ > > ^ > > > > The log files were attached. How can I resolve this issue? Thanks in > advance. > > > > > <c.log><config.log><m.log><mi.log>_______________________________________________ > > 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 > -- Dr. Zheng Li Research Assistant State Key Laboratory of Environmental Aquatic Chemistry Research Center for Eco-Environmental Sciences Chinese Academy of Sciences P. O. Box 2871, Beijing, 100085 China seraphzl(a)gmail.com

1 0

Re: [mpich-discuss] Issue on compiling MPICH 3.0.4 with intel compiler on scientific linux
by Rajeev Thakur 12 Jun '13

12 Jun '13

The build seems to have completed. Can you run the example programs? Try running the cpi example in the examples directory. On Jun 12, 2013, at 1:15 AM, Zheng Li wrote: > Dear All, > > I tried to compile the MPICH 3.0.4 with Intel C/C++/Fortran compiler 13.1.1 on scientific linux 6.4 x64 platform. The building steps were as follows: > > export CC=icc CXX=icpc CPP='icc -E' CXXCPP='icpc -E' F77=ifort FC=ifort CFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' CXXFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' FFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' > configure --prefix=/home/sl/mpich-3.0.4 --disable-fast 2>&1 | tee c.log > make 2>&1 | tee m.log > make install 2>&1 | tee mi.log > > The terminal reported many warning of pragma during 'make', such like the following: > > ../src/binding/f77/fdebug.c(22): warning #20: identifier "MPIR_IS_BOTTOM" is undefined > #pragma weak MPIR_IS_BOTTOM = mpir_is_bottom_ > ^ > > The log files were attached. How can I resolve this issue? Thanks in advance. > > <c.log><config.log><m.log><mi.log>_______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0

Issue on compiling MPICH 3.0.4 with intel compiler on scientific linux
by Zheng Li 12 Jun '13

12 Jun '13

Dear All, I tried to compile the MPICH 3.0.4 with Intel C/C++/Fortran compiler 13.1.1 on scientific linux 6.4 x64 platform. The building steps were as follows: export CC=icc CXX=icpc CPP='icc -E' CXXCPP='icpc -E' F77=ifort FC=ifort CFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' CXXFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' FFLAGS='-O3 -xHost -ip -no-prec-div -static-intel' configure --prefix=/home/sl/mpich-3.0.4 --disable-fast 2>&1 | tee c.log make 2>&1 | tee m.log make install 2>&1 | tee mi.log The terminal reported many warning of pragma during 'make', such like the following: ../src/binding/f77/fdebug.c(22): warning #20: identifier "MPIR_IS_BOTTOM" is undefined #pragma weak MPIR_IS_BOTTOM = mpir_is_bottom_ ^ The log files were attached. How can I resolve this issue? Thanks in advance. <seraphzl(a)gmail.com>

1 0

Re: [mpich-discuss] install + config on windows
by Antonio J. Peña 11 Jun '13

11 Jun '13

Hi Benoit, As our support for Windows platforms has been discontinued, we cannot guarantee MPICH is going to be able to be compiled in newer versions of the Windows compilers and/or the operating system itself. Unless Jayesh has any comments on this regard, I'm not aware of any experience of MPICH + Windows 7. I apologize for the inconvenience. Thanks, Antonio On Monday, June 10, 2013 08:04:03 AM spatiogis wrote: > Hello, > > actually, it seems that Mpich must be compiled to work. The point is that > the "Readme" file gives an explanation to compile the programs with Visual > studio 2003. Anyway this last software is very difficult to make work on > windows 7. > > Is there finally a way to compile Mpich on windows 7 with Visual Studio ? > > best regards, > > Benoit Véler > > > Hi, > > > > From the log output it looks like credentials (password) for > > > > Utilisateur was not correct. > > > > Is Utilisateur a valid Windows user on your machine? Have you > > > > registered the username/password correctly (Try re-registering the > > username+password by typing "mpiexec -register" at the command prompt)? > > > > Regards, > > Jayesh > > > > ----- Original Message ----- > > From: "spatiogis" <geo(a)spatiogis.fr> > > To: discuss(a)mpich.org > > Sent: Friday, May 3, 2013 11:58:00 AM > > Subject: Re: [mpich-discuss] install + config on windows > > > > Hello, > > > > for this command : > > > > # C:\Progra~1\MPICH2\bin\mpiexec -verbose -n 2 > > > > C:\Progra~1\MPICH2\examples\cpi.exe > > > > result : > > > > ....../SMPDU_Sock_post_readv > > > > ...../SMPDU_Sock_post_read > > ..../smpd_handle_op_connect > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_READ event.error = 0, result = 0, context=left > > ....\smpd_handle_op_read > > .....\smpd_state_reading_challenge_string > > ......read challenge string: '1.4.1p1 18467' > > ......\smpd_verify_version > > ....../smpd_verify_version > > ......Verification of smpd version succeeded > > ......\smpd_hash > > ....../smpd_hash > > ......\SMPDU_Sock_post_write > > .......\SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_writev > > ....../SMPDU_Sock_post_write > > ...../smpd_state_reading_challenge_string > > ..../smpd_handle_op_read > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > ....\smpd_handle_op_write > > .....\smpd_state_writing_challenge_response > > ......wrote challenge response: 'dafd1d07c1e6e9cb5fae968403d0d933' > > ......\SMPDU_Sock_post_read > > .......\SMPDU_Sock_post_readv > > ......./SMPDU_Sock_post_readv > > ....../SMPDU_Sock_post_read > > ...../smpd_state_writing_challenge_response > > ..../smpd_handle_op_write > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_READ event.error = 0, result = 0, context=left > > ....\smpd_handle_op_read > > .....\smpd_state_reading_connect_result > > ......read connect result: 'SUCCESS' > > ......\SMPDU_Sock_post_write > > .......\SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_writev > > ....../SMPDU_Sock_post_write > > ...../smpd_state_reading_connect_result > > ..../smpd_handle_op_read > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > ....\smpd_handle_op_write > > .....\smpd_state_writing_process_session_request > > ......wrote process session request: 'process' > > ......\SMPDU_Sock_post_read > > .......\SMPDU_Sock_post_readv > > ......./SMPDU_Sock_post_readv > > ....../SMPDU_Sock_post_read > > ...../smpd_state_writing_process_session_request > > ..../smpd_handle_op_write > > ....sock_waiting for the next event. > > ....\SMPDU_Sock_wait > > ..../SMPDU_Sock_wait > > ....SOCK_OP_READ event.error = 0, result = 0, context=left > > ....\smpd_handle_op_read > > .....\smpd_state_reading_cred_request > > ......read cred request: 'credentials' > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > .......\smpd_option_on > > ........\smpd_get_smpd_data > > .........\smpd_get_smpd_data_from_environment > > ........./smpd_get_smpd_data_from_environment > > .........\smpd_get_smpd_data_default > > ........./smpd_get_smpd_data_default > > .........Unable to get the data for the key 'nocache' > > ......../smpd_get_smpd_data > > ......./smpd_option_on > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ......\SMPDU_Sock_post_write > > .......\SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_writev > > ....../SMPDU_Sock_post_write > > ...../smpd_handle_op_read > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > .....\smpd_handle_op_write > > ......\smpd_state_writing_cred_ack_yes > > .......wrote cred request yes ack. > > .......\SMPDU_Sock_post_write > > ........\SMPDU_Sock_post_writev > > ......../SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_write > > ....../smpd_state_writing_cred_ack_yes > > ...../smpd_handle_op_write > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > .....\smpd_handle_op_write > > ......\smpd_state_writing_account > > .......wrote account: 'Utilisateur' > > .......\smpd_encrypt_data > > ......./smpd_encrypt_data > > .......\SMPDU_Sock_post_write > > ........\SMPDU_Sock_post_writev > > ......../SMPDU_Sock_post_writev > > ......./SMPDU_Sock_post_write > > ....../smpd_state_writing_account > > ...../smpd_handle_op_write > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_WRITE event.error = 0, result = 0, context=left > > .....\smpd_handle_op_write > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > .......\smpd_hide_string_arg > > ........\first_token > > ......../first_token > > ........\compare_token > > ......../compare_token > > ........\next_token > > .........\first_token > > ........./first_token > > .........\first_token > > ........./first_token > > ......../next_token > > ......./smpd_hide_string_arg > > ......./smpd_hide_string_arg > > .......\SMPDU_Sock_post_read > > ........\SMPDU_Sock_post_readv > > ......../SMPDU_Sock_post_readv > > ......./SMPDU_Sock_post_read > > ......\smpd_hide_string_arg > > .......\first_token > > ......./first_token > > .......\compare_token > > ......./compare_token > > .......\next_token > > ........\first_token > > ......../first_token > > ........\first_token > > ......../first_token > > ......./next_token > > ....../smpd_hide_string_arg > > ....../smpd_hide_string_arg > > ...../smpd_handle_op_write > > .....sock_waiting for the next event. > > .....\SMPDU_Sock_wait > > ...../SMPDU_Sock_wait > > .....SOCK_OP_READ event.error = 0, result = 0, context=left > > .....\smpd_handle_op_read > > ......\smpd_state_reading_process_result > > .......read process session result: 'FAIL' > > .......\smpd_hide_string_arg > > ........\first_token > > ......../first_token > > ........\compare_token > > ......../compare_token > > ........\next_token > > .........\first_token > > ........./first_token > > .........\first_token > > ........./first_token > > ......../next_token > > ......./smpd_hide_string_arg > > ......./smpd_hide_string_arg > > .......\smpd_hide_string_arg > > ........\first_token > > ......../first_token > > ........\compare_token > > ......../compare_token > > ........\next_token > > .........\first_token > > ........./first_token > > .........\first_token > > ........./first_token > > ......../next_token > > ......./smpd_hide_string_arg > > ......./smpd_hide_string_arg > > Credentials for Utilisateur rejected connecting to Benoit > > .......process session rejected > > .......\SMPDU_Sock_post_close > > ........\SMPDU_Sock_post_read > > .........\SMPDU_Sock_post_readv > > ........./SMPDU_Sock_post_readv > > ......../SMPDU_Sock_post_read > > ......./SMPDU_Sock_post_close > > .......\smpd_post_abort_command > > ........\smpd_create_command > > .........\smpd_init_command > > ........./smpd_init_command > > ......../smpd_create_command > > ........\smpd_add_command_arg > > ......../smpd_add_command_arg > > ........\smpd_command_destination > > .........0 -> 0 : returning NULL context > > ......../smpd_command_destination > > Aborting: Unable to connect to Benoit > > ......./smpd_post_abort_command > > .......\smpd_exit > > ........\smpd_kill_all_processes > > ......../smpd_kill_all_processes > > ........\smpd_finalize_drive_maps > > ......../smpd_finalize_drive_maps > > ........\smpd_dbs_finalize > > ......../smpd_dbs_finalize > > ........\SMPDU_Sock_finalize > > ......../SMPDU_Sock_finalize > > > > C:\Users\Utilisateur> > > > >> Hi, > >> > >> Looks like you missed the "-" before the status ("smpd -status" not > >> > >> "smpd status") argument. > >> > >> It also looks like you have multiple MPI libraries installed in your > >> > >> system. Try running this command (full path to mpiexec and smpd), > >> > >> # C:\Progra~1\MPICH2\bin\smpd -status > >> > >> # C:\Progra~1\MPICH2\bin\mpiexec -verbose -n 2 > >> C:\Progra~1\MPICH2\examples\cpi.exe > >> > >> > >> Regards, > >> Jayesh > >> > >> ----- Original Message ----- > >> From: "spatiogis" <geo(a)spatiogis.fr> > >> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> > >> Sent: Friday, May 3, 2013 11:05:34 AM > >> Subject: Re: [mpich-discuss] install + config on windows > >> > >> Hello, > >> > >> C:\Users\Utilisateur>smpd status > >> Unexpected parameters: status > >> > >> C:\Users\Utilisateur>mpiexec -verbose -n 2 > >> C:\Progra~1\MPICH2\examples\cpi.exe > >> Unknown option: -verbose > >> > >> ------------------------------------------------------------------------- > >> ---- C:\Program Files\MPICH2\examples>mpiexec -verbose -n 2 cpi.exe > >> Unknown option: -verbose > >> > >> C:\Program Files\MPICH2\examples>smpd status > >> Unexpected parameters: status > >> ------------------------------------------------------------------------- > >> ---- > >> > >> regards, Ben > >> > >>> Hi, > >>> > >>> Ok. Please send us the output of the following commands, > >>> > >>> # smpd -status > >>> # mpiexec -verbose -n 2 C:\Progra~1\MPICH2\examples\cpi.exe > >>> > >>> Please copy-paste the command and the complete output in your email. > >>> > >>> Regards, > >>> Jayesh > >>> > >>> > >>> ----- Original Message ----- > >>> From: "spatiogis" <geo(a)spatiogis.fr> > >>> To: discuss(a)mpich.org > >>> Sent: Friday, May 3, 2013 1:46:53 AM > >>> Subject: Re: [mpich-discuss] install + config on windows > >>> > >>> Hello > >>> > >>>> (PS: I am assuming from your reply in the previous email that you can > >>>> run a command like "mpiexec -n 2 C:\Progra~1\MPICH2\examples\cpi.exe" > >>>> correctly) > >>>> > >>> In fact this command doesn't run. > >>> > >>> The message is this one > >>> > >>> [01:11728]....ERROR:unable to read the cmd header on the pmi context, > >>> > >>> Error = -1 > >>> > >>> Ben > >>> > >>>> ----- Original Message ----- > >>>> From: "spatiogis" <geo(a)spatiogis.fr> > >>>> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> > >>>> Sent: Thursday, May 2, 2013 10:48:56 AM > >>>> Subject: Re: [mpich-discuss] install + config on windows > >>>> > >>>> Hello, > >>>> > >>>>> Hi, > >>>>> > >>>>> Are you able to run any other MPI programs? Try running the example > >>>>> > >>>>> program, cpi.exe (C:\Program Files\MPICH2\examples\cpi.exe), to make > >>>>> sure that your MPICH2 installation works. > >>>>> > >>>> yes it does work > >>>> > >>>>> Installing MPICH2 on Windows 7 typically requires you to uninstall > >>>>> > >>>>> any > >>>>> previous versions of MPICH2, launch an administrative command promt > >>>>> and > >>>>> run "msiexec /i mpich2-installer.msi" to install MPICH2. > >>>>> > >>>> yes it 's been installed like this... > >>>> > >>>> In wmpiconfig, the message is the following in the 'Get settings' > >>>> > >>>> line. > >>>> > >>>> Credentials for Utilisateur rejected connecting to host > >>>> Aborting: Unable to connect to host > >>>> > >>>> The software I try to use is Taudem, which is intergrated inside > >>>> > >>>> Qgis. > >>>> Launching a taudem process inside Qgis gives the same message. > >>>> > >>>>> Regards, > >>>>> Jayesh > >>>>> > >>>> Sincerely, Ben > >>>> > >>>>> ----- Original Message ----- > >>>>> From: "spatiogis" <geo(a)spatiogis.fr> > >>>>> To: discuss(a)mpich.org > >>>>> Sent: Thursday, May 2, 2013 10:08:23 AM > >>>>> Subject: Re: [mpich-discuss] install + config on windows > >>>>> > >>>>> Hello, > >>>>> > >>>>> in my case Mpich is normally used to run .exe programs. I guess that > >>>>> > >>>>> they > >>>>> are already compiled... > >>>>> > >>>>> The .exe files are integrated into a software, and accessed from > >>>>> > >>>>> menus > >>>>> inside it. When I run one of the programs, the answer is actually > >>>>> "unable > >>>>> to query host". > >>>>> > >>>>> At the end, the process is not realised. It seems that this 'host' > >>>>> > >>>>> question is a problem to the software... > >>>>> > >>>>> Sincerely, > >>>>> > >>>>> Ben. > >>>>> > >>>>>> Hi, > >>>>>> > >>>>>> You can download MPICH2 binaries for Windows at > >>>>>> > >>>>>> http://www.mpich.org/downloads/ . > >>>>>> > >>>>>> You need to compile your MPI programs with MPICH2 to make it work. > >>>>>> > >>>>>> I > >>>>>> would recommend recompiling your code after you install MPICH2 (If > >>>>>> you > >>>>>> have MPI program binaries pre-built with MPICH2 - instead of > >>>>>> compiling > >>>>>> them on your own - make sure that you install the same version of > >>>>>> MPICH2 > >>>>>> that was used to build the binaries). > >>>>>> > >>>>>> The wmpiregister program has a bug and you can ignore this error > >>>>>> > >>>>>> message ("...unable to query host"). Can you run your MPI program > >>>>>> using > >>>>>> mpiexec from a command prompt? > >>>>>> > >>>>>> Regards, > >>>>>> Jayesh > >>>>>> > >>>>>> ----- Original Message ----- > >>>>>> From: "spatiogis" <geo(a)spatiogis.fr> > >>>>>> To: discuss(a)mpich.org > >>>>>> Sent: Tuesday, April 30, 2013 9:26:35 AM > >>>>>> Subject: [mpich-discuss] install + config on windows > >>>>>> > >>>>>> Hello, > >>>>>> > >>>>>> I'm not very good at computing, but I would like to install Mpich2 > >>>>>> > >>>>>> on > >>>>>> windows 7 - 64 bits. There is only one pc, with one user plus the > >>>>>> admin, > >>>>>> and a simple core processor. > >>>>>> > >>>>>> I would like to know if it's mandatory to have compiling softwares > >>>>>> > >>>>>> with > >>>>>> it to make it work, whereas it is asked in this case only to make > >>>>>> run > >>>>>> another software, and not for compiling (that would maybe save some > >>>>>> disk > >>>>>> space and simplify the installation) ? > >>>>>> > >>>>>> My second issue is that I must be missing something about the > >>>>>> > >>>>>> server > >>>>>> configuration. I have installed Mpich from the .msi file, then > >>>>>> configured > >>>>>> the wmpiregister program with the Domain/user informations. > >>>>>> > >>>>>> There is this message displayed when trying to connect in the > >>>>>> > >>>>>> 'configurable settings' window : 'MPICH2 not installed or unable to > >>>>>> query > >>>>>> the host'. > >>>>>> > >>>>>> What is the host actually ? > >>>>>> > >>>>>> I know I am starting from very far, I am sorry for these very > >>>>>> > >>>>>> simple > >>>>>> questions. Thanks if you can reply me, that would certainly save me > >>>>>> some > >>>>>> long hours of reading and testing ;) > >>>>>> > >>>>>> sincerely, > >>>>>> > >>>>>> Ben > >>>>>> > >>>>>> _______________________________________________ > >>>>>> 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] ckpoint-num error
by Wesley Bland 11 Jun '13

11 Jun '13

Did you check if there's actually anything in the checkpoint files? If they're empty, that probably means that you're checkpointing too frequently. On Jun 10, 2013, at 5:17 PM, john donald <johnd9886(a)gmail.com> wrote: > i raised it to 20 sec but same results > sorry i am new to checkpoint restart > i am trying this initially on one multicore pc > how should it look like if the restart succeed? should it work in the same terminal in which i am running restart command > my test app has 5000 iterations , checkpoint is taken at iteration no 300 for example , if i choose to restart from this checkpoint file should it restart near this iteration no 300 > > > 2013/6/6 Wesley Bland <wbland(a)mcs.anl.gov> > Is there actually anything in those checkpoints? With a checkpoint happening every 4 seconds you may be overdoing it. > > Wesley > > On Jun 5, 2013, at 2:14 PM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > > > I don't know, but see if anything on this page helps: > > http://wiki.mpich.org/mpich/index.php/Checkpointing > > > > On Jun 5, 2013, at 4:09 PM, john donald wrote: > > > >> > >> > >> ---------- Forwarded message ---------- > >> From: john donald <johnd9886(a)gmail.com> > >> Date: 2013/6/3 > >> Subject: ckpoint-num error > >> To: mpich-discuss(a)mcs.anl.gov > >> > >> > >> i used mpiexec with checkpoint and created two checkpoint files: > >> > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint -ckpoint-interval 4 -n 4 /home/john/app/md > >> > >> context-num0-0-0 > >> context-num1-0-0 > >> > >> > >> i am trying to make a restart > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint -n 4 -ckpoint-num 1 > >> > >> but nothing happened it just hangs > >> i also tried: > >> mpiexec -ckpointlib blcr -ckpoint-prefix /home/john/ckpts/app.ckpoint -n 4 -ckpoint-num 0-0-0 > >> also hangs > >> > >> _______________________________________________ > >> 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