[c442-111.stampede2.tacc.utexas.edu:216591] mca_base_component_repository_open: unable to open mca_reachable_netlink: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_reachable_netlink.so: failed to map segment from shared object (ignored) [c442-111.stampede2.tacc.utexas.edu:216590] mca_base_component_repository_open: unable to open mca_schizo_flux: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_flux.so: failed to map segment from shared object (ignored) [c442-111.stampede2.tacc.utexas.edu:216596] mca_base_component_repository_open: unable to open mca_schizo_ompi: /usr/lib/x86_64-linux-gnu/openmpi/lib/openmpi3/mca_schizo_ompi.so: failed to map segment from shared object (ignored) [c442-111.stampede2.tacc.utexas.edu:216598] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 633 [c442-111.stampede2.tacc.utexas.edu:216602] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 633 [c442-111.stampede2.tacc.utexas.edu:216591] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 633 [c442-111.stampede2.tacc.utexas.edu:216590] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 633 [c442-111.stampede2.tacc.utexas.edu:216602] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 172 [c442-111.stampede2.tacc.utexas.edu:216598] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 172 [c442-111.stampede2.tacc.utexas.edu:216596] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 633 [c442-111.stampede2.tacc.utexas.edu:216591] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 172 [c442-111.stampede2.tacc.utexas.edu:216590] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 172 [c442-111.stampede2.tacc.utexas.edu:216596] [[INVALID],INVALID] ORTE_ERROR_LOG: The system limit on number of children a process can have was reached in file ess_singleton_module.c at line 172 -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like orte_init failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during orte_init; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): orte_ess_init failed --> Returned value The system limit on number of children a process can have was reached (-119) instead of ORTE_SUCCESS -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0) -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0) -------------------------------------------------------------------------- *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, [c442-111.stampede2.tacc.utexas.edu:216591] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0) -------------------------------------------------------------------------- *** and potentially your MPI job) -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0) -------------------------------------------------------------------------- -------------------------------------------------------------------------- It looks like MPI_INIT failed for some reason; your parallel process is likely to abort. There are many reasons that a parallel process can fail during MPI_INIT; some of which are due to configuration or environment problems. This failure appears to be an internal failure; here's some additional information (which may only be relevant to an Open MPI developer): ompi_mpi_init: ompi_rte_init failed --> Returned "The system limit on number of children a process can have was reached" (-119) instead of "Success" (0) -------------------------------------------------------------------------- [c442-111.stampede2.tacc.utexas.edu:216602] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! *** An error occurred in MPI_Init *** An error occurred in MPI_Init *** on a NULL communicator *** An error occurred in MPI_Init *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** on a NULL communicator *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) *** MPI_ERRORS_ARE_FATAL (processes in this communicator will now abort, *** and potentially your MPI job) *** and potentially your MPI job) [c442-111.stampede2.tacc.utexas.edu:216598] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! [c442-111.stampede2.tacc.utexas.edu:216596] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! [c442-111.stampede2.tacc.utexas.edu:216590] Local abort before MPI_INIT completed completed successfully, but am not able to aggregate error messages, and not able to guarantee that all other processes were killed! Traceback (most recent call last): File "../../td/LinearThermalExpansionCoeffCubic__TD_522633393614_001/runner", line 343, in alpha = compute_alpha(lmpvolfile, T) File "../../td/LinearThermalExpansionCoeffCubic__TD_522633393614_001/runner", line 180, in compute_alpha with open(fin, "r") as f: FileNotFoundError: [Errno 2] No such file or directory: 'output/vol_T253.15.out' Command exited with non-zero status 1 {"realtime":2.50,"usertime":3.51,"systime":10.56,"memmax":39244,"memavg":0}