May 2013 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] install + config on windows
by Jayesh Krishna 03 May '13

03 May '13

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 >>>> >>>> >>> >>> >> >> > > -- Benoit Véler Adhérent au groupe JAM Ingénierie 180 Avenue du Genevois, Parc d'Activité de Croix Rousse 73000 Chambéry http://www.spatiogis.fr 06-46-13-40-94 _______________________________________________ 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] install + config on windows
by spatiogis 03 May '13

03 May '13

For this command : > # C:\Progra~1\MPICH2\bin\smpd -status C:\Users\Utilisateur>C:\Progra~1\MPICH2\bin\smpd -status smpd running on Benoit

1 0

Re: [mpich-discuss] install + config on windows
by spatiogis 03 May '13

03 May '13

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 >>>> >>>> >>> >>> >> >> > > -- Benoit Véler Adhérent au groupe JAM Ingénierie 180 Avenue du Genevois, Parc d'Activité de Croix Rousse 73000 Chambéry http://www.spatiogis.fr 06-46-13-40-94

1 0

Re: [mpich-discuss] install + config on windows
by Jayesh Krishna 03 May '13

03 May '13

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 >>> >>> >> >> > > -- Benoit Véler Adhérent au groupe JAM Ingénierie 180 Avenue du Genevois, Parc d'Activité de Croix Rousse 73000 Chambéry http://www.spatiogis.fr 06-46-13-40-94

1 0

Re: [mpich-discuss] install + config on windows
by Jayesh Krishna 03 May '13

03 May '13

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 >> >> > > -- Benoit Véler Adhérent au groupe JAM Ingénierie 180 Avenue du Genevois, Parc d'Activité de Croix Rousse 73000 Chambéry http://www.spatiogis.fr 06-46-13-40-94 _______________________________________________ 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] install + config on windows
by spatiogis 03 May '13

03 May '13

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 >> >> > > -- Benoit Véler Adhérent au groupe JAM Ingénierie 180 Avenue du Genevois, Parc d'Activité de Croix Rousse 73000 Chambéry http://www.spatiogis.fr 06-46-13-40-94

1 0

mpich-3.0.4: building shared libraries w/cygwin
by Brad Aagaard 02 May '13

02 May '13

I am trying to build shared libraries under cygwin for mpich 3.0.4 for use in the binary of a parallel application with Python modules (this is why we need shared libraries). Running configure/make/make install produces static libraries even though I configure with --enable-shared --disable-static. This happens with both --enable-sharedlibs=libtool and --enable-sharedlibs=cygwin-gcc. Examining the config.log (attached) seems to indicate there were no errors in the tests/configuration for shared libraries. What configure/make arguments should I use to build shared libraries on cygwin? Thanks, Brad

1 0

Re: [mpich-discuss] Network drive recognition problems by mpiexec
by Bauer, Robert 02 May '13

02 May '13

Jayesh: Yes, this was strictly a local run, but using network drives. The -localonly option worked. Thanks. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 1:23 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Well, if you think about it "it is the right thing to do" (Although I agree that mpiexec could add more flexibility). MPI processes are launched by the process manager that typically runs as a service and these processes don't have access to network drives due to security concerns (Windows security). However if you running all your MPI processes on the local computer you could try running your job with the "localonly" option (remove the map option and add "localonly" option: mpiexec -localonly -n 2 MY_MPI_PGM.exe ). Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> Cc: discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:49:31 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec Jayesh: This is unfortunate. What I find difficult to understand, is why mpiexec does not honor network drives that are already established, prior to its launch? Why must it "re-connect" on its own terms? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 12:43 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Unfortunately there is no way to specify different credentials for mapping network drives and launching MPI processes (jobs). An easy fix would be to create a local Windows user with the same username and password as the user used to share the network drive and register this user with mpiexec. # Assuming User FOO is the user used to share the network drive (with password BAR) # Create a local Windows user FOO with the same password BAR # Run "mpiexec -register" # When mpiexec prompts for registering the user register FOO (with password BAR) # Run your jobs (All jobs will now be launched using FOO's credentials - network drives will now be mapped using FOO's credentials). Hope this helps. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> Cc: discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:24:54 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec Jayesh: When I establish the networked drive using "map network drive" , I identify of course computer name, and share drive name, but I also must enter in a user name and password that differs from my user account and password on the local computer on which I hope to execute mpiexec. I see your point, if I issue -map request through mpiexec, then the mpiexec would also need the user name and password pertaining to the computer that is hosting the network drive. How may I pass on these credentials to mpiexec? If this is going to turn in to quite a bit of back and forth, I would be happy to t-con with you on this. I am presently at the 215 number below. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 12:15 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Are the network drives shared/accessible by the user registered with mpiexec? The user registered with mpiexec is the user mpiexec uses to launch the job. While launching the process manager uses credentials of this user to map the network drives. The network drives could be mapped as any user from the Windows explorer. Please try disconnecting and reconnecting your mapped drive using the user registered with mpiexec. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov>, discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:07:55 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec The network drives are already connected, prior to executing mpiexec. The network drives also work after mpiexec has executed. The network drives are not working while mpiexec is loaded. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 10:22 AM To: discuss(a)mpich.org Cc: Bauer, Robert Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Are the network drives accessible by the user launching the job (registered with mpiexec)? Try manually mapping the network drive, as the user registered with mpiexec, to make sure it works. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: discuss(a)mpich.org Sent: Wednesday, May 1, 2013 6:19:19 PM Subject: [mpich-discuss] Network drive recognition problems by mpiexec The mpiexec program on a windows environment does not recognize networked drives despite my attempts at using –map and –mapall. Can anyone provide suggestions? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835

1 0

Re: [mpich-discuss] Network drive recognition problems by mpiexec
by Jayesh Krishna 02 May '13

02 May '13

Hi, Well, if you think about it "it is the right thing to do" (Although I agree that mpiexec could add more flexibility). MPI processes are launched by the process manager that typically runs as a service and these processes don't have access to network drives due to security concerns (Windows security). However if you running all your MPI processes on the local computer you could try running your job with the "localonly" option (remove the map option and add "localonly" option: mpiexec -localonly -n 2 MY_MPI_PGM.exe ). Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> Cc: discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:49:31 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec Jayesh: This is unfortunate. What I find difficult to understand, is why mpiexec does not honor network drives that are already established, prior to its launch? Why must it "re-connect" on its own terms? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 12:43 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Unfortunately there is no way to specify different credentials for mapping network drives and launching MPI processes (jobs). An easy fix would be to create a local Windows user with the same username and password as the user used to share the network drive and register this user with mpiexec. # Assuming User FOO is the user used to share the network drive (with password BAR) # Create a local Windows user FOO with the same password BAR # Run "mpiexec -register" # When mpiexec prompts for registering the user register FOO (with password BAR) # Run your jobs (All jobs will now be launched using FOO's credentials - network drives will now be mapped using FOO's credentials). Hope this helps. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> Cc: discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:24:54 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec Jayesh: When I establish the networked drive using "map network drive" , I identify of course computer name, and share drive name, but I also must enter in a user name and password that differs from my user account and password on the local computer on which I hope to execute mpiexec. I see your point, if I issue -map request through mpiexec, then the mpiexec would also need the user name and password pertaining to the computer that is hosting the network drive. How may I pass on these credentials to mpiexec? If this is going to turn in to quite a bit of back and forth, I would be happy to t-con with you on this. I am presently at the 215 number below. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 12:15 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Are the network drives shared/accessible by the user registered with mpiexec? The user registered with mpiexec is the user mpiexec uses to launch the job. While launching the process manager uses credentials of this user to map the network drives. The network drives could be mapped as any user from the Windows explorer. Please try disconnecting and reconnecting your mapped drive using the user registered with mpiexec. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov>, discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:07:55 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec The network drives are already connected, prior to executing mpiexec. The network drives also work after mpiexec has executed. The network drives are not working while mpiexec is loaded. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 10:22 AM To: discuss(a)mpich.org Cc: Bauer, Robert Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Are the network drives accessible by the user launching the job (registered with mpiexec)? Try manually mapping the network drive, as the user registered with mpiexec, to make sure it works. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: discuss(a)mpich.org Sent: Wednesday, May 1, 2013 6:19:19 PM Subject: [mpich-discuss] Network drive recognition problems by mpiexec The mpiexec program on a windows environment does not recognize networked drives despite my attempts at using –map and –mapall. Can anyone provide suggestions? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835

1 0

Re: [mpich-discuss] Network drive recognition problems by mpiexec
by Bauer, Robert 02 May '13

02 May '13

Jayesh: This is unfortunate. What I find difficult to understand, is why mpiexec does not honor network drives that are already established, prior to its launch? Why must it "re-connect" on its own terms? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 12:43 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Unfortunately there is no way to specify different credentials for mapping network drives and launching MPI processes (jobs). An easy fix would be to create a local Windows user with the same username and password as the user used to share the network drive and register this user with mpiexec. # Assuming User FOO is the user used to share the network drive (with password BAR) # Create a local Windows user FOO with the same password BAR # Run "mpiexec -register" # When mpiexec prompts for registering the user register FOO (with password BAR) # Run your jobs (All jobs will now be launched using FOO's credentials - network drives will now be mapped using FOO's credentials). Hope this helps. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov> Cc: discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:24:54 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec Jayesh: When I establish the networked drive using "map network drive" , I identify of course computer name, and share drive name, but I also must enter in a user name and password that differs from my user account and password on the local computer on which I hope to execute mpiexec. I see your point, if I issue -map request through mpiexec, then the mpiexec would also need the user name and password pertaining to the computer that is hosting the network drive. How may I pass on these credentials to mpiexec? If this is going to turn in to quite a bit of back and forth, I would be happy to t-con with you on this. I am presently at the 215 number below. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 12:15 PM To: Bauer, Robert Cc: discuss(a)mpich.org Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Are the network drives shared/accessible by the user registered with mpiexec? The user registered with mpiexec is the user mpiexec uses to launch the job. While launching the process manager uses credentials of this user to map the network drives. The network drives could be mapped as any user from the Windows explorer. Please try disconnecting and reconnecting your mapped drive using the user registered with mpiexec. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: "Jayesh Krishna" <jayesh(a)mcs.anl.gov>, discuss(a)mpich.org Sent: Thursday, May 2, 2013 11:07:55 AM Subject: RE: [mpich-discuss] Network drive recognition problems by mpiexec The network drives are already connected, prior to executing mpiexec. The network drives also work after mpiexec has executed. The network drives are not working while mpiexec is loaded. Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com -----Original Message----- From: Jayesh Krishna [mailto:[email protected]] Sent: Thursday, May 02, 2013 10:22 AM To: discuss(a)mpich.org Cc: Bauer, Robert Subject: Re: [mpich-discuss] Network drive recognition problems by mpiexec Hi, Are the network drives accessible by the user launching the job (registered with mpiexec)? Try manually mapping the network drive, as the user registered with mpiexec, to make sure it works. Regards, Jayesh ----- Original Message ----- From: "Robert Bauer" <Robert.Bauer(a)iconplc.com> To: discuss(a)mpich.org Sent: Wednesday, May 1, 2013 6:19:19 PM Subject: [mpich-discuss] Network drive recognition problems by mpiexec The mpiexec program on a windows environment does not recognize networked drives despite my attempts at using –map and –mapall. Can anyone provide suggestions? Robert J. Bauer, Ph.D. Vice President, Pharmacometrics, R&D ICON Development Solutions 7740 Milestone Parkway Suite 150 Hanover, MD 21076 Tel: (215) 616-6428 Mob: (925) 286-0769 Email: Robert.Bauer(a)iconplc.com Web: www.iconplc.com ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835 ICON plc made the following annotations. ------------------------------------------------------------------------------ This e-mail transmission may contain confidential or legally privileged information that is intended only for the individual or entity named in the e-mail address. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or reliance upon the contents of this e-mail is strictly prohibited. If you have received this e-mail transmission in error, please reply to the sender, so that ICON plc can arrange for proper delivery, and then please delete the message. Thank You, ICON plc South County Business Park Leopardstown Dublin 18 Ireland Registered number: 145835

1 0