- discuss - mailman3.cels.anl.gov

Re: [mpich-discuss] MPICH equivalent to OMPI_COMM_WORLD_RANK
by Zhou, Hui 04 Jan '21

04 Jan '21

With the default `mpiexec`, which is `mpiexec.hydra`, it sets environment variable `PMI_RANK`, and `PMI_SIZE`. You can check that with mpiexec -n 1 env |grep PMI_ -- Hui Zhou From: Sajid Ali via discuss <discuss(a)mpich.org> Date: Monday, January 4, 2021 at 8:13 PM To: discuss(a)mpich.org <discuss(a)mpich.org> Cc: Sajid Ali <sajidsyed2021(a)u.northwestern.edu> Subject: [mpich-discuss] MPICH equivalent to OMPI_COMM_WORLD_RANK Hi MPICH-developers, Does MPICH set an environment variable describing the MPI rank equivalent to OpenMPI's `OMPI_COMM_WORLD_RANK` ? If so, what is it called ? Thank You, Sajid Ali (he/him) | PhD Candidate Applied Physics Northwestern University s-sajid-ali.github.io<http://s-sajid-ali.github.io>

1 0

MPICH equivalent to OMPI_COMM_WORLD_RANK
by Sajid Ali 04 Jan '21

04 Jan '21

Hi MPICH-developers, Does MPICH set an environment variable describing the MPI rank equivalent to OpenMPI's `OMPI_COMM_WORLD_RANK` ? If so, what is it called ? Thank You, Sajid Ali (he/him) | PhD Candidate Applied Physics Northwestern University s-sajid-ali.github.io

1 0

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

04 Jan '21

> 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: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

1 0

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

04 Jan '21

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

Re: [mpich-discuss] Is PMIx working well for ch4:ucx ? Intermitent Seg Fault in MPIR_pmi_init()
by Zhou, Hui 04 Jan '21

04 Jan '21

Hi Martin, PMIx with MPICH is not well tested with large number of nodes and we are not aware of the issue you described. We’ll look into it. Meanwhile, if you could file a github issue, that will help us better tracking it. Thanks for reporting it. -- Hui Zhou From: Audet, Martin via discuss <discuss(a)mpich.org> Date: Tuesday, December 22, 2020 at 5:16 PM To: discuss(a)mpich.org <discuss(a)mpich.org> Cc: Audet, Martin <Martin.Audet(a)cnrc-nrc.gc.ca>, Raymond, Stephane <Stephane.Raymond(a)cnrc-nrc.gc.ca> Subject: [mpich-discuss] Is PMIx working well for ch4:ucx ? Intermitent Seg Fault in MPIR_pmi_init() Hello MPICH_Users && MPICH_Developers, Is the new mpich version 3.4rc1 is supposed to work well with PMIx when using the ch4:ucx device or is it still considered experimental ? Yesterday when trying it with a my usual “hellompihost2.cpp” test program on our cluster it turns out that it created intermittent Segmentation fault in the MPIR_pmi_init() initialization function which is indirectly called by MPI_Init(). It seems that the higher number of “processors” (MPI ranks) involved, the higher the chances of having this problem. With 24 nodes each with 24 or 48 “processors” (MPI ranks) the probability seems to be 100%. When keeping 24 “processors” per node, the probability of having this problem increase rapidly when increasing the node count from 9 to 10 (i.e. at 9 nodes it works most of the time and with 10 nodes it fails most of the time). Note that my “hellompihost2.cpp” program works very well with OpenMPI and with the same mpich 3.4rc1 but with the ch3:sock or ch3:nemesis channel (using the PMI2 startup mechanism). We use Slurm version 20.02.6 and PMIx 3.1.5. Our OS is CentOS 7.9 (latest kernel and packages) and we use MOFED 4.9.2.2.4.0. As you can see our environment is absolutely not exotic and should be very common among mpich users. Below is the output from uname, mpichversion, the source code of hellompihost2.cpp and a sample of the output when it crashes. Thanks, Martin Audet [audetm@hn audetm]$ uname -a Linux hn.galerkin.res.nrc.gc.ca 3.10.0-1160.6.1.el7.x86_64 #1 SMP Tue Nov 17 13:59:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [audetm@hn audetm]$ mpichversion MPICH Version: 3.4rc1 MPICH Release date: Thu Dec 10 14:41:59 CST 2020 MPICH Device: ch4:ucx MPICH configure: --with-device=ch4:ucx --with-hcoll=/opt/mellanox/hcoll --with-pmix=/usr --prefix=/work/software/x86_64/mpi/mpich-ch4_ucx-3.4rc1 --enable-fast=all --enable-romio --with-file-system=ufs+nfs+lustre --enable-shared --enable-sharedlibs=gcc MPICH CC: gcc -std=gnu99 -std=gnu99 -DNDEBUG -DNVALGRIND -O2 MPICH CXX: g++ -DNDEBUG -DNVALGRIND -O2 MPICH F77: gfortran -O2 MPICH FC: gfortran -O2 MPICH Custom Information: [audetm@hn audetm]$ #include <mpi.h> #include <unistd.h> #include <sched.h> #include <iostream> #include <vector> #include <sstream> #include <string> int main(int argc, char **argv) { MPI_Init(&argc, &argv); std::ostringstream ostr; const MPI_Comm cur_comm = MPI_COMM_WORLD; int comm_rank, comm_size; MPI_Comm_rank(cur_comm, &comm_rank); MPI_Comm_size(cur_comm, &comm_size); char name_buf[MPI_MAX_PROCESSOR_NAME+1]; int name_len; MPI_Get_processor_name(name_buf, &name_len); name_buf[name_len] = '\0'; ostr << "rank " << comm_rank << " running on " << name_buf << " PID " << getpid() << " pinned to CPUs "; cpu_set_t cpuset; const int ret = sched_getaffinity(0, sizeof(cpuset), &cpuset); if (ret == 0) { bool prev = false; for (int i_cpu=0; i_cpu < CPU_SETSIZE; i_cpu++) { if (CPU_ISSET(i_cpu, &cpuset)) { if (prev) { ostr << ','; } ostr << i_cpu; prev = true; } } } else { ostr << "(unknown)"; } const std::string msg(ostr.str()); const int msg_len = int(msg.size()); const int msg_len2 = msg_len; enum { STR_LEN_TAG, STR_VAL_TAG }; const int ROOT_RANK = 0; MPI_Request req_tbl[2]; MPI_Isend(&msg_len2, 1, MPI_INT, ROOT_RANK, STR_LEN_TAG, cur_comm, &req_tbl[0]); MPI_Isend(msg.data(), msg_len, MPI_CHAR, ROOT_RANK, STR_VAL_TAG, cur_comm, &req_tbl[1]); if (comm_rank == ROOT_RANK) { std::cout << "Running with " << comm_size << " process\n"; std::vector<char> recv_msg; for (int i_rank=0; i_rank < comm_size; i_rank++) { int recv_len; MPI_Status stat; MPI_Recv(&recv_len, 1, MPI_INT, i_rank, STR_LEN_TAG, cur_comm, &stat); recv_msg.resize(recv_len+2); MPI_Recv(&recv_msg[0], recv_len, MPI_CHAR, i_rank, STR_VAL_TAG, cur_comm, &stat); recv_msg[recv_len ] = '\n'; recv_msg[recv_len+1] = '\0'; std::cout << &recv_msg[0]; } } std::cout << std::flush; MPI_Status stat_tbl[2]; MPI_Waitall(2, req_tbl, stat_tbl); MPI_Finalize(); return 0; } audetm@hn audetm]$ time srun --nodes=16 --ntasks-per-node=48 --ntasks-per-core=2 --exclusive ./hellompihost2_ch4_ucx_34rc1 [cn12:29033:0:29033] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x905aea0) [cn12:29032:0:29032] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x9726690) [cn12:29049:0:29049] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x423fea0) [cn12:29034:0:29034] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x3308690) [cn9:29497:0:29497] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x986e460) [cn9:29523:0:29523] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x9a3f460) [cn9:29491:0:29491] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x31d0460) [cn9:29521:0:29521] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x8a86460) [cn12:29037:0:29037] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x55e5690) [cn9:29493:0:29493] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x96de460) ==== backtrace (tid: 29032) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= [cn9:29485:0:29485] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x4381c50) ==== backtrace (tid: 29033) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= ==== backtrace (tid: 29049) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= [cn7:34315:0:34315] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xbbcd450) [cn7:34310:0:34310] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x47b4c40) [cn7:34311:0:34311] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x86f2c40) [cn7:34320:0:34320] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2775c40) [cn7:34322:0:34322] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x8a5e450) [cn2:34371:0:34371] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x9e8fc70) [cn2:34394:0:34394] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x3036480) [cn2:34370:0:34370] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2951480) [cn12:29030:0:29030] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x5b4e690) [cn11:29124:0:29124] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x843c470) ==== backtrace (tid: 29034) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= [cn12:29059:0:29059] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xa1f3690) [cn7:34331:0:34331] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2630c40) [cn12:29044:0:29044] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x639b690) [cn11:29159:0:29159] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xaa1fc60) [cn11:29126:0:29126] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x735bc60) ==== backtrace (tid: 29037) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 =================================

1 0

Re: [mpich-discuss] Question about non-blocking MPI - 3
by Zhou, Hui 04 Jan '21

04 Jan '21

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

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

04 Jan '21

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? Regards, Hirak

1 0

Is PMIx working well for ch4:ucx ? Intermitent Seg Fault in MPIR_pmi_init()
by Audet, Martin 22 Dec '20

22 Dec '20

Hello MPICH_Users && MPICH_Developers, Is the new mpich version 3.4rc1 is supposed to work well with PMIx when using the ch4:ucx device or is it still considered experimental ? Yesterday when trying it with a my usual "hellompihost2.cpp" test program on our cluster it turns out that it created intermittent Segmentation fault in the MPIR_pmi_init() initialization function which is indirectly called by MPI_Init(). It seems that the higher number of "processors" (MPI ranks) involved, the higher the chances of having this problem. With 24 nodes each with 24 or 48 "processors" (MPI ranks) the probability seems to be 100%. When keeping 24 "processors" per node, the probability of having this problem increase rapidly when increasing the node count from 9 to 10 (i.e. at 9 nodes it works most of the time and with 10 nodes it fails most of the time). Note that my "hellompihost2.cpp" program works very well with OpenMPI and with the same mpich 3.4rc1 but with the ch3:sock or ch3:nemesis channel (using the PMI2 startup mechanism). We use Slurm version 20.02.6 and PMIx 3.1.5. Our OS is CentOS 7.9 (latest kernel and packages) and we use MOFED 4.9.2.2.4.0. As you can see our environment is absolutely not exotic and should be very common among mpich users. Below is the output from uname, mpichversion, the source code of hellompihost2.cpp and a sample of the output when it crashes. Thanks, Martin Audet [audetm@hn audetm]$ uname -a Linux hn.galerkin.res.nrc.gc.ca 3.10.0-1160.6.1.el7.x86_64 #1 SMP Tue Nov 17 13:59:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux [audetm@hn audetm]$ mpichversion MPICH Version: 3.4rc1 MPICH Release date: Thu Dec 10 14:41:59 CST 2020 MPICH Device: ch4:ucx MPICH configure: --with-device=ch4:ucx --with-hcoll=/opt/mellanox/hcoll --with-pmix=/usr --prefix=/work/software/x86_64/mpi/mpich-ch4_ucx-3.4rc1 --enable-fast=all --enable-romio --with-file-system=ufs+nfs+lustre --enable-shared --enable-sharedlibs=gcc MPICH CC: gcc -std=gnu99 -std=gnu99 -DNDEBUG -DNVALGRIND -O2 MPICH CXX: g++ -DNDEBUG -DNVALGRIND -O2 MPICH F77: gfortran -O2 MPICH FC: gfortran -O2 MPICH Custom Information: [audetm@hn audetm]$ #include <mpi.h> #include <unistd.h> #include <sched.h> #include <iostream> #include <vector> #include <sstream> #include <string> int main(int argc, char **argv) { MPI_Init(&argc, &argv); std::ostringstream ostr; const MPI_Comm cur_comm = MPI_COMM_WORLD; int comm_rank, comm_size; MPI_Comm_rank(cur_comm, &comm_rank); MPI_Comm_size(cur_comm, &comm_size); char name_buf[MPI_MAX_PROCESSOR_NAME+1]; int name_len; MPI_Get_processor_name(name_buf, &name_len); name_buf[name_len] = '\0'; ostr << "rank " << comm_rank << " running on " << name_buf << " PID " << getpid() << " pinned to CPUs "; cpu_set_t cpuset; const int ret = sched_getaffinity(0, sizeof(cpuset), &cpuset); if (ret == 0) { bool prev = false; for (int i_cpu=0; i_cpu < CPU_SETSIZE; i_cpu++) { if (CPU_ISSET(i_cpu, &cpuset)) { if (prev) { ostr << ','; } ostr << i_cpu; prev = true; } } } else { ostr << "(unknown)"; } const std::string msg(ostr.str()); const int msg_len = int(msg.size()); const int msg_len2 = msg_len; enum { STR_LEN_TAG, STR_VAL_TAG }; const int ROOT_RANK = 0; MPI_Request req_tbl[2]; MPI_Isend(&msg_len2, 1, MPI_INT, ROOT_RANK, STR_LEN_TAG, cur_comm, &req_tbl[0]); MPI_Isend(msg.data(), msg_len, MPI_CHAR, ROOT_RANK, STR_VAL_TAG, cur_comm, &req_tbl[1]); if (comm_rank == ROOT_RANK) { std::cout << "Running with " << comm_size << " process\n"; std::vector<char> recv_msg; for (int i_rank=0; i_rank < comm_size; i_rank++) { int recv_len; MPI_Status stat; MPI_Recv(&recv_len, 1, MPI_INT, i_rank, STR_LEN_TAG, cur_comm, &stat); recv_msg.resize(recv_len+2); MPI_Recv(&recv_msg[0], recv_len, MPI_CHAR, i_rank, STR_VAL_TAG, cur_comm, &stat); recv_msg[recv_len ] = '\n'; recv_msg[recv_len+1] = '\0'; std::cout << &recv_msg[0]; } } std::cout << std::flush; MPI_Status stat_tbl[2]; MPI_Waitall(2, req_tbl, stat_tbl); MPI_Finalize(); return 0; } audetm@hn audetm]$ time srun --nodes=16 --ntasks-per-node=48 --ntasks-per-core=2 --exclusive ./hellompihost2_ch4_ucx_34rc1 [cn12:29033:0:29033] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x905aea0) [cn12:29032:0:29032] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x9726690) [cn12:29049:0:29049] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x423fea0) [cn12:29034:0:29034] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x3308690) [cn9:29497:0:29497] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x986e460) [cn9:29523:0:29523] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x9a3f460) [cn9:29491:0:29491] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x31d0460) [cn9:29521:0:29521] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x8a86460) [cn12:29037:0:29037] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x55e5690) [cn9:29493:0:29493] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x96de460) ==== backtrace (tid: 29032) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= [cn9:29485:0:29485] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x4381c50) ==== backtrace (tid: 29033) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= ==== backtrace (tid: 29049) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= [cn7:34315:0:34315] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xbbcd450) [cn7:34310:0:34310] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x47b4c40) [cn7:34311:0:34311] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x86f2c40) [cn7:34320:0:34320] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2775c40) [cn7:34322:0:34322] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x8a5e450) [cn2:34371:0:34371] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x9e8fc70) [cn2:34394:0:34394] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x3036480) [cn2:34370:0:34370] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2951480) [cn12:29030:0:29030] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x5b4e690) [cn11:29124:0:29124] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x843c470) ==== backtrace (tid: 29034) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 ================================= [cn12:29059:0:29059] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xa1f3690) [cn7:34331:0:34331] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x2630c40) [cn12:29044:0:29044] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x639b690) [cn11:29159:0:29159] Caught signal 11 (Segmentation fault: address not mapped to object at address 0xaa1fc60) [cn11:29126:0:29126] Caught signal 11 (Segmentation fault: address not mapped to object at address 0x735bc60) ==== backtrace (tid: 29037) ==== 0 0x000000000004d455 ucs_debug_print_backtrace() ???:0 1 0x0000000000305a6c MPIR_pmi_init() :0 2 0x000000000031303f MPID_Init() :0 3 0x0000000000202fa6 MPIR_Init_thread() :0 4 0x0000000000202df2 PMPI_Init() ???:0 5 0x0000000000401805 main() ???:0 6 0x0000000000022555 __libc_start_main() ???:0 7 0x0000000000401709 _start() ???:0 =================================

1 0

Re: [mpich-discuss] Communication
by Raffenetti, Kenneth J. 09 Dec '20

09 Dec '20

This error output is mostly just Hydra (mpiexec) cleaning up after an MPI process crashed. This line: srun: error: node008: task 0: Exited with exit code 7 indicates the failed process exited with error code 7. Does the test program generate useful error codes? It could also indicate a signal (e.g. SIGBUS) that caused the program to crash. Ken On 12/9/20, 9:50 AM, "Palmer, Bruce J via discuss" <discuss(a)mpich.org> wrote: Hi, I’m currently debugging a variant of the progress ranks runtime used in Global Arrays and I’m getting a failure in one of the runtime test programs when I run on more than one node (running on one node is successful). The failure occurs in a portion of the code that is performing a large number of MPI_Isends on the sending side and posting MPI_Recv from MPI_ANY_SOURCE on the receive side. The configuration is 6 MPI ranks evenly split between two nodes and the error is [proxy:0:[email protected]] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): assert (!closed) failed [proxy:0:[email protected]] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): callback returned error status [proxy:0:[email protected]] main (pm/pmiserv/pmip.c:200): demux engine error waiting for event srun: error: node008: task 0: Exited with exit code 7 [mpiexec(a)node008.local] HYDT_bscu_wait_for_completion (tools/bootstrap/utils/bscu_wait.c:75): one of the processes terminated badly; aborting [mpiexec(a)node008.local] HYDT_bsci_wait_for_completion (tools/bootstrap/src/bsci_wait.c:22): launcher returned error waiting for completion [mpiexec(a)node008.local] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:215): launcher returned error waiting for completion [mpiexec(a)node008.local] main (ui/mpich/mpiexec.c:336): process manager error waiting for completion Can anyone describe in layman’s terms what might be generating this type of error? I’m using the mpich-3.4a2 release and configuring with ./configure --prefix=/people/bjpalmer/mpich/mpich-3.4a2/install --with-device=ch4:ofi:sockets --with-libfabric=embedded --enable-threads=multiple --with-slurm CC=gcc CXX=g++ Bruce Palmer Senior Research Scientist Pacific Northwest National Laboratory Richland, WA 99352 (509) 375-3899

1 0

Communication
by Palmer, Bruce J 09 Dec '20

09 Dec '20

Hi, I’m currently debugging a variant of the progress ranks runtime used in Global Arrays and I’m getting a failure in one of the runtime test programs when I run on more than one node (running on one node is successful). The failure occurs in a portion of the code that is performing a large number of MPI_Isends on the sending side and posting MPI_Recv from MPI_ANY_SOURCE on the receive side. The configuration is 6 MPI ranks evenly split between two nodes and the error is [proxy:0:[email protected]] HYD_pmcd_pmip_control_cmd_cb (pm/pmiserv/pmip_cb.c:878): assert (!closed) failed [proxy:0:[email protected]] HYDT_dmxu_poll_wait_for_event (tools/demux/demux_poll.c:77): callback returned error status [proxy:0:[email protected]] main (pm/pmiserv/pmip.c:200): demux engine error waiting for event srun: error: node008: task 0: Exited with exit code 7 [mpiexec(a)node008.local] HYDT_bscu_wait_for_completion (tools/bootstrap/utils/bscu_wait.c:75): one of the processes terminated badly; aborting [mpiexec(a)node008.local] HYDT_bsci_wait_for_completion (tools/bootstrap/src/bsci_wait.c:22): launcher returned error waiting for completion [mpiexec(a)node008.local] HYD_pmci_wait_for_completion (pm/pmiserv/pmiserv_pmci.c:215): launcher returned error waiting for completion [mpiexec(a)node008.local] main (ui/mpich/mpiexec.c:336): process manager error waiting for completion Can anyone describe in layman’s terms what might be generating this type of error? I’m using the mpich-3.4a2 release and configuring with ./configure --prefix=/people/bjpalmer/mpich/mpich-3.4a2/install --with-device=ch4:ofi:sockets --with-libfabric=embedded --enable-threads=multiple --with-slurm CC=gcc CXX=g++ Bruce Palmer Senior Research Scientist Pacific Northwest National Laboratory Richland, WA 99352 (509) 375-3899

1 0