- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Problems running MPICH jobs under SLURM
by Markus Geimer 07 Jun '13

07 Jun '13

Hi Pavan, The nightly snapshot fixes the issue for me. Many thanks! @John: Did you also recompile your sample application? From what I understand, the issue is not in hydra but in the MPI library (please correct me if I'm wrong, Pavan). Best regards, Markus On 06/07/13 08:40, Pavan Balaji wrote: > > FYI, I believe this is now fixed. Please try out the latest nightly > snapshot and let us know if you are still running into this issue: > > http://www.mpich.org/static/tarballs/nightly/master/hydra/ > http://www.mpich.org/static/tarballs/nightly/master/mpich/ > > -- Pavan > > On 06/06/2013 01:39 AM, Biddiscombe, John A. wrote: >> Just FYI. I am also getting the double free error when I run under >> slurm (mpich 3.0.4). Please don't take correspondence off list as I'm >> following the thread. >> >> I can't add anything more useful than Markus has already provided with >> his stack trace and logs. >> >> [I did find that if I configure --with-slurm and use srun instead of >> mpiexec , then all works, as expected, but I need mpiexec to pass env >> vars to processes using mpmd syntax] >> >> JB >> >> -----Original Message----- >> From: discuss-bounces(a)mpich.org [mailto:[email protected]] On >> Behalf Of Markus Geimer >> Sent: 03 June 2013 16:36 >> To: Pavan Balaji >> Cc: discuss(a)mpich.org >> Subject: Re: [mpich-discuss] Problems running MPICH jobs under SLURM >> >> Pavan, >> >>> 1. Can you run your application processes using "ddd" or some other >>> debugger to see where the double free is coming from? You might have >>> to build mpich with --enable-g=dbg to get the debug symbols in. >> >> Here is the full stack backtrace: >> >> ----- 8< ----- 8< ----- 8< ----- 8< ----- 8< ----- 8< ----- >> >> #0 0x00007ffff6deb475 in *__GI_raise (sig=<optimized out>) >> at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 >> #1 0x00007ffff6dee6f0 in *__GI_abort () at abort.c:92 >> #2 0x00007ffff6e2652b in __libc_message (do_abort=<optimized out>, >> fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 >> #3 0x00007ffff6e2fd76 in malloc_printerr (action=3, >> str=0x7ffff6f081e0 "double free or corruption (fasttop)", >> ptr=<optimized out>) at malloc.c:6283 >> #4 0x00007ffff6e34aac in *__GI___libc_free (mem=<optimized out>) >> at malloc.c:3738 >> #5 0x00007ffff7a1d5d9 in populate_ids_from_mapping ( >> did_map=<synthetic pointer>, num_nodes=<synthetic pointer>, >> mapping=<optimized out>, pg=<optimized out>) >> at src/mpid/ch3/src/mpid_vc.c:1063 >> #6 MPIDI_Populate_vc_node_ids (pg=pg@entry=0x604910, >> our_pg_rank=our_pg_rank@entry=0) at src/mpid/ch3/src/mpid_vc.c:1193 >> #7 0x00007ffff7a17dd6 in MPID_Init (argc=argc@entry=0x7fffffffd97c, >> argv=argv@entry=0x7fffffffd970, requested=requested@entry=0, >> provided=provided@entry=0x7fffffffd8e8, >> has_args=has_args@entry=0x7fffffffd8e0, >> has_env=has_env@entry=0x7fffffffd8e4) at >> src/mpid/ch3/src/mpid_init.c:156 >> #8 0x00007ffff7acdf7f in MPIR_Init_thread >> (argc=argc@entry=0x7fffffffd97c, >> argv=argv@entry=0x7fffffffd970, required=required@entry=0, >> provided=provided@entry=0x7fffffffd944) at >> src/mpi/init/initthread.c:431 >> #9 0x00007ffff7acd90e in PMPI_Init (argc=0x7fffffffd97c, >> argv=0x7fffffffd970) >> at src/mpi/init/init.c:136 >> #10 0x000000000040086d in main () >> >> ----- >8 ----- >8 ----- >8 ----- >8 ----- >8 ----- >8 ----- >> >>> 2. Can you send me the output with the ssh launcher as well? >> >> See mail sent off-list. >> >> Thanks, >> Markus >> >> -- >> Dr. Markus Geimer >> Juelich Supercomputing Centre >> Institute for Advanced Simulation >> Forschungszentrum Juelich GmbH >> 52425 Juelich, Germany >> >> Phone: +49-2461-61-1773 >> Fax: +49-2461-61-6656 >> E-mail: m.geimer(a)fz-juelich.de >> WWW: http://www.fz-juelich.de/jsc/ >> >> >> >> ------------------------------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------------------------ >> >> Forschungszentrum Juelich GmbH >> 52425 Juelich >> Sitz der Gesellschaft: Juelich >> Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 >> Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher >> Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten >> Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. >> Sebastian M. Schmidt >> ------------------------------------------------------------------------------------------------ >> >> ------------------------------------------------------------------------------------------------ >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > -- Dr. Markus Geimer Juelich Supercomputing Centre Institute for Advanced Simulation Forschungszentrum Juelich GmbH 52425 Juelich, Germany Phone: +49-2461-61-1773 Fax: +49-2461-61-6656 E-mail: m.geimer(a)fz-juelich.de WWW: http://www.fz-juelich.de/jsc/

1 0

Re: [mpich-discuss] crash on 2^31 size in MPI_Win_allocate_shared(...)
by Jeff Hammond 07 Jun '13

07 Jun '13

First, "long unsigned int window_size=2147483648" is not correct. They type you need to use there is MPI_Aint. The syntax of this function is int MPI_Win_allocate_shared(MPI_Aint size, int disp_unit, MPI_Info info, MPI_Comm comm, void *baseptr, MPI_Win *win) It may be true that "long unsigned int" is safely case to MPI_Aint, but that's a very danger way to write code and it may be broken on some platforms. In any case, everything above 2^31 is probably not okay. Unless absolutely every integer type used in the code paths you are hitting is size_t (or equivalent) and not int, you're going to hit overflow somewhere. Maybe I'm wrong, but you should verify (as a debugging mechanism, not in general) that MPI_Win_allocate_shared is behaving as desired by memset-ing the resulting data (mem) to verify that you're actually getting e.g. 2^34 bytes back. If /dev/shm is 4G, I'm not sure how that's possible but maybe the implementation doesn't use that. I'm going to be on a plane today but I'll run your code on my machine and try to figure out more about how "count-safe" MPI_Win_allocate_shared is. Jeff PS Installing MPICH in ~/git/openmpi is just dirty :-) On Fri, Jun 7, 2013 at 5:50 AM, Weise Steffen <Steffen.Weise(a)iec.tu-freiberg.de> wrote: > Dear mailing-list, > > this is my first time posting here. I found that with version 3.0.4 using MPI_Win_allocate_shared i get an error when using a size exactly 2^31 everything below and above is ok. Though i also had the same issue with 2^34. Some kind of division or type conversion seems to be off. (/dev/shm has 4G so it is not a size issue.. i know what those errors look like) > > I attach my code and the output i get on a linux (debian 6.0) 64 bit machine (same issue on a mac though) . > > I'll be happy to provide more machine details or everything you guys need to analyse whats going on. > > with kind regards, > Steffen Weise > > > > _______________________________________________ > 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] Linking to personal libraries
by Pavan Balaji 07 Jun '13

07 Jun '13

On 06/07/2013 08:35 AM, Wesley Bland wrote: > As long as you have *.a versions of your library, you can use those > instead of the *.so versions. You'll need to pass -static to mpicc to > make that work. > > You also need to link MPICH statically, but as of all of the released > versions of MPICH, that is the default behavior. In future releases, > that will change. I believe the configure flag that you'll have to use > is --enable-static, but I could be wrong about that. FYI, --enable-static is the right flag, but it's not required. Till mpich-3.0.4, the default is --enable-static --disable-shared. From mpich-3.1.x, the default will be --enable-static --enable-shared. (though shared will be prioritized by the system, unless you pass -static to mpicc). -- Pavan -- Pavan Balaji http://www.mcs.anl.gov/~balaji

1 0

Re: [mpich-discuss] Linking to personal libraries
by Wesley Bland 07 Jun '13

07 Jun '13

As long as you have *.a versions of your library, you can use those instead of the *.so versions. You'll need to pass -static to mpicc to make that work. You also need to link MPICH statically, but as of all of the released versions of MPICH, that is the default behavior. In future releases, that will change. I believe the configure flag that you'll have to use is --enable-static, but I could be wrong about that. Wesley On Jun 7, 2013, at 4:48 AM, Alejandro Allievi <alejandro.allievi(a)gmail.com> wrote: > Good morning Wesley, > > Under NFS, is there a way to bypass dynamic linking and "force" static linking?? > > Thanks. > > Alejandro > > > On Thu, Jun 6, 2013 at 3:52 PM, Alejandro Allievi <alejandro.allievi(a)gmail.com> wrote: > Thanks!! > > > On Thu, Jun 6, 2013 at 3:44 PM, Wesley Bland <wbland(a)mcs.anl.gov> wrote: > No, this is the correct way to do it. > > On Jun 6, 2013, at 11:12 AM, Alejandro Allievi <alejandro.allievi(a)gmail.com> wrote: > >> Is there a better way?? >> >> >> On Thu, Jun 6, 2013 at 3:40 PM, Wesley Bland <wbland(a)mcs.anl.gov> wrote: >> That's true and for most smallish clusters, that's how people use it. >> >> On Jun 6, 2013, at 11:09 AM, Alejandro Allievi <alejandro.allievi(a)gmail.com> wrote: >> >>> Hi Wesley, >>> >>> Just to clarify myself: provided our NFS mirrors my home directory and that LD_LIBRARY_PATH is set correctly, the dynamic compile/link step for the user (me) is the same as for static compile/link?? >>> >>> Thanks again Wesley!! >>> >>> Alejandro >>> >>> >>> On Thu, Jun 6, 2013 at 11:15 AM, Wesley Bland <wbland(a)mcs.anl.gov> wrote: >>> It depends on whether you are linking your library statically or dynamically. If you are linking statically, the linker puts everything in one executable that is sent to all of the nodes. If you do it dynamically, you need to make sure your libraries are available on all of the nodes you will be using (usually by using something like NFS to mirror your home directory across the cluster. You will also need to make sure your environment is set up correctly to allow the libraries to be found on the remote process, usually via an environment variable such as LD_LIBRARY_PATH. >>> >>> Wesley >>> >>> >>> On Jun 6, 2013, at 6:18 AM, Alejandro Allievi <alejandro.allievi(a)gmail.com> wrote: >>> >>>> Hi >>>> >>>> When linking to personal libraries using MPICH2, how does each process access them in a distributed environment?? Does the linker actually combines everything into a single executable program and "sends a copy" of entire executable to each process even though not all processes may use the libraries?? Can somebody shed some light on the entire linking process?? >>>> >>>> Thanks for any help!! >>>> >>>> Alejandro >>>> _______________________________________________ >>>> 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 >>> >>> >>> >>> -- >>> Alejandro Allievi >>> http://www.ace-net.ca/wiki/Alejandro_Allievi >>> >>> "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre véritable sentiment n'est pas celui dans lequel nous n'avons jamais vacillé; mais celui auquel nous sommes le plus habituellement revenus". Denis Diderot. >>> >>> Este e-mail esta consignado sólo para el destinatario designado en el mismo y puede contener información confidencial y privilegiada. Su distribución o copiado está prohibido. Si Usted no fuera el destinatario designado, por favor notifíquenos de inmediato y destruya este e-mail en forma permanente así como todas las copias del mismo. Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci. This e-mail may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it. >>> _______________________________________________ >>> 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 >> >> >> >> -- >> Alejandro Allievi >> http://www.ace-net.ca/wiki/Alejandro_Allievi >> >> "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre véritable sentiment n'est pas celui dans lequel nous n'avons jamais vacillé; mais celui auquel nous sommes le plus habituellement revenus". Denis Diderot. >> >> Este e-mail esta consignado sólo para el destinatario designado en el mismo y puede contener información confidencial y privilegiada. Su distribución o copiado está prohibido. Si Usted no fuera el destinatario designado, por favor notifíquenos de inmediato y destruya este e-mail en forma permanente así como todas las copias del mismo. Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci. This e-mail may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it. >> _______________________________________________ >> 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 > > > > -- > Alejandro Allievi > http://www.ace-net.ca/wiki/Alejandro_Allievi > > "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre véritable sentiment n'est pas celui dans lequel nous n'avons jamais vacillé; mais celui auquel nous sommes le plus habituellement revenus". Denis Diderot. > > Este e-mail esta consignado sólo para el destinatario designado en el mismo y puede contener información confidencial y privilegiada. Su distribución o copiado está prohibido. Si Usted no fuera el destinatario designado, por favor notifíquenos de inmediato y destruya este e-mail en forma permanente así como todas las copias del mismo. Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci. This e-mail may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it. > > > > -- > Alejandro Allievi > http://www.ace-net.ca/wiki/Alejandro_Allievi > > "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre véritable sentiment n'est pas celui dans lequel nous n'avons jamais vacillé; mais celui auquel nous sommes le plus habituellement revenus". Denis Diderot. > > Este e-mail esta consignado sólo para el destinatario designado en el mismo y puede contener información confidencial y privilegiada. Su distribución o copiado está prohibido. Si Usted no fuera el destinatario designado, por favor notifíquenos de inmediato y destruya este e-mail en forma permanente así como todas las copias del mismo. Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci. This e-mail may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it. > _______________________________________________ > 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] Linking to personal libraries
by Pavan Balaji 07 Jun '13

07 Jun '13

static vs. dynamic linking has nothing to do with the NFS. With static linking, the executable needs to be available on all nodes (either through the NFS or through explicit copies). With dynamic linking, the executable and all its dependency libraries need to be available on all nodes (again, either through the NFS or through explicit copies). So far, mpich used static builds by default. All released versions so far use this model. You can ask it to build dynamic libraries as well by passing --enable-shared to configure. We recently moved to building mpich as a dynamic library by default as well (both static and dynamic libraries will be built, but the dynamic library is prioritized for linking). You'll see this model in the upcoming mpich-3.1.x series and beyond. -- Pavan On 06/07/2013 06:48 AM, Alejandro Allievi wrote: > Good morning Wesley, > > Under NFS, is there a way to bypass dynamic linking and "force" static > linking?? > > Thanks. > > Alejandro > > > On Thu, Jun 6, 2013 at 3:52 PM, Alejandro Allievi > <alejandro.allievi(a)gmail.com <mailto:[email protected]>> wrote: > > Thanks!! > > > On Thu, Jun 6, 2013 at 3:44 PM, Wesley Bland <wbland(a)mcs.anl.gov > <mailto:[email protected]>> wrote: > > No, this is the correct way to do it. > > On Jun 6, 2013, at 11:12 AM, Alejandro Allievi > <alejandro.allievi(a)gmail.com > <mailto:[email protected]>> wrote: > >> Is there a better way?? >> >> >> On Thu, Jun 6, 2013 at 3:40 PM, Wesley Bland >> <wbland(a)mcs.anl.gov <mailto:[email protected]>> wrote: >> >> That's true and for most smallish clusters, that's how >> people use it. >> >> On Jun 6, 2013, at 11:09 AM, Alejandro Allievi >> <alejandro.allievi(a)gmail.com >> <mailto:[email protected]>> wrote: >> >>> Hi Wesley, >>> >>> Just to clarify myself: provided our NFS mirrors my home >>> directory and that LD_LIBRARY_PATH is set correctly, the >>> dynamic compile/link step for the user (me) is the same >>> as for static compile/link?? >>> >>> Thanks again Wesley!! >>> >>> Alejandro >>> >>> >>> On Thu, Jun 6, 2013 at 11:15 AM, Wesley Bland >>> <wbland(a)mcs.anl.gov <mailto:[email protected]>> wrote: >>> >>> It depends on whether you are linking your library >>> statically or dynamically. If you are linking >>> statically, the linker puts everything in one >>> executable that is sent to all of the nodes. If you >>> do it dynamically, you need to make sure your >>> libraries are available on all of the nodes you will >>> be using (usually by using something like NFS to >>> mirror your home directory across the cluster. You >>> will also need to make sure your environment is set >>> up correctly to allow the libraries to be found on >>> the remote process, usually via an environment >>> variable such as LD_LIBRARY_PATH. >>> >>> Wesley >>> >>> >>> On Jun 6, 2013, at 6:18 AM, Alejandro Allievi >>> <alejandro.allievi(a)gmail.com >>> <mailto:[email protected]>> wrote: >>> >>>> H >>>> i >>>> >>>> When linking to personal libraries using MPICH2, how >>>> does each process access them in a distributed >>>> environment?? Does the linker actually >>>> combines >>>> everything >>>> into a single >>>> executable >>>> program >>>> and "sends a copy" of entire executable to each >>>> process even though not all processes may use the >>>> libraries?? Can somebody shed some light on the >>>> entire linking process?? >>>> >>>> Thanks for any help!! >>>> >>>> Alejandro >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org >>>> <mailto:[email protected]> >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> <mailto:[email protected]> >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >>> >>> >>> >>> -- >>> Alejandro Allievi >>> http://www.ace-net.ca/wiki/Alejandro_Allievi >>> "Tenez, mon ami, si vous y pensez bien, vous trouverez >>> qu'en tout, notre vï¿½ritable sentiment n'est pas celui >>> dans lequel nous n'avons jamais vacillï¿½; mais celui >>> auquel nous sommes le plus habituellement revenus". Denis >>> Diderot. >>> Este e-mail esta consignado sï¿½lo para el destinatario >>> designado en el mismo y puede contener informaciï¿½n >>> confidencial y privilegiada. Su distribuciï¿½n o copiado >>> estï¿½ prohibido. Si Usted no fuera el destinatario >>> designado, por favor notifï¿½quenos de inmediato y destruya >>> este e-mail en forma permanente asï¿½ como todas las copias >>> del mismo. _Ce courriel peut renfermer des renseignements >>> confidentiels et privilï¿½giï¿½s et s'adresse au destinataire >>> dï¿½signï¿½ seulement. La distribution ou la copie de ce >>> courriel est interdit. Si vous n'ï¿½tes pas le destinataire >>> dï¿½signï¿½, veuillez nous en aviser immï¿½diatement et >>> dï¿½truire de faï¿½on permanente ce courriel ainsi que toute >>> copie de celui-ci_. This e-mail may contain confidential >>> information, and is intended only for the named recipient >>> and may be privileged. Distribution or copying of this >>> email is prohibited. If you are not the named recipient, >>> please notify us immediately and permanently destroy this >>> email and all copies of it. >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> <mailto:[email protected]> >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> >> >> >> -- >> Alejandro Allievi >> http://www.ace-net.ca/wiki/Alejandro_Allievi >> "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en >> tout, notre vï¿½ritable sentiment n'est pas celui dans lequel >> nous n'avons jamais vacillï¿½; mais celui auquel nous sommes le >> plus habituellement revenus". Denis Diderot. >> Este e-mail esta consignado sï¿½lo para el destinatario >> designado en el mismo y puede contener informaciï¿½n >> confidencial y privilegiada. Su distribuciï¿½n o copiado estï¿½ >> prohibido. Si Usted no fuera el destinatario designado, por >> favor notifï¿½quenos de inmediato y destruya este e-mail en >> forma permanente asï¿½ como todas las copias del mismo. _Ce >> courriel peut renfermer des renseignements confidentiels et >> privilï¿½giï¿½s et s'adresse au destinataire dï¿½signï¿½ seulement. La >> distribution ou la copie de ce courriel est interdit. Si vous >> n'ï¿½tes pas le destinataire dï¿½signï¿½, veuillez nous en aviser >> immï¿½diatement et dï¿½truire de faï¿½on permanente ce courriel >> ainsi que toute copie de celui-ci_. This e-mail may contain >> confidential information, and is intended only for the named >> recipient and may be privileged. Distribution or copying of >> this email is prohibited. If you are not the named recipient, >> please notify us immediately and permanently destroy this >> email and all copies of it. >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org <mailto:[email protected]> >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org <mailto:[email protected]> > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > > > > > -- > Alejandro Allievi > http://www.ace-net.ca/wiki/Alejandro_Allievi > "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, > notre vï¿½ritable sentiment n'est pas celui dans lequel nous n'avons > jamais vacillï¿½; mais celui auquel nous sommes le plus habituellement > revenus". Denis Diderot. > Este e-mail esta consignado sï¿½lo para el destinatario designado en > el mismo y puede contener informaciï¿½n confidencial y privilegiada. > Su distribuciï¿½n o copiado estï¿½ prohibido. Si Usted no fuera el > destinatario designado, por favor notifï¿½quenos de inmediato y > destruya este e-mail en forma permanente asï¿½ como todas las copias > del mismo. _Ce courriel peut renfermer des renseignements > confidentiels et privilï¿½giï¿½s et s'adresse au destinataire dï¿½signï¿½ > seulement. La distribution ou la copie de ce courriel est interdit. > Si vous n'ï¿½tes pas le destinataire dï¿½signï¿½, veuillez nous en aviser > immï¿½diatement et dï¿½truire de faï¿½on permanente ce courriel ainsi que > toute copie de celui-ci_. This e-mail may contain confidential > information, and is intended only for the named recipient and may be > privileged. Distribution or copying of this email is prohibited. If > you are not the named recipient, please notify us immediately and > permanently destroy this email and all copies of it. > > > > > -- > Alejandro Allievi > http://www.ace-net.ca/wiki/Alejandro_Allievi > "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre > vï¿½ritable sentiment n'est pas celui dans lequel nous n'avons jamais > vacillï¿½; mais celui auquel nous sommes le plus habituellement revenus". > Denis Diderot. > Este e-mail esta consignado sï¿½lo para el destinatario designado en el > mismo y puede contener informaciï¿½n confidencial y privilegiada. Su > distribuciï¿½n o copiado estï¿½ prohibido. Si Usted no fuera el destinatario > designado, por favor notifï¿½quenos de inmediato y destruya este e-mail en > forma permanente asï¿½ como todas las copias del mismo. _Ce courriel peut > renfermer des renseignements confidentiels et privilï¿½giï¿½s et s'adresse > au destinataire dï¿½signï¿½ seulement. La distribution ou la copie de ce > courriel est interdit. Si vous n'ï¿½tes pas le destinataire dï¿½signï¿½, > veuillez nous en aviser immï¿½diatement et dï¿½truire de faï¿½on permanente ce > courriel ainsi que toute copie de celui-ci_. This e-mail may contain > confidential information, and is intended only for the named recipient > and may be privileged. Distribution or copying of this email is > prohibited. If you are not the named recipient, please notify us > immediately and permanently destroy this email and all copies of it. > > > _______________________________________________ > 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

crash on 2^31 size in MPI_Win_allocate_shared(...)
by Weise Steffen 07 Jun '13

07 Jun '13

Dear mailing-list, this is my first time posting here. I found that with version 3.0.4 using MPI_Win_allocate_shared i get an error when using a size exactly 2^31 everything below and above is ok. Though i also had the same issue with 2^34. Some kind of division or type conversion seems to be off. (/dev/shm has 4G so it is not a size issue.. i know what those errors look like) I attach my code and the output i get on a linux (debian 6.0) 64 bit machine (same issue on a mac though) . I'll be happy to provide more machine details or everything you guys need to analyse whats going on. with kind regards, Steffen Weise

1 0

Re: [mpich-discuss] Linking to personal libraries
by Alejandro Allievi 07 Jun '13

07 Jun '13

Good morning Wesley, Under NFS, is there a way to bypass dynamic linking and "force" static linking?? Thanks. Alejandro On Thu, Jun 6, 2013 at 3:52 PM, Alejandro Allievi < alejandro.allievi(a)gmail.com> wrote: > Thanks!! > > > On Thu, Jun 6, 2013 at 3:44 PM, Wesley Bland <wbland(a)mcs.anl.gov> wrote: > >> No, this is the correct way to do it. >> >> On Jun 6, 2013, at 11:12 AM, Alejandro Allievi < >> alejandro.allievi(a)gmail.com> wrote: >> >> Is there a better way?? >> >> >> On Thu, Jun 6, 2013 at 3:40 PM, Wesley Bland <wbland(a)mcs.anl.gov> wrote: >> >>> That's true and for most smallish clusters, that's how people use it. >>> >>> On Jun 6, 2013, at 11:09 AM, Alejandro Allievi < >>> alejandro.allievi(a)gmail.com> wrote: >>> >>> Hi Wesley, >>> >>> Just to clarify myself: provided our NFS mirrors my home directory and >>> that LD_LIBRARY_PATH is set correctly, the dynamic compile/link step >>> for the user (me) is the same as for static compile/link?? >>> >>> Thanks again Wesley!! >>> >>> Alejandro >>> >>> >>> On Thu, Jun 6, 2013 at 11:15 AM, Wesley Bland <wbland(a)mcs.anl.gov>wrote: >>> >>>> It depends on whether you are linking your library statically or >>>> dynamically. If you are linking statically, the linker puts everything in >>>> one executable that is sent to all of the nodes. If you do it dynamically, >>>> you need to make sure your libraries are available on all of the nodes you >>>> will be using (usually by using something like NFS to mirror your home >>>> directory across the cluster. You will also need to make sure your >>>> environment is set up correctly to allow the libraries to be found on the >>>> remote process, usually via an environment variable such as >>>> LD_LIBRARY_PATH. >>>> >>>> Wesley >>>> >>>> >>>> On Jun 6, 2013, at 6:18 AM, Alejandro Allievi < >>>> alejandro.allievi(a)gmail.com> wrote: >>>> >>>> H >>>> i >>>> >>>> When linking to personal libraries using MPICH2, how does each process >>>> access them in a distributed environment?? Does the linker actually >>>> combines >>>> everything >>>> into a single >>>> executable >>>> program >>>> and "sends a copy" of entire executable to each process even though not >>>> all processes may use the libraries?? Can somebody shed some light on the >>>> entire linking process?? >>>> >>>> Thanks for any help!! >>>> >>>> Alejandro >>>> >>>> _______________________________________________ >>>> 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 >>>> >>> >>> >>> >>> -- >>> Alejandro Allievi >>> http://www.ace-net.ca/wiki/Alejandro_Allievi >>> >>> "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre >>> véritable sentiment n'est pas celui dans lequel nous n'avons jamais >>> vacillé; mais celui auquel nous sommes le plus habituellement revenus". >>> Denis Diderot. >>> >>> Este e-mail esta consignado sólo para el destinatario designado en el >>> mismo y puede contener información confidencial y privilegiada. Su >>> distribución o copiado está prohibido. Si Usted no fuera el destinatario >>> designado, por favor notifíquenos de inmediato y destruya este e-mail en >>> forma permanente así como todas las copias del mismo. *Ce courriel peut >>> renfermer des renseignements confidentiels et privilégiés et s'adresse au >>> destinataire désigné seulement. La distribution ou la copie de ce courriel >>> est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en >>> aviser immédiatement et détruire de façon permanente ce courriel ainsi que >>> toute copie de celui-ci*. This e-mail may contain confidential >>> information, and is intended only for the named recipient and may be >>> privileged. Distribution or copying of this email is prohibited. If you are >>> not the named recipient, please notify us immediately and permanently >>> destroy this email and all copies of it. >>> _______________________________________________ >>> 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 >>> >> >> >> >> -- >> Alejandro Allievi >> http://www.ace-net.ca/wiki/Alejandro_Allievi >> >> "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre >> véritable sentiment n'est pas celui dans lequel nous n'avons jamais >> vacillé; mais celui auquel nous sommes le plus habituellement revenus". >> Denis Diderot. >> >> Este e-mail esta consignado sólo para el destinatario designado en el >> mismo y puede contener información confidencial y privilegiada. Su >> distribución o copiado está prohibido. Si Usted no fuera el destinatario >> designado, por favor notifíquenos de inmediato y destruya este e-mail en >> forma permanente así como todas las copias del mismo. *Ce courriel peut >> renfermer des renseignements confidentiels et privilégiés et s'adresse au >> destinataire désigné seulement. La distribution ou la copie de ce courriel >> est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en >> aviser immédiatement et détruire de façon permanente ce courriel ainsi que >> toute copie de celui-ci*. This e-mail may contain confidential >> information, and is intended only for the named recipient and may be >> privileged. Distribution or copying of this email is prohibited. If you are >> not the named recipient, please notify us immediately and permanently >> destroy this email and all copies of it. >> _______________________________________________ >> 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 >> > > > > -- > Alejandro Allievi > http://www.ace-net.ca/wiki/Alejandro_Allievi > > "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre > véritable sentiment n'est pas celui dans lequel nous n'avons jamais > vacillé; mais celui auquel nous sommes le plus habituellement revenus". > Denis Diderot. > > Este e-mail esta consignado sólo para el destinatario designado en el > mismo y puede contener información confidencial y privilegiada. Su > distribución o copiado está prohibido. Si Usted no fuera el destinatario > designado, por favor notifíquenos de inmediato y destruya este e-mail en > forma permanente así como todas las copias del mismo. *Ce courriel peut > renfermer des renseignements confidentiels et privilégiés et s'adresse au > destinataire désigné seulement. La distribution ou la copie de ce courriel > est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en > aviser immédiatement et détruire de façon permanente ce courriel ainsi que > toute copie de celui-ci*. This e-mail may contain confidential > information, and is intended only for the named recipient and may be > privileged. Distribution or copying of this email is prohibited. If you are > not the named recipient, please notify us immediately and permanently > destroy this email and all copies of it. > -- Alejandro Allievi http://www.ace-net.ca/wiki/Alejandro_Allievi "Tenez, mon ami, si vous y pensez bien, vous trouverez qu'en tout, notre véritable sentiment n'est pas celui dans lequel nous n'avons jamais vacillé; mais celui auquel nous sommes le plus habituellement revenus". Denis Diderot. Este e-mail esta consignado sólo para el destinatario designado en el mismo y puede contener información confidencial y privilegiada. Su distribución o copiado está prohibido. Si Usted no fuera el destinatario designado, por favor notifíquenos de inmediato y destruya este e-mail en forma permanente así como todas las copias del mismo. *Ce courriel peut renfermer des renseignements confidentiels et privilégiés et s'adresse au destinataire désigné seulement. La distribution ou la copie de ce courriel est interdit. Si vous n'êtes pas le destinataire désigné, veuillez nous en aviser immédiatement et détruire de façon permanente ce courriel ainsi que toute copie de celui-ci*. This e-mail may contain confidential information, and is intended only for the named recipient and may be privileged. Distribution or copying of this email is prohibited. If you are not the named recipient, please notify us immediately and permanently destroy this email and all copies of it.

1 0

Re: [mpich-discuss] Problems running MPICH jobs under SLURM
by Biddiscombe, John A. 07 Jun '13

07 Jun '13

I downloaded the nightly tarball and recompiled/installed mpich (used mpich-master-v3.0.4-259-gf322ce79) I still get this (output below) with a simple hello world program. Now you must understand that I have no idea what I'm doing (really). I wanted to test some debugging features under slurm so installed slurm myself on a workstation with just 2 cores and have the bare minimum setup. I'm doing the following sudo munged & sudo slurmd & sudo slurmctld -D and then I can run jobs on the local machine and it seems to be ok, except that mpi jobs always give the double free error as below when run under slurm, but are just fine when run from the command line. My suspicion is that slurm is not actually using the hydra pm that I just compiled. I installed slurm from rpms. Should I recompile slurm myself and somehow tell it which mpi to use? My job script looks as follows ###################### #!/bin/bash # # Create the job script from the supplied parameters # #SBATCH --job-name=pvserver #SBATCH --time=00:04:00 #SBATCH --nodes=1 #SBATCH --partition=normal #SBATCH --output=/home/biddisco/slurm.out #SBATCH --error=/home/biddisco/slurm.err #SBATCH --mem=2048MB #export # echo "Path is $PATH" # echo "LD_LIBRARY_PATH is " $LD_LIBRARY_PATH # cd /home/biddisco/build/pv-38/bin/ #export PMI_DEBUG=9 #ulimit -s unlimited #ulimit -c 0 /home/biddisco/apps/mpich-3.0.4/bin/mpiexec -rmk slurm -n 2 /home/biddisco/build/hello/hello ###################### It gives the same result with or without the -rmk slurm and the #ulimit settings. Apologies for wasting your time, I'm certain I'm doing something wrong - I just don't know what. JB biddisco@breno2 ~ $ more ~/slurm.err *** glibc detected *** /home/biddisco/build/hello/hello: double free or corruption (fasttop): 0x0000000001896340 *** ======= Backtrace: ========= /lib/x86_64-linux-gnu/libc.so.6(+0x7eb96)[0x7f9a1695cb96] /home/biddisco/build/hello/hello(MPIDI_Populate_vc_node_ids+0x3f9)[0x427c89] /home/biddisco/build/hello/hello(MPID_Init+0x136)[0x4253f6] /home/biddisco/build/hello/hello(MPIR_Init_thread+0x22f)[0x414cbf] /home/biddisco/build/hello/hello(MPI_Init+0xae)[0x4146ee] /home/biddisco/build/hello/hello(main+0x22)[0x413f2e] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xed)[0x7f9a168ff76d] /home/biddisco/build/hello/hello[0x413e31] ======= Memory map: ======== 00400000-0051a000 r-xp 00000000 08:01 8661191 /home/biddisco/build/hello/hello 0071a000-00727000 r--p 0011a000 08:01 8661191 /home/biddisco/build/hello/hello 00727000-00729000 rw-p 00127000 08:01 8661191 /home/biddisco/build/hello/hello 00729000-00751000 rw-p 00000000 00:00 0 01895000-018b6000 rw-p 00000000 00:00 0 [heap] 7f9a166c8000-7f9a166dd000 r-xp 00000000 08:01 9047556 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f9a166dd000-7f9a168dc000 ---p 00015000 08:01 9047556 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f9a168dc000-7f9a168dd000 r--p 00014000 08:01 9047556 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f9a168dd000-7f9a168de000 rw-p 00015000 08:01 9047556 /lib/x86_64-linux-gnu/libgcc_s.so.1 7f9a168de000-7f9a16a93000 r-xp 00000000 08:01 9050358 /lib/x86_64-linux-gnu/libc-2.15.so 7f9a16a93000-7f9a16c92000 ---p 001b5000 08:01 9050358 /lib/x86_64-linux-gnu/libc-2.15.so 7f9a16c92000-7f9a16c96000 r--p 001b4000 08:01 9050358 /lib/x86_64-linux-gnu/libc-2.15.so 7f9a16c96000-7f9a16c98000 rw-p 001b8000 08:01 9050358 /lib/x86_64-linux-gnu/libc-2.15.so 7f9a16c98000-7f9a16c9d000 rw-p 00000000 00:00 0 7f9a16c9d000-7f9a16cb5000 r-xp 00000000 08:01 9050338 /lib/x86_64-linux-gnu/libpthread-2.15.so 7f9a16cb5000-7f9a16eb4000 ---p 00018000 08:01 9050338 /lib/x86_64-linux-gnu/libpthread-2.15.so 7f9a16eb4000-7f9a16eb5000 r--p 00017000 08:01 9050338 /lib/x86_64-linux-gnu/libpthread-2.15.so 7f9a16eb5000-7f9a16eb6000 rw-p 00018000 08:01 9050338 /lib/x86_64-linux-gnu/libpthread-2.15.so 7f9a16eb6000-7f9a16eba000 rw-p 00000000 00:00 0 7f9a16eba000-7f9a16edc000 r-xp 00000000 08:01 9050344 /lib/x86_64-linux-gnu/ld-2.15.so 7f9a170c1000-7f9a170c4000 rw-p 00000000 00:00 0 7f9a170d9000-7f9a170dc000 rw-p 00000000 00:00 0 7f9a170dc000-7f9a170dd000 r--p 00022000 08:01 9050344 /lib/x86_64-linux-gnu/ld-2.15.so 7f9a170dd000-7f9a170df000 rw-p 00023000 08:01 9050344 /lib/x86_64-linux-gnu/ld-2.15.so 7fff52f27000-7fff52f48000 rw-p 00000000 00:00 0 [stack] 7fff52fff000-7fff53000000 r-xp 00000000 00:00 0 [vdso] ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

1 0

Re: [mpich-discuss] Problems running MPICH jobs under SLURM
by Pavan Balaji 07 Jun '13

07 Jun '13

FYI, I believe this is now fixed. Please try out the latest nightly snapshot and let us know if you are still running into this issue: http://www.mpich.org/static/tarballs/nightly/master/hydra/ http://www.mpich.org/static/tarballs/nightly/master/mpich/ -- Pavan On 06/06/2013 01:39 AM, Biddiscombe, John A. wrote: > Just FYI. I am also getting the double free error when I run under slurm (mpich 3.0.4). Please don't take correspondence off list as I'm following the thread. > > I can't add anything more useful than Markus has already provided with his stack trace and logs. > > [I did find that if I configure --with-slurm and use srun instead of mpiexec , then all works, as expected, but I need mpiexec to pass env vars to processes using mpmd syntax] > > JB > > -----Original Message----- > From: discuss-bounces(a)mpich.org [mailto:[email protected]] On Behalf Of Markus Geimer > Sent: 03 June 2013 16:36 > To: Pavan Balaji > Cc: discuss(a)mpich.org > Subject: Re: [mpich-discuss] Problems running MPICH jobs under SLURM > > Pavan, > >> 1. Can you run your application processes using "ddd" or some other >> debugger to see where the double free is coming from? You might have >> to build mpich with --enable-g=dbg to get the debug symbols in. > > Here is the full stack backtrace: > > ----- 8< ----- 8< ----- 8< ----- 8< ----- 8< ----- 8< ----- > > #0 0x00007ffff6deb475 in *__GI_raise (sig=<optimized out>) > at ../nptl/sysdeps/unix/sysv/linux/raise.c:64 > #1 0x00007ffff6dee6f0 in *__GI_abort () at abort.c:92 > #2 0x00007ffff6e2652b in __libc_message (do_abort=<optimized out>, > fmt=<optimized out>) at ../sysdeps/unix/sysv/linux/libc_fatal.c:189 > #3 0x00007ffff6e2fd76 in malloc_printerr (action=3, > str=0x7ffff6f081e0 "double free or corruption (fasttop)", > ptr=<optimized out>) at malloc.c:6283 > #4 0x00007ffff6e34aac in *__GI___libc_free (mem=<optimized out>) > at malloc.c:3738 > #5 0x00007ffff7a1d5d9 in populate_ids_from_mapping ( > did_map=<synthetic pointer>, num_nodes=<synthetic pointer>, > mapping=<optimized out>, pg=<optimized out>) > at src/mpid/ch3/src/mpid_vc.c:1063 > #6 MPIDI_Populate_vc_node_ids (pg=pg@entry=0x604910, > our_pg_rank=our_pg_rank@entry=0) at src/mpid/ch3/src/mpid_vc.c:1193 > #7 0x00007ffff7a17dd6 in MPID_Init (argc=argc@entry=0x7fffffffd97c, > argv=argv@entry=0x7fffffffd970, requested=requested@entry=0, > provided=provided@entry=0x7fffffffd8e8, > has_args=has_args@entry=0x7fffffffd8e0, > has_env=has_env@entry=0x7fffffffd8e4) at > src/mpid/ch3/src/mpid_init.c:156 > #8 0x00007ffff7acdf7f in MPIR_Init_thread (argc=argc@entry=0x7fffffffd97c, > argv=argv@entry=0x7fffffffd970, required=required@entry=0, > provided=provided@entry=0x7fffffffd944) at src/mpi/init/initthread.c:431 > #9 0x00007ffff7acd90e in PMPI_Init (argc=0x7fffffffd97c, > argv=0x7fffffffd970) > at src/mpi/init/init.c:136 > #10 0x000000000040086d in main () > > ----- >8 ----- >8 ----- >8 ----- >8 ----- >8 ----- >8 ----- > >> 2. Can you send me the output with the ssh launcher as well? > > See mail sent off-list. > > Thanks, > Markus > > -- > Dr. Markus Geimer > Juelich Supercomputing Centre > Institute for Advanced Simulation > Forschungszentrum Juelich GmbH > 52425 Juelich, Germany > > Phone: +49-2461-61-1773 > Fax: +49-2461-61-6656 > E-mail: m.geimer(a)fz-juelich.de > WWW: http://www.fz-juelich.de/jsc/ > > > > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > Forschungszentrum Juelich GmbH > 52425 Juelich > Sitz der Gesellschaft: Juelich > Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498 Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher > Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender), Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt, Prof. Dr. Sebastian M. Schmidt > ------------------------------------------------------------------------------------------------ > ------------------------------------------------------------------------------------------------ > _______________________________________________ > 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] MPICH problem
by Wesley Bland 06 Jun '13

06 Jun '13

(Re-adding mpich-discuss) Sorry I can't help you more. I'm afraid I'll have to defer to Jayesh on this one he's the only one who still knows anything about Windows support. On Jun 6, 2013, at 11:17 AM, "Miller, Harry CSNR:EX" <Harry.Miller(a)gov.bc.ca> wrote: > I am at a loss as when I even ‘google’ the problem everyone writing in seems to have a similar problem but no final (fix) resolution is ever offered? > > http://trac.mpich.org/projects/mpich/ticket/1151 > http://trac.mpich.org/projects/mpich/ticket/1577 > http://trac.mpich.org/projects/mpich/ticket/1692 > http://lists.mcs.anl.gov/pipermail/mpich-discuss/2011-March/009303.html > http://lists.mcs.anl.gov/pipermail/mpich-discuss/2010-May/007293.html > http://lists.mcs.anl.gov/pipermail/mpich-discuss/2009-July/005324.html > http://lists.mcs.anl.gov/pipermail/mpich-discuss/2008-November/000032.html > http://lists.mcs.anl.gov/pipermail/mpich-discuss/2005-September/000768.html > https://groups.google.com/forum/?fromgroups#!topic/fds-smv/3nSxMLMWRvY > http://auriza.site40.net/notes/mpi/mpich2-on-windows-xp/ > > I can go on ... > > mpiexec -register ONLY works with the admin user credentials (mine). I installed MPICH as ‘admin’ as it indicated one should but it now it doesn’t work if register other regular Citrix user credentials using either wmpiexec or mpiexec. Is wpmiregister.exe the same as mpiexec.exe? mpiexec -register.? Maybe I have to remove the credentials registered with the wmpiexec.exe app. and make sure to register with mpiexec.exe using the mpiexec –register command? > > Confusing. > > Harry > > > H.J. Miller > Spatial Technology Analyst | Infrastructure Services Section > Information Management Branch (IMB) > Phone: 250-356-5217 | FAX: 250-953-3493 | E-Mail: Harry.Miller(a)gov.bc.ca > Corporate Services For The Natural Resources Sector (CSNR) > > > > > > From: Wesley Bland [mailto:[email protected]] > Sent: Wednesday, June 5, 2013 9:05 PM > To: Miller, Harry CSNR:EX > Cc: discuss(a)mpich.org > Subject: Re: [mpich-discuss] MPICH problem > > It sounds like your problem is outside of MPICH's control but just to be sure, you can run a simple MPI application and get expected output as long as you're using a regular Windows user account correct? (You'll have to forgive me if I don't know all the Windowsisms. There aren't many Windows people left on this project as we stopped officially supporting Windows on version 1.4.1p) > > Wesley > > On Jun 5, 2013, at 2:55 PM, "Miller, Harry CSNR:EX" <Harry.Miller(a)gov.bc.ca> wrote: > > Hello, > > We are having problems after having installed the MPICH2 (32-bit) along withTauDEM 5.1 32-bit Install Package on one of our Windows Server 2008 64-bit Citrix 6.5 test severs. When registering users using the wpmiregister.exe it appears that only the admin. credentials will work and NOT Citrix regular user accounts. Is there some way to allow Citrix regular users to be able to run commands that call the TauDEM applications from the server? > > For example, opening up a command prompt on the test server and typing in ... > > mpiexec -n 8 pitremove -z "W:\FOR\RSI\RSI\Projects\wburt\projects\2013\006_HSCM_Boundary\data\Raster\dem25.tif" -fel "T:\test.tif" > > requires users credentials to launch the processes (see screenshot below). Regular Citrix credentials don’t seem to be accepted whilst my admin. ones are? Also, do we add the credentials logged in to the server as ‘admin’ or do individual regular users register their credentials from the Citrix server session? Our users won’t have admin. accounts but they will all log into the same test server with the MPICH2 and TuaDEM 5.1 install ... and yet the processes ask for credentials even though the users are already logged in with their regular IDIR Citrix login creds.??? > > I registered my regular Citrix user creds. and also my admin. ones but ONLy the admin one is accepted. When I installed MPICH2 I also checked off that it be available to everyone. But we still get the Aborting: Unable to connect message??? > > <image001.jpg> > > Thank you in advance for a reply. > > > H.J. Miller > Spatial Technology Analyst | Infrastructure Services Section > Information Management Branch (IMB) > Phone: 250-356-5217 | FAX: 250-953-3493 | E-Mail: Harry.Miller(a)gov.bc.ca > Corporate Services For The Natural Resources Sector (CSNR) > > > > > From: David Tarboton [mailto:[email protected]] > Sent: Tuesday, June 4, 2013 7:23 PM > To: Miller, Harry CSNR:EX > Subject: Re: FW: TauDEM problem > > Harry, > > I do not understand MPICH2 credentials very well so I do not know what to say. I have successfully run on Windows 2008 as a Windows user but not with Citrix. You might want to make sure MPICH2 was installed for all users. Also see http://nick-goodman.blogspot.com/2012/02/using-mpich-from-ms-visual-studio-… some suggestions that may help. Also you might try mpiexec -register with the admin user. If it is running as admin maybe this will work for other users without having to give them admin credentials. Also is wpmiregister.exe the same as mpiexec -register. Sometimes there are different versions of MPI on the same machine from different software and if the wrong one runs it does not work. It is frustrating to me to have to have TauDEM depend on this software that is so hard to install and get configured right. > > Good luck. > > Dave > > On 6/4/2013 5:06 PM, Miller, Harry CSNR:EX wrote: > Hello, > > I have installed the MPICH2 (32-bit) and TauDEM 5.1 32-bit Install Package on one of our Windows Server 2008 64-bit Citrix 6.5 test severs. However, when registering users using the wpmiregister.exe it appears that only the admin. credentials will work and NOT Citrix regular user accounts. Is there some way to allow Citrix regular users to be able to run commands that call the TauDEM applications from the server? > > For example, opening up a command prompt on the test server and typing in ... > > mpiexec -n 8 pitremove -z "W:\FOR\RSI\RSI\Projects\wburt\projects\2013\006_HSCM_Boundary\data\Raster\dem25.tif" -fel "T:\test.tif" > > requires users credentials to launch the processes (see screenshot below). Regular Citrix credentials don’t seem to be accepted whilst my admin. ones are? Our users won’t have admin. accounts but they will all log into the same test server with the MPICH2 and TuaDEM 5.1 install ... and yet the processes ask for credentials even though the users are already logged in with their regular IDIR Citrix login creds.??? > > I registered my regular Citrix user creds. and also my admin. ones. > > Is something still missing here?? > > Thanks for a reply. > > Harry > > > H.J. Miller > Spatial Technology Analyst | Infrastructure Services Section > Information Management Branch (IMB) > Phone: 250-356-5217 | FAX: 250-953-3493 | E-Mail: Harry.Miller(a)gov.bc.ca > Corporate Services For The Natural Resources Sector (CSNR) > Government of British Columbia > > From: Miller, Harry CSNR:EX > Sent: Tuesday, June 4, 2013 3:20 PM > To: Burt, William FLNR:EX > Subject: RE: TauDEM fix > > Will, > > Looks like the creds have to be admin ones. Do you have an admin. account? My admin. creds work but not my regular IDIR creds. > > <ATT00001.png> > > Harry > > > H.J. Miller > Spatial Technology Analyst | Infrastructure Services Section > Information Management Branch (IMB) > Phone: 250-356-5217 | FAX: 250-953-3493 | E-Mail: Harry.Miller(a)gov.bc.ca > Corporate Services For The Natural Resources Sector (CSNR) > > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss

1 0