February 2017 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] "ffmpeg" error
by Halim Amer 28 Feb '17

28 Feb '17

This is more of a LAMMPS question than an MPICH question. I suggest you to contact the LAMMPS folks to get advice. Also, we do not support MPICH on windows (including Cygwin and MinGW). You will have better luck with Microsoft MPI (https://msdn.microsoft.com/en-us/library/bb524831(v=vs.85).aspx) Halim www.mcs.anl.gov/~aamer On 2/27/17 9:33 PM, Rouhollah Mirzaamiri wrote: > Dear Users and developers, > > I am using MPICH2.1.4.1 on WIN 10 64X for runnig LAMMPS MPI. > When I am ruing a script including "making movie file related command", > this error occurred: > > setti"ffmpeg" is not recognized as an internal or external command, > operable program or bath " > > ** this error doesn't happen in LAMMPS SERIAL run** > I also installed new version of FFMPEG and set the "path" in windows. > What should I do > Regards, > Rouhollah > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

"ffmpeg" error
by Rouhollah Mirzaamiri 27 Feb '17

27 Feb '17

Dear Users and developers, I am using MPICH2.1.4.1 on WIN 10 64X for runnig LAMMPS MPI. When I am ruing a script including "making movie file related command", this error occurred: setti"ffmpeg" is not recognized as an internal or external command, operable program or bath " ** this error doesn't happen in LAMMPS SERIAL run** I also installed new version of FFMPEG and set the "path" in windows. What should I do Regards, Rouhollah _______________________________________________ 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] Does Asynchronous Allgather work in background without any effects on computing cores?
by Richard Warren 21 Feb '17

21 Feb '17

Hi Sunwoo, In general I think that you should be aware that the asynchronous operations in MPI are there to take advantage of RDMA capable networks. With most simple TCP/IP based networks, the interfaces are passive and thus data movement between peers can only be made by actively calling MPI functionality. You’ve already noticed that messages will be advanced by calling MPI_Wait. The general point to be made is that on non-RDMA capable networks, an independent thread or your main program can call MPI_Wait or other MPI calls such as MPI_Test to force the library to actively move data that has been queued by an asynchronous operation. In summary, the answer to your overall question is at best: a qualified yes (depending on the network capabilities of your cluster or if you employ multithreading). I hope that explanation helps… Richard A. Warren (HDFgroup) From: Sunwoo Lee <sunwoolee1.2014(a)u.northwestern.edu> Reply-To: "discuss(a)mpich.org" <discuss(a)mpich.org> Date: Tuesday, February 21, 2017 at 12:19 PM To: "discuss(a)mpich.org" <discuss(a)mpich.org> Subject: [mpich-discuss] Does Asynchronous Allgather work in background without any effects on computing cores? Hi, I would like to implement a software that communication and computation are performed simultaneously. That is, while communication for the current data is done, the next data is computed overlapping with the communication. I expected asynchronous MPI such as Iallgather() would make the communication and computation overlapped. But it seems like the communication is not started until I call MPI_Wait(). With a simple toy application, I compared the two cases. MPI_IAllgather + MPI_Wait() versus MPI_Allgather. The issue is that MPI_Wait() takes almost same time with MPI_Allgather. I can guess the communication is just started when I call MPI_Wait. My question is, could asynchronous MPI functions work background so that computing cores do other works while the communication is performed? Thank you. Best, Sunwoo Lee _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Does Asynchronous Allgather work in background without any effects on computing cores?
by Sunwoo Lee 21 Feb '17

21 Feb '17

Hi, I would like to implement a software that communication and computation are performed simultaneously. That is, while communication for the current data is done, the next data is computed overlapping with the communication. I expected asynchronous MPI such as Iallgather() would make the communication and computation overlapped. But it seems like the communication is not started until I call MPI_Wait(). With a simple toy application, I compared the two cases. MPI_IAllgather + MPI_Wait() versus MPI_Allgather. The issue is that MPI_Wait() takes almost same time with MPI_Allgather. I can guess the communication is just started when I call MPI_Wait. My question is, could asynchronous MPI functions work background so that computing cores do other works while the communication is performed? Thank you. Best, Sunwoo Lee _______________________________________________ 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] Waiting for spawned processes to call MPI_Finalize?
by Bland, Wesley 17 Feb '17

17 Feb '17

It's a minor modification to add the MPI_Comm_disconnect, but yes, it's a modification. I'm not sure of another easy way while staying inside MPI. You could probably do some sort of tricks with some wrapper scripts. On Feb 17, 2017, at 8:45 AM, Dorier, Matthieu <mdorier(a)anl.gov<mailto:[email protected]>> wrote: Thanks! There is no way to do this with modifying the child application's code, then, right? Mattthieu ________________________________ From: Bland, Wesley [wesley.bland(a)intel.com<mailto:[email protected]>] Sent: Friday, February 17, 2017 8:39 AM To: <discuss(a)mpich.org<mailto:[email protected]>> Subject: Re: [mpich-discuss] Waiting for spawned processes to call MPI_Finalize? You could use MPI_Comm_disconnect. The description is in the 3.1 standard p. 398: This function waits for all pending communication on comm to complete internally, deallocates the communicator object, and sets the handle to MPI_COMM_NULL. It is a collective operation. If you disconnect the communicator from MPI_Comm_get_parent before you call MPI_Finalize and the spawning processes do the same, you should synchronize around the disconnect. On Feb 17, 2017, at 7:58 AM, Dorier, Matthieu <mdorier(a)anl.gov<mailto:[email protected]>> wrote: Hi, If I have an application that calls MPI_Comm_spawn, is there a way to make the parent "wait" for the child application to have called MPI_Finalize (or terminated), at some point? The rational would be that MPI_Comm_spawn is sort of an MPI equivalent of "fork/execv", but I don't see an equivalent of "wait", in the standard. My feeling is that once a child application is spawned, it is supposed to stay alive until the parent calls MPI_Finalize as well. Am I mistaken? Thanks, Matthieu _______________________________________________ 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 _______________________________________________ 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] Waiting for spawned processes to call MPI_Finalize?
by Dorier, Matthieu 17 Feb '17

17 Feb '17

Thanks! There is no way to do this with modifying the child application's code, then, right? Mattthieu ________________________________ From: Bland, Wesley [wesley.bland(a)intel.com] Sent: Friday, February 17, 2017 8:39 AM To: <discuss(a)mpich.org> Subject: Re: [mpich-discuss] Waiting for spawned processes to call MPI_Finalize? You could use MPI_Comm_disconnect. The description is in the 3.1 standard p. 398: This function waits for all pending communication on comm to complete internally, deallocates the communicator object, and sets the handle to MPI_COMM_NULL. It is a collective operation. If you disconnect the communicator from MPI_Comm_get_parent before you call MPI_Finalize and the spawning processes do the same, you should synchronize around the disconnect. On Feb 17, 2017, at 7:58 AM, Dorier, Matthieu <mdorier(a)anl.gov<mailto:[email protected]>> wrote: Hi, If I have an application that calls MPI_Comm_spawn, is there a way to make the parent "wait" for the child application to have called MPI_Finalize (or terminated), at some point? The rational would be that MPI_Comm_spawn is sort of an MPI equivalent of "fork/execv", but I don't see an equivalent of "wait", in the standard. My feeling is that once a child application is spawned, it is supposed to stay alive until the parent calls MPI_Finalize as well. Am I mistaken? Thanks, Matthieu _______________________________________________ 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 To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] Waiting for spawned processes to call MPI_Finalize?
by Bland, Wesley 17 Feb '17

17 Feb '17

You could use MPI_Comm_disconnect. The description is in the 3.1 standard p. 398: This function waits for all pending communication on comm to complete internally, deallocates the communicator object, and sets the handle to MPI_COMM_NULL. It is a collective operation. If you disconnect the communicator from MPI_Comm_get_parent before you call MPI_Finalize and the spawning processes do the same, you should synchronize around the disconnect. On Feb 17, 2017, at 7:58 AM, Dorier, Matthieu <mdorier(a)anl.gov<mailto:[email protected]>> wrote: Hi, If I have an application that calls MPI_Comm_spawn, is there a way to make the parent "wait" for the child application to have called MPI_Finalize (or terminated), at some point? The rational would be that MPI_Comm_spawn is sort of an MPI equivalent of "fork/execv", but I don't see an equivalent of "wait", in the standard. My feeling is that once a child application is spawned, it is supposed to stay alive until the parent calls MPI_Finalize as well. Am I mistaken? Thanks, Matthieu _______________________________________________ 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 To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Waiting for spawned processes to call MPI_Finalize?
by Dorier, Matthieu 17 Feb '17

17 Feb '17

Hi, If I have an application that calls MPI_Comm_spawn, is there a way to make the parent "wait" for the child application to have called MPI_Finalize (or terminated), at some point? The rational would be that MPI_Comm_spawn is sort of an MPI equivalent of "fork/execv", but I don't see an equivalent of "wait", in the standard. My feeling is that once a child application is spawned, it is supposed to stay alive until the parent calls MPI_Finalize as well. Am I mistaken? Thanks, Matthieu _______________________________________________ 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] MPI error
by Seth Munholland 15 Feb '17

15 Feb '17

I went and purged mpich and mpiexec/mpirun was still found from 'which' along with mpiexec.openmpi/mpirun.openmpi. These are part of openmpi-common and after purging that and reinstalling mpich it is back to working order. Not sure what installed the openmpi-common package, but that fixed it for me. Thanks for your help! Seth Munholland, B.Sc. Department of Biological Sciences Rm. 304 Biology Building University of Windsor 401 Sunset Ave. N9B 3P4 T: (519) 253-3000 Ext: 4755 On Wed, Feb 15, 2017 at 12:36 PM, Halim Amer <halim.amer(a)acm.org> wrote: > You can use `which mpiexec` to figure out which binary you are using. Use > `ldd <your binary>` to locate the MPI library you are linking to. Use > `apt-file` to find which package(s) installed those files. > > > Which it properly defined in /etc/hosts. It compiled and executed > > without error and returned all the processes I had on each node. I went > > on to install some programs on the NFS drive and when I tried to run it > > I get the following error > > If your MPI program was working before you installed those programs, you > could try uninstalling them. It could be that one of those programs have a > dependency on Open MPI, so the problem might remain. In this case, you > still need to locate the packages that installed the MPI binaries and > libraries as shown above and uninstalled them. > > Halim > www.mcs.anl.gov/~aamer > > > On 2/15/17 10:26 AM, Seth Munholland wrote: > >> That's very strange as I never installed OpenMPI. I used apt-get to >> install MPICH and have avoided OpenMPI to try and not get this issue. I >> thought it would be an easy fix of uninstalling and reinstalling via >> apt-get, but I can't seem to actually remove this OpenMPI version. Would >> a >> source compile write over the apt-get installed version? >> >> Seth Munholland, B.Sc. >> Department of Biological Sciences >> Rm. 304 Biology Building >> University of Windsor >> 401 Sunset Ave. N9B 3P4 >> T: (519) 253-3000 Ext: 4755 >> >> On Wed, Feb 8, 2017 at 11:50 AM, Halim Amer <halim.amer(a)acm.org> wrote: >> >> Hi, >>> >>> It seems you are using Open MPI. You can whether contact the Open MPI >>> team >>> to look into your problem, or clean your environment (both binaries and >>> libraries) if you want to use MPICH to make sure you are truly using >>> MPICH >>> when building and running your program. >>> >>> Halim >>> www.mcs.anl.gov/~aamer >>> >>> >>> On 2/8/17 10:18 AM, Seth Munholland wrote: >>> >>> Hello everyone, >>>> >>>> I have been configuring a new ubuntu cluster and wanted it to run MPI >>>> programs. I got mpich configured and compiled then ran the following as >>>> a test: >>>> >>>> #include <stdio.h> >>>> #include <mpi.h> >>>> >>>> int main (int argc, char** argv) { >>>> int rank = 0, size = 0, nameLen = 0; >>>> char procName[MPI_MAX_PROCESSOR_NAME]; >>>> >>>> MPI_Init (&argc, &argv); >>>> MPI_Comm_size (MPI_COMM_WORLD, &size); >>>> MPI_Comm_rank (MPI_COMM_WORLD, &rank); >>>> MPI_Get_processor_name (procName, &nameLen); >>>> >>>> printf ("Hello from processor %s, rank %d of %d\n", procName, rank, >>>> size); >>>> >>>> MPI_Finalize(); >>>> return 0; >>>> } >>>> >>>> using the commands: >>>> mpicc mpi_hello.c -o mpi_hello >>>> mpiexec -mahcinefile machinefile mpi_hello >>>> >>>> my machienfile looks like this: >>>> beanblade4:24 >>>> beanblade3:24 >>>> beanblade2:24 >>>> beanblade:24 >>>> >>>> Which it properly defined in /etc/hosts. It compiled and executed >>>> without error and returned all the processes I had on each node. I went >>>> on to install some programs on the NFS drive and when I tried to run it >>>> I get the following error >>>> >>>> bash: orted: command not found >>>> ------------------------------------------------------------ >>>> -------------- >>>> ORTE was unable to reliably start one or more daemons. >>>> This usually is caused by: >>>> >>>> * not finding the required libraries and/or binaries on >>>> one or more nodes. Please check your PATH and LD_LIBRARY_PATH >>>> settings, or configure OMPI with --enable-orterun-prefix-by-default >>>> >>>> * lack of authority to execute on one or more specified nodes. >>>> Please verify your allocation and authorities. >>>> >>>> * the inability to write startup files into /tmp >>>> (--tmpdir/orte_tmpdir_base). >>>> Please check with your sys admin to determine the correct location to >>>> use. >>>> >>>> * compilation of the orted with dynamic libraries when static are >>>> required >>>> (e.g., on Cray). Please check your configure cmd line and consider >>>> using >>>> one of the contrib/platform definitions for your system type. >>>> >>>> * an inability to create a connection back to mpirun due to a >>>> lack of common network interfaces and/or no route found between >>>> them. Please check network connectivity (including firewalls >>>> and network routing requirements). >>>> ------------------------------------------------------------ >>>> -------------- >>>> >>>> This error now gets returned when I try to run the mpi_hello program I >>>> used to test my mpi implementation. if I drop the machinefile tag from >>>> my mpiexec command I get >>>> >>>> mpiexec ./mpi_hello >>>> ------------------------------------------------------------ >>>> -------------- >>>> [[14894,1],17]: A high-performance Open MPI point-to-point messaging >>>> module >>>> was unable to find any relevant network interfaces: >>>> >>>> Module: OpenFabrics (openib) >>>> Host: beanblade >>>> >>>> Another transport will be used instead, although this may result in >>>> lower performance. >>>> ------------------------------------------------------------ >>>> -------------- >>>> Hello from processor beanblade, rank 18 of 24 >>>> Hello from processor beanblade, rank 0 of 24 >>>> Hello from processor beanblade, rank 2 of 24 >>>> Hello from processor beanblade, rank 4 of 24 >>>> Hello from processor beanblade, rank 6 of 24 >>>> Hello from processor beanblade, rank 7 of 24 >>>> Hello from processor beanblade, rank 3 of 24 >>>> Hello from processor beanblade, rank 1 of 24 >>>> Hello from processor beanblade, rank 5 of 24 >>>> Hello from processor beanblade, rank 8 of 24 >>>> Hello from processor beanblade, rank 12 of 24 >>>> Hello from processor beanblade, rank 13 of 24 >>>> Hello from processor beanblade, rank 11 of 24 >>>> Hello from processor beanblade, rank 9 of 24 >>>> Hello from processor beanblade, rank 10 of 24 >>>> Hello from processor beanblade, rank 14 of 24 >>>> Hello from processor beanblade, rank 15 of 24 >>>> Hello from processor beanblade, rank 16 of 24 >>>> Hello from processor beanblade, rank 17 of 24 >>>> Hello from processor beanblade, rank 19 of 24 >>>> Hello from processor beanblade, rank 20 of 24 >>>> Hello from processor beanblade, rank 21 of 24 >>>> Hello from processor beanblade, rank 22 of 24 >>>> Hello from processor beanblade, rank 23 of 24 >>>> [beanblade:13849] 23 more processes have sent help message >>>> help-mpi-btl-base.txt / btl:no-nics >>>> [beanblade:13849] Set MCA parameter "orte_base_help_aggregate" to 0 to >>>> see all help / error messages >>>> >>>> I've been trying to figure it out on the forums and I think it's >>>> somethign to do with my bashrc file (I have a few exports for >>>> environmental variables), but removing them didn't fix the problem. >>>> What did I break? Where do I look to fix it? >>>> >>>> Seth Munholland, B.Sc. >>>> Department of Biological Sciences >>>> Rm. 304 Biology Building >>>> University of Windsor >>>> 401 Sunset Ave. N9B 3P4 >>>> T: (519) 253-3000 Ext: 4755 >>>> >>>> >>>> _______________________________________________ >>>> discuss mailing list discuss(a)mpich.org >>>> To manage subscription options or unsubscribe: >>>> https://lists.mpich.org/mailman/listinfo/discuss >>>> >>>> _______________________________________________ >>>> >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >>> >> >> >> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> >> _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Re: [mpich-discuss] MPI error
by Halim Amer 15 Feb '17

15 Feb '17

You can use `which mpiexec` to figure out which binary you are using. Use `ldd <your binary>` to locate the MPI library you are linking to. Use `apt-file` to find which package(s) installed those files. > Which it properly defined in /etc/hosts. It compiled and executed > without error and returned all the processes I had on each node. I went > on to install some programs on the NFS drive and when I tried to run it > I get the following error If your MPI program was working before you installed those programs, you could try uninstalling them. It could be that one of those programs have a dependency on Open MPI, so the problem might remain. In this case, you still need to locate the packages that installed the MPI binaries and libraries as shown above and uninstalled them. Halim www.mcs.anl.gov/~aamer On 2/15/17 10:26 AM, Seth Munholland wrote: > That's very strange as I never installed OpenMPI. I used apt-get to > install MPICH and have avoided OpenMPI to try and not get this issue. I > thought it would be an easy fix of uninstalling and reinstalling via > apt-get, but I can't seem to actually remove this OpenMPI version. Would a > source compile write over the apt-get installed version? > > Seth Munholland, B.Sc. > Department of Biological Sciences > Rm. 304 Biology Building > University of Windsor > 401 Sunset Ave. N9B 3P4 > T: (519) 253-3000 Ext: 4755 > > On Wed, Feb 8, 2017 at 11:50 AM, Halim Amer <halim.amer(a)acm.org> wrote: > >> Hi, >> >> It seems you are using Open MPI. You can whether contact the Open MPI team >> to look into your problem, or clean your environment (both binaries and >> libraries) if you want to use MPICH to make sure you are truly using MPICH >> when building and running your program. >> >> Halim >> www.mcs.anl.gov/~aamer >> >> >> On 2/8/17 10:18 AM, Seth Munholland wrote: >> >>> Hello everyone, >>> >>> I have been configuring a new ubuntu cluster and wanted it to run MPI >>> programs. I got mpich configured and compiled then ran the following as >>> a test: >>> >>> #include <stdio.h> >>> #include <mpi.h> >>> >>> int main (int argc, char** argv) { >>> int rank = 0, size = 0, nameLen = 0; >>> char procName[MPI_MAX_PROCESSOR_NAME]; >>> >>> MPI_Init (&argc, &argv); >>> MPI_Comm_size (MPI_COMM_WORLD, &size); >>> MPI_Comm_rank (MPI_COMM_WORLD, &rank); >>> MPI_Get_processor_name (procName, &nameLen); >>> >>> printf ("Hello from processor %s, rank %d of %d\n", procName, rank, >>> size); >>> >>> MPI_Finalize(); >>> return 0; >>> } >>> >>> using the commands: >>> mpicc mpi_hello.c -o mpi_hello >>> mpiexec -mahcinefile machinefile mpi_hello >>> >>> my machienfile looks like this: >>> beanblade4:24 >>> beanblade3:24 >>> beanblade2:24 >>> beanblade:24 >>> >>> Which it properly defined in /etc/hosts. It compiled and executed >>> without error and returned all the processes I had on each node. I went >>> on to install some programs on the NFS drive and when I tried to run it >>> I get the following error >>> >>> bash: orted: command not found >>> ------------------------------------------------------------ >>> -------------- >>> ORTE was unable to reliably start one or more daemons. >>> This usually is caused by: >>> >>> * not finding the required libraries and/or binaries on >>> one or more nodes. Please check your PATH and LD_LIBRARY_PATH >>> settings, or configure OMPI with --enable-orterun-prefix-by-default >>> >>> * lack of authority to execute on one or more specified nodes. >>> Please verify your allocation and authorities. >>> >>> * the inability to write startup files into /tmp >>> (--tmpdir/orte_tmpdir_base). >>> Please check with your sys admin to determine the correct location to >>> use. >>> >>> * compilation of the orted with dynamic libraries when static are >>> required >>> (e.g., on Cray). Please check your configure cmd line and consider using >>> one of the contrib/platform definitions for your system type. >>> >>> * an inability to create a connection back to mpirun due to a >>> lack of common network interfaces and/or no route found between >>> them. Please check network connectivity (including firewalls >>> and network routing requirements). >>> ------------------------------------------------------------ >>> -------------- >>> >>> This error now gets returned when I try to run the mpi_hello program I >>> used to test my mpi implementation. if I drop the machinefile tag from >>> my mpiexec command I get >>> >>> mpiexec ./mpi_hello >>> ------------------------------------------------------------ >>> -------------- >>> [[14894,1],17]: A high-performance Open MPI point-to-point messaging >>> module >>> was unable to find any relevant network interfaces: >>> >>> Module: OpenFabrics (openib) >>> Host: beanblade >>> >>> Another transport will be used instead, although this may result in >>> lower performance. >>> ------------------------------------------------------------ >>> -------------- >>> Hello from processor beanblade, rank 18 of 24 >>> Hello from processor beanblade, rank 0 of 24 >>> Hello from processor beanblade, rank 2 of 24 >>> Hello from processor beanblade, rank 4 of 24 >>> Hello from processor beanblade, rank 6 of 24 >>> Hello from processor beanblade, rank 7 of 24 >>> Hello from processor beanblade, rank 3 of 24 >>> Hello from processor beanblade, rank 1 of 24 >>> Hello from processor beanblade, rank 5 of 24 >>> Hello from processor beanblade, rank 8 of 24 >>> Hello from processor beanblade, rank 12 of 24 >>> Hello from processor beanblade, rank 13 of 24 >>> Hello from processor beanblade, rank 11 of 24 >>> Hello from processor beanblade, rank 9 of 24 >>> Hello from processor beanblade, rank 10 of 24 >>> Hello from processor beanblade, rank 14 of 24 >>> Hello from processor beanblade, rank 15 of 24 >>> Hello from processor beanblade, rank 16 of 24 >>> Hello from processor beanblade, rank 17 of 24 >>> Hello from processor beanblade, rank 19 of 24 >>> Hello from processor beanblade, rank 20 of 24 >>> Hello from processor beanblade, rank 21 of 24 >>> Hello from processor beanblade, rank 22 of 24 >>> Hello from processor beanblade, rank 23 of 24 >>> [beanblade:13849] 23 more processes have sent help message >>> help-mpi-btl-base.txt / btl:no-nics >>> [beanblade:13849] Set MCA parameter "orte_base_help_aggregate" to 0 to >>> see all help / error messages >>> >>> I've been trying to figure it out on the forums and I think it's >>> somethign to do with my bashrc file (I have a few exports for >>> environmental variables), but removing them didn't fix the problem. >>> What did I break? Where do I look to fix it? >>> >>> Seth Munholland, B.Sc. >>> Department of Biological Sciences >>> Rm. 304 Biology Building >>> University of Windsor >>> 401 Sunset Ave. N9B 3P4 >>> T: (519) 253-3000 Ext: 4755 >>> >>> >>> _______________________________________________ >>> discuss mailing list discuss(a)mpich.org >>> To manage subscription options or unsubscribe: >>> https://lists.mpich.org/mailman/listinfo/discuss >>> >>> _______________________________________________ >> discuss mailing list discuss(a)mpich.org >> To manage subscription options or unsubscribe: >> https://lists.mpich.org/mailman/listinfo/discuss >> > > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > _______________________________________________ discuss mailing list discuss(a)mpich.org To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0