January 2021 - discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] Question about non-blocking MPI - 3
by Joachim Protze 07 Jan '21

07 Jan '21

Hi Viet, If MPICH_ASYNC_PROGRESS=1 is necessary for your application to terminate, i.e., you see a deadlock without this flag, the applications has a correctness/portability issue. This env variable should only have a possible impact to performance (better compute/communication overlap) but should not be necessary to avoid deadlock. You can compare this to the classical send-send deadlock (example 3.9 in the standard), where the application relies on buffering / eager communication, but all send suddenly block. The portable fix for the application is not to increase the eager-limit, but to fix the communication pattern. Best Joachim Am 07.01.21 um 13:08 schrieb viet via discuss: > Dear Hui Zhou, > > Thank you for your response to this thread. > Could you give me some references on this issue? > > It seems that the below environment setting is necessary. > > MPICH_ASYNC_PROGRESS=1 > > Thank you for anything you can provide. > Best, Viet. > > > > On Tue, Jan 5, 2021 at 5:59 AM Zhou, Hui <zhouh(a)anl.gov> wrote: > >> You don’t need any special settings to use non-blocking MPI collectives in >> MPICH. >> >> >> >> -- >> Hui Zhou >> >> >> >> >> >> *From: *viet via discuss <discuss(a)mpich.org> >> *Date: *Friday, December 4, 2020 at 7:12 AM >> *To: *discuss(a)mpich.org <discuss(a)mpich.org> >> *Cc: *teivml(a)gmail.com <teivml(a)gmail.com> >> *Subject: *[mpich-discuss] Question about non-blocking MPI - 3 >> >> Hello everyone, >> >> What is the environment setting for the use of non-blocking MPI-3 * >> collectives in mpich3.3? >> >> In Intel MPI, the setting is as follows >> >> $ export I_MPI_ASYNC_PROGRESS=1 >> $ export I_MPI_ASYNC_PROGRESS_PIN=<CPU list> >> >> Is there an equivalent setting in mpich3.3? >> Thank you, >> Viet. >> > > > _______________________________________________ > discuss mailing list discuss(a)mpich.org > To manage subscription options or unsubscribe: > https://lists.mpich.org/mailman/listinfo/discuss > -- Dipl.-Inf. Joachim Protze IT Center Group: High Performance Computing Division: Computational Science and Engineering RWTH Aachen University Seffenter Weg 23 D 52074 Aachen (Germany) Tel: +49 241 80- 24765 Fax: +49 241 80-624765 protze(a)itc.rwth-aachen.de www.itc.rwth-aachen.de

1 0

Re: [mpich-discuss] Question about non-blocking MPI - 3
by teivml＠gmail.com 07 Jan '21

07 Jan '21

Dear Hui Zhou, Thank you for your response to this thread. Could you give me some references on this issue? It seems that the below environment setting is necessary. MPICH_ASYNC_PROGRESS=1 Thank you for anything you can provide. Best, Viet. On Tue, Jan 5, 2021 at 5:59 AM Zhou, Hui <zhouh(a)anl.gov> wrote: > You don’t need any special settings to use non-blocking MPI collectives in > MPICH. > > > > -- > Hui Zhou > > > > > > *From: *viet via discuss <discuss(a)mpich.org> > *Date: *Friday, December 4, 2020 at 7:12 AM > *To: *discuss(a)mpich.org <discuss(a)mpich.org> > *Cc: *teivml(a)gmail.com <teivml(a)gmail.com> > *Subject: *[mpich-discuss] Question about non-blocking MPI - 3 > > Hello everyone, > > What is the environment setting for the use of non-blocking MPI-3 * > collectives in mpich3.3? > > In Intel MPI, the setting is as follows > > $ export I_MPI_ASYNC_PROGRESS=1 > $ export I_MPI_ASYNC_PROGRESS_PIN=<CPU list> > > Is there an equivalent setting in mpich3.3? > Thank you, > Viet. >

1 0

Re: [mpich-discuss] Change in SOVERSION of mpich 3.4 ?
by Raffenetti, Kenneth J. 06 Jan '21

06 Jan '21

Hi, We did not bump the major version because MPIX_Mutex interfaces were "experimental" in nature. Our position is that we update the ABI version based on official MPI standard functionality only. Ken On 1/6/21, 3:55 AM, "Alastair McKinstry via discuss" <discuss(a)mpich.org> wrote: Dear MPICH developers, I see that MPICH 3.4 has been released - Happy New Year and congratulations to all involved. I'm one of the Debian Maintainers of MPICH, and have a question though : should the SOMAJOR version not have been increased? From the CHANGES log, the following look concerning: # Change the signature of MPID_Init to include requested and provided thread levels. # Remove support for logical reduction operations on floating point types. # Remove MPIX_Mutex interfaces. Typically when functionality is removed from a library, or signatures change, the major version is incremented (the minor version can be for additions, such as the other functionality added. Are these changes purely internal to MPICH, or has the ABI changed ? This matters to the distributions such as Debian because we ship the shared libs based on SOVERSION; ie the binary package "libmpich12" currently contains libmpich.so.12.18 and libmpich.so.12 , and if mpich 3.4 is packaged as-is, will contain libmpich.so.12.1.9 (ansd symlink libmpich.so.12) and it is necessary for applications to be able to use this as a drop-in replacement. On seeing these changes in the release logs, I had been anticipating that the next version would be libmpich13.0.0 (or similar), shipped in "libmpich13". This enables upgrades; both libmpich12 and libmpich13 can co-exist. Can you confirm whether the ABI changes, and this is a drop-in replacement ? Regards Alastair McKinstry -- Alastair McKinstry, <alastair(a)sceal.ie>, <mckinstry(a)debian.org>, https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered. _______________________________________________ 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] [discuss-mpich]Error while using mpirun
by Zhou, Hui 06 Jan '21

06 Jan '21

Sorry, I just membered now that there is a bug in 3.3.2 which we fixed in https://github.com/pmodels/mpich/pull/4320/. If you can upgrade your mpich to recent releases, such as 3.4, https://www.mpich.org/downloads/, it should fix the issue. -- Hui Zhou From: Hirakjyoti Sarma via discuss <discuss(a)mpich.org> Date: Tuesday, January 5, 2021 at 11:21 PM To: discuss(a)mpich.org <discuss(a)mpich.org> Cc: Hirakjyoti Sarma <herockx1995(a)gmail.com> Subject: Re: [mpich-discuss] [discuss-mpich]Error while using mpirun actually the hostname hirakjyoti-HP-dx2480-MT-KL969AV was already there in the /etc/hosts file : 127.0.1.1 hirakjyoti-HP-dx2480-MT-KL969AV On Tue, 5 Jan 2021 at 05:37, Tony Curtis via discuss <discuss(a)mpich.org<mailto:[email protected]>> wrote: On Jan 4, 2021, at 11:59 AM, Hirakjyoti Sarma via discuss <discuss(a)mpich.org<mailto:[email protected]>> wrote: Dear all, I get the following error while running LAMMPS on ubuntu without an internet connection. Invalid error code (-2) (error ring index 127 invalid) Invalid error code (-2) (error ring index 127 invalid) INTERNAL ERROR: invalid error code fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373 Fatal error in PMPI_Init: Other MPI error, error stack: MPIR_Init_thread(586)..............: MPID_Init(224).....................: channel initialization failed MPIDI_CH3_Init(105)................: MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0) But if the PC is connected to internet LAMMPS successfully run. How can i solve the problem? This looks like a local hostname resolution issue. Maybe you could just add your hostname (presumably “hirakjyoti-……”) to the localhost entry in /etc/hosts and then when offline you’d resolve over loopback? Assuming it’s a single machine. tony _______________________________________________ discuss mailing list discuss(a)mpich.org<mailto:[email protected]> To manage subscription options or unsubscribe: https://lists.mpich.org/mailman/listinfo/discuss

1 0

Change in SOVERSION of mpich 3.4 ?
by Alastair McKinstry 06 Jan '21

06 Jan '21

Dear MPICH developers, I see that MPICH 3.4 has been released - Happy New Year and congratulations to all involved. I'm one of the Debian Maintainers of MPICH, and have a question though : should the SOMAJOR version not have been increased? From the CHANGES log, the following look concerning: # Change the signature of MPID_Init to include requested and provided thread levels. # Remove support for logical reduction operations on floating point types. # Remove MPIX_Mutex interfaces. Typically when functionality is removed from a library, or signatures change, the major version is incremented (the minor version can be for additions, such as the other functionality added. Are these changes purely internal to MPICH, or has the ABI changed ? This matters to the distributions such as Debian because we ship the shared libs based on SOVERSION; ie the binary package "libmpich12" currently contains libmpich.so.12.18 and libmpich.so.12 , and if mpich 3.4 is packaged as-is, will contain libmpich.so.12.1.9 (ansd symlink libmpich.so.12) and it is necessary for applications to be able to use this as a drop-in replacement. On seeing these changes in the release logs, I had been anticipating that the next version would be libmpich13.0.0 (or similar), shipped in "libmpich13". This enables upgrades; both libmpich12 and libmpich13 can co-exist. Can you confirm whether the ABI changes, and this is a drop-in replacement ? Regards Alastair McKinstry -- Alastair McKinstry, <alastair(a)sceal.ie>, <mckinstry(a)debian.org>, https://diaspora.sceal.ie/u/amckinstry Misentropy: doubting that the Universe is becoming more disordered.

1 0

Re: [mpich-discuss] [discuss-mpich]Error while using mpirun
by Hirakjyoti Sarma 05 Jan '21

05 Jan '21

actually the hostname *hirakjyoti-HP-dx2480-MT-KL969AV *was already there in the /etc/hosts file : 127.0.1.1 hirakjyoti-HP-dx2480-MT-KL969AV On Tue, 5 Jan 2021 at 05:37, Tony Curtis via discuss <discuss(a)mpich.org> wrote: > > > On Jan 4, 2021, at 11:59 AM, Hirakjyoti Sarma via discuss < > discuss(a)mpich.org> wrote: > > > Dear all, > I get the following error while running LAMMPS on ubuntu *without an > internet connection.* > > > > > > > > > > > > *Invalid error code (-2) (error ring index 127 invalid)Invalid error code > (-2) (error ring index 127 invalid)INTERNAL ERROR: invalid error code > fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373Fatal error in > PMPI_Init: Other MPI error, error > stack:MPIR_Init_thread(586)..............: MPID_Init(224).....................: > channel initialization > failedMPIDI_CH3_Init(105)................: MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: > gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0)* > > But if the PC is connected to internet LAMMPS successfully run. > How can i solve the problem? > > > This looks like a local hostname resolution issue. Maybe you could just > add your hostname (presumably “*hirakjyoti-……”)* to the localhost entry > in /etc/hosts and then when offline you’d resolve over loopback? Assuming > it’s a single machine. > > tony > > _______________________________________________ > 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] [discuss-mpich]Error while using mpirun
by Hirakjyoti Sarma 05 Jan '21

05 Jan '21

I used *mpiexec -host <hostname> -n 2 /path/to/executable -in in.script * *But the following error shows up:* I *nvalid error code (-2) (error ring index 127 invalid)INTERNAL ERROR: invalid error code fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373Fatal error in PMPI_Init: Other MPI error, error stack:MPIR_Init_thread(586)..............: MPID_Init(224).....................: channel initialization failedMPIDI_CH3_Init(105)................: MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0)Invalid error code (-2) (error ring index 127 invalid)INTERNAL ERROR: invalid error code fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373Fatal error in PMPI_Init: Other MPI error, error stack:MPIR_Init_thread(586)..............: MPID_Init(224).....................: channel initialization failed* *MPIDI_CH3_Init(105)................: MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0)* I tried changing the <hostname> to localhost also but still it shows me the same error. On Tue, 5 Jan 2021 at 21:10, Zhou, Hui <zhouh(a)anl.gov> wrote: > Hi Hirakjyoti Sarma, > > > > Note that your local hostname was “*hirakjyoti-HP-dx2480-MT-KL969AV*” > according to your log. If you edit hosts file, you should simply add new > entries rather than overwriting “localhost” because “localhost” is useful > and maybe important for some applications. There are a few options other > than adding entries to hosts file. You could directly set hosts on command > line, e.g. `mpiexec -hosts=localhost …`. There is also an environment > variable for ch3 nemesis – you may try set > `MPIR_CVAR_CH3_INTERFACE_HOSTNAME` to e.g. “localhost”. > > > > -- > Hui Zhou > > > > > > *From: *Hirakjyoti Sarma via discuss <discuss(a)mpich.org> > *Date: *Monday, January 4, 2021 at 10:38 PM > *To: *discuss(a)mpich.org <discuss(a)mpich.org> > *Cc: *Hirakjyoti Sarma <herockx1995(a)gmail.com> > *Subject: *Re: [mpich-discuss] [discuss-mpich]Error while using mpirun > > I opened the hosts file by using Vi and changed "localhost" to " > hirakjyoti---- " and then saved it and closed and then rebooted the PC. But > even after that the problem persists. > > > > On Tue, 5 Jan 2021 at 10:04, Hirakjyoti Sarma <herockx1995(a)gmail.com> > wrote: > > Its 3.3.2-build1 > > > > On Tue, 5 Jan 2021 at 02:40, Zhou, Hui <zhouh(a)anl.gov> wrote: > > Hi Hirakjyoti Sarma, > > > > Could you identify the MPICH version? > > > > -- > Hui Zhou > > > > > > *From: *Hirakjyoti Sarma via discuss <discuss(a)mpich.org> > *Date: *Monday, January 4, 2021 at 10:59 AM > *To: *discuss(a)mpich.org <discuss(a)mpich.org> > *Cc: *Hirakjyoti Sarma <herockx1995(a)gmail.com> > *Subject: *[mpich-discuss] [discuss-mpich]Error while using mpirun > > > Dear all, > > I get the following error while running LAMMPS on ubuntu *without an > internet connection.* > > > > > > > > > > > > > > *Invalid error code (-2) (error ring index 127 invalid) Invalid error code > (-2) (error ring index 127 invalid) INTERNAL ERROR: invalid error code > fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373 Fatal error in > PMPI_Init: Other MPI error, error stack: > MPIR_Init_thread(586)..............: MPID_Init(224).....................: > channel initialization failed MPIDI_CH3_Init(105)................: > MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: > MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: > gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0)* > > > > But if the PC is connected to internet LAMMPS successfully run. > > How can i solve the problem? > > > > Regards, > > Hirak > >

1 0

some trouble with mpich + openmp thread affinity
by Burlen Loring 05 Jan '21

05 Jan '21

Hi All, I'm trying to accomplish binding each of a number of openmp threads to a unique physical core. my system has 2 hyper-threads per core, I want to bind only 1 openmp thread per physical core and skip hyper-thread "slots". My system has 10 cores (20 if you count hyper-threads). I want to run 2 mpi ranks each with 5 openmp threads, and I want the threads on rank 0 to bind to core: 0,1,2,3,4 and the threads on rank 1 to bind to core: 5,6,7,8,9. I've tried combinations of -bind-to and -map-by but I'm experiencing that the openmp threads are always doubled up , the hyperthread slots are being used. For example (a.out here prints the thread affinity): $ export OMP_PLACES=threads OMP_PROC_BIND=true OMP_DISPLAY_ENV=TRUE OMP_NUM_THREADS=5 $ mpiexec -np 2 -bind-to core:5 -map-by hwthread:10 ./a.out | sort -k 4 OPENMP DISPLAY ENVIRONMENT BEGIN _OPENMP = '201511' OMP_DYNAMIC = 'FALSE' OMP_NESTED = 'FALSE' OMP_NUM_THREADS = '5' OMP_SCHEDULE = 'DYNAMIC' OMP_PROC_BIND = 'TRUE' OMP_PLACES = '{0},{10},{1},{11},{2},{12},{3},{13},{4},{14}' OMP_STACKSIZE = '0' OMP_WAIT_POLICY = 'PASSIVE' OMP_THREAD_LIMIT = '4294967295' OMP_MAX_ACTIVE_LEVELS = '2147483647' OMP_CANCELLATION = 'FALSE' OMP_DEFAULT_DEVICE = '0' OMP_MAX_TASK_PRIORITY = '0' OMP_DISPLAY_AFFINITY = 'FALSE' OMP_AFFINITY_FORMAT = 'level %L thread %i affinity %A' OPENMP DISPLAY ENVIRONMENT END OPENMP DISPLAY ENVIRONMENT BEGIN _OPENMP = '201511' OMP_DYNAMIC = 'FALSE' OMP_NESTED = 'FALSE' OMP_NUM_THREADS = '5' OMP_SCHEDULE = 'DYNAMIC' OMP_PROC_BIND = 'TRUE' OMP_PLACES = '{5},{15},{6},{16},{7},{17},{8},{18},{9},{19}' OMP_STACKSIZE = '0' OMP_WAIT_POLICY = 'PASSIVE' OMP_THREAD_LIMIT = '4294967295' OMP_MAX_ACTIVE_LEVELS = '2147483647' OMP_CANCELLATION = 'FALSE' OMP_DEFAULT_DEVICE = '0' OMP_MAX_TASK_PRIORITY = '0' OMP_DISPLAY_AFFINITY = 'FALSE' OMP_AFFINITY_FORMAT = 'level %L thread %i affinity %A' OPENMP DISPLAY ENVIRONMENT END Hello from rank 0, thread 0, on smic.dhcp. (core affinity = 0) Hello from rank 0, thread 1, on smic.dhcp. (core affinity = 10) Hello from rank 0, thread 2, on smic.dhcp. (core affinity = 1) Hello from rank 0, thread 3, on smic.dhcp. (core affinity = 11) Hello from rank 0, thread 4, on smic.dhcp. (core affinity = 2) Hello from rank 1, thread 0, on smic.dhcp. (core affinity = 5) Hello from rank 1, thread 1, on smic.dhcp. (core affinity = 15) Hello from rank 1, thread 2, on smic.dhcp. (core affinity = 6) Hello from rank 1, thread 3, on smic.dhcp. (core affinity = 16) Hello from rank 1, thread 4, on smic.dhcp. (core affinity = 7) *How do I get mpich to skip the hyper-threads (i.e. cores with number greater than 9)?* Here's an example that did work: export OMP_PROC_BIND=true OMP_DISPLAY_ENV=TRUE OMP_NUM_THREADS=5 export OMP_PLACES="{0},{1},{2},{3},{4},{5},{6},{7},{8},{9}" mpiexec -np 2 -bind-to core:5 -map-by core:5 ./a.out libgomp: Number of places reduced from 10 to 5 because some places didn't contain any usable logical CPUs OPENMP DISPLAY ENVIRONMENT BEGIN _OPENMP = '201511' OMP_DYNAMIC = 'FALSE' OMP_NESTED = 'FALSE' OMP_NUM_THREADS = '5' OMP_SCHEDULE = 'DYNAMIC' OMP_PROC_BIND = 'TRUE' OMP_PLACES = '{0},{1},{2},{3},{4} libgomp: ' OMP_STACKSIZE = '0' OMP_WAIT_POLICY = 'PASSIVE' OMP_THREAD_LIMIT = '4294967295' OMP_MAX_ACTIVE_LEVELS = '2147483647' OMP_CANCELLATION = 'FALSE' OMP_DEFAULT_DEVICE = '0' OMP_MAX_TASK_PRIORITY = '0' OMP_DISPLAY_AFFINITY = 'FALSE' OMP_AFFINITY_FORMAT = 'level %L thread %i affinity %A' OPENMP DISPLAY ENVIRONMENT END Number of places reduced from 10 to 5 because some places didn't contain any usable logical CPUs OPENMP DISPLAY ENVIRONMENT BEGIN _OPENMP = '201511' OMP_DYNAMIC = 'FALSE' OMP_NESTED = 'FALSE' OMP_NUM_THREADS = '5' OMP_SCHEDULE = 'DYNAMIC' OMP_PROC_BIND = 'TRUE' OMP_PLACES = '{5},{6},{7},{8},{9}' OMP_STACKSIZE = '0' OMP_WAIT_POLICY = 'PASSIVE' OMP_THREAD_LIMIT = '4294967295' OMP_MAX_ACTIVE_LEVELS = '2147483647' OMP_CANCELLATION = 'FALSE' OMP_DEFAULT_DEVICE = '0' OMP_MAX_TASK_PRIORITY = '0' OMP_DISPLAY_AFFINITY = 'FALSE' OMP_AFFINITY_FORMAT = 'level %L thread %i affinity %A' OPENMP DISPLAY ENVIRONMENT END Hello from rank 0, thread 1, on smic.dhcp. (core affinity = 1) Hello from rank 0, thread 2, on smic.dhcp. (core affinity = 2) Hello from rank 1, thread 0, on smic.dhcp. (core affinity = 5) Hello from rank 0, thread 3, on smic.dhcp. (core affinity = 3) Hello from rank 0, thread 0, on smic.dhcp. (core affinity = 0) Hello from rank 1, thread 4, on smic.dhcp. (core affinity = 9) Hello from rank 0, thread 4, on smic.dhcp. (core affinity = 4) Hello from rank 1, thread 3, on smic.dhcp. (core affinity = 8) Hello from rank 1, thread 1, on smic.dhcp. (core affinity = 6) Hello from rank 1, thread 2, on smic.dhcp. (core affinity = 7) That's exactly what I want! *Could I accomplish this without setting OMP_PLACES list explicitly? And in the process hopefully avoid the libgomp warning. Is there some combination of -bind-to, -map-to that would achieve this result?* Thanks!

1 0

Re: [mpich-discuss] [discuss-mpich]Error while using mpirun
by Zhou, Hui 05 Jan '21

05 Jan '21

Hi Hirakjyoti Sarma, Note that your local hostname was “hirakjyoti-HP-dx2480-MT-KL969AV” according to your log. If you edit hosts file, you should simply add new entries rather than overwriting “localhost” because “localhost” is useful and maybe important for some applications. There are a few options other than adding entries to hosts file. You could directly set hosts on command line, e.g. `mpiexec -hosts=localhost …`. There is also an environment variable for ch3 nemesis – you may try set `MPIR_CVAR_CH3_INTERFACE_HOSTNAME` to e.g. “localhost”. -- Hui Zhou From: Hirakjyoti Sarma via discuss <discuss(a)mpich.org> Date: Monday, January 4, 2021 at 10:38 PM To: discuss(a)mpich.org <discuss(a)mpich.org> Cc: Hirakjyoti Sarma <herockx1995(a)gmail.com> Subject: Re: [mpich-discuss] [discuss-mpich]Error while using mpirun I opened the hosts file by using Vi and changed "localhost" to " hirakjyoti---- " and then saved it and closed and then rebooted the PC. But even after that the problem persists. On Tue, 5 Jan 2021 at 10:04, Hirakjyoti Sarma <herockx1995(a)gmail.com<mailto:[email protected]>> wrote: Its 3.3.2-build1 On Tue, 5 Jan 2021 at 02:40, Zhou, Hui <zhouh(a)anl.gov<mailto:[email protected]>> wrote: Hi Hirakjyoti Sarma, Could you identify the MPICH version? -- Hui Zhou From: Hirakjyoti Sarma via discuss <discuss(a)mpich.org<mailto:[email protected]>> Date: Monday, January 4, 2021 at 10:59 AM To: discuss(a)mpich.org<mailto:[email protected]> <discuss(a)mpich.org<mailto:[email protected]>> Cc: Hirakjyoti Sarma <herockx1995(a)gmail.com<mailto:[email protected]>> Subject: [mpich-discuss] [discuss-mpich]Error while using mpirun Dear all, I get the following error while running LAMMPS on ubuntu without an internet connection. Invalid error code (-2) (error ring index 127 invalid) Invalid error code (-2) (error ring index 127 invalid) INTERNAL ERROR: invalid error code fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373 Fatal error in PMPI_Init: Other MPI error, error stack: MPIR_Init_thread(586)..............: MPID_Init(224).....................: channel initialization failed MPIDI_CH3_Init(105)................: MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0) But if the PC is connected to internet LAMMPS successfully run. How can i solve the problem? Regards, Hirak

1 0

Re: [mpich-discuss] [discuss-mpich]Error while using mpirun
by Hirakjyoti Sarma 04 Jan '21

04 Jan '21

I opened the hosts file by using Vi and changed "localhost" to " hirakjyoti---- " and then saved it and closed and then rebooted the PC. But even after that the problem persists. On Tue, 5 Jan 2021 at 10:04, Hirakjyoti Sarma <herockx1995(a)gmail.com> wrote: > Its 3.3.2-build1 > > On Tue, 5 Jan 2021 at 02:40, Zhou, Hui <zhouh(a)anl.gov> wrote: > >> Hi Hirakjyoti Sarma, >> >> >> >> Could you identify the MPICH version? >> >> >> >> -- >> Hui Zhou >> >> >> >> >> >> *From: *Hirakjyoti Sarma via discuss <discuss(a)mpich.org> >> *Date: *Monday, January 4, 2021 at 10:59 AM >> *To: *discuss(a)mpich.org <discuss(a)mpich.org> >> *Cc: *Hirakjyoti Sarma <herockx1995(a)gmail.com> >> *Subject: *[mpich-discuss] [discuss-mpich]Error while using mpirun >> >> >> Dear all, >> >> I get the following error while running LAMMPS on ubuntu *without an >> internet connection.* >> >> >> >> >> >> >> >> >> >> >> >> >> >> *Invalid error code (-2) (error ring index 127 invalid) Invalid error >> code (-2) (error ring index 127 invalid) INTERNAL ERROR: invalid error code >> fffffffe (Ring Index out of range) in MPID_nem_tcp_init:373 Fatal error in >> PMPI_Init: Other MPI error, error stack: >> MPIR_Init_thread(586)..............: MPID_Init(224).....................: >> channel initialization failed MPIDI_CH3_Init(105)................: >> MPID_nem_init(324).................: MPID_nem_tcp_init(175).............: >> MPID_nem_tcp_get_business_card(401): MPID_nem_tcp_init(373).............: >> gethostbyname failed, hirakjyoti-HP-dx2480-MT-KL969AV (errno 0)* >> >> >> >> But if the PC is connected to internet LAMMPS successfully run. >> >> How can i solve the problem? >> >> >> >> Regards, >> >> Hirak >> >

1 0