RuntimeError: Job process returned error code 1

Traceback (most recent call last):
  File "/usr/local/bin/run_openkim_job.py", line 546, in <module>
    execute_in_place(runner, runner_driver, subject, subject_driver, env)
  File "/usr/local/bin/run_openkim_job.py", line 396, in execute_in_place
    raise RuntimeError(f"Job process returned error code {retcode}")
RuntimeError: Job process returned error code 1

output/pipeline.stdout:
-----------------------
element(s):['O']AFLOW prototype label:A_mC4_12_iParameter names:['a', 'b/a', 'c/a', 'beta', 'x1', 'z1']model type (only 'standard' supported at this time):standardnumber of parameter sets:2Parameter values for parameter set 0:['6.1332', '0.61429596', '0.89643253', '135.4539', '0.097219577', '0.15969399']Parameter values for parameter set 1:['4.8144', '0.81652958', '0.98066218', '141.8659', '0.18473196', '0.088770687']model name:

output/pipeline.stderr:
-----------------------
----------------------------------------------------------------------------------------------------------------------------------------------------It looks like MPI_INIT failed for some reason; your parallel process islikely to abort.  There are many reasons that a parallel process canfail during MPI_INIT; some of which are due to configuration or environmentproblems.  This failure appears to be an internal failure; here's someadditional information (which may only be relevant to an Open MPIdeveloper):  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)[c413-023.stampede2.tacc.utexas.edu:172745] 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!Command exited with non-zero status 1{"realtime":18.94,"usertime":26.33,"systime":31.46,"memmax":111052,"memavg":0}

output/kim.log:
---------------
2023-05-08:17:00:10CDT * 0 * information * 0x2040100 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-05-08:17:00:10CDT * 1 * information * 0x2040100 * KIM_LogImplementation.cpp:120 * Log object destroyed.2023-05-08:17:00:10CDT * 0 * information * 0x2040100 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-05-08:17:00:10CDT * 0 * information * 0x202c4c0 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-05-08:17:00:10CDT * 1 * information * 0x202c4c0 * KIM_LogImplementation.cpp:242 * Log object renamed.  ID changed to '0x2040100_Collections'.2023-05-08:17:00:10CDT * 2 * information * 0x2040100_Collections * KIM_LogImplementation.cpp:246 * Log object renamed.  ID changed from '0x202c4c0'.2023-05-08:17:00:10CDT * 3 * information * 0x2040100_Collections * KIM_LogImplementation.cpp:120 * Log object destroyed.2023-05-08:17:00:10CDT * 1 * information * 0x2040100 * KIM_LogImplementation.cpp:120 * Log object destroyed.