My program is failing in MPI_Comm_spawn, but it seems to simply terminate the job rather than throwing an exception that I can catch. Here is the abbreviated error message:
[n001:32127] *** An error occurred in MPI_Comm_spawn [n001:32127] *** reported by process [1679884289,1] [n001:32127] *** on communicator MPI_COMM_SELF [n001:32127] *** MPI_ERR_SPAWN: could not spawn processes [n001:32127] *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, [n001:32127] *** and potentially your MPI job) [n002.cluster.com:21375] PMIX ERROR: BAD-PARAM in file event/pmix_event_notification.c at line 923 [n001.cluster.com:32115] PMIX ERROR: BAD-PARAM in file event/pmix_event_notification.c at line 923 When I compiled OpenMpi, I used the following flags: ./configure --prefix=/opt/openmpi_pgc --enable-mpi-cxx --enable-cxx-exceptions --with-tm Is --enable-cxx-exceptions not sufficient by itself to enable exceptions? I'm using the Portland Group Compiler pgc++ 19.5-0 and OpenMpi 4.0.2.
