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):['Si']AFLOW prototype label:A_hP58_164_2d3i3jParameter names:['a', 'c/a', 'z1', 'z2', 'x3', 'z3', 'x4', 'z4', 'x5', 'z5', 'x6', 'y6', 'z6', 'x7', 'y7', 'z7', 'x8', 'y8', 'z8']model type (only 'standard' supported at this time):standardnumber of parameter sets:1Parameter values for parameter set 0:['10.017', '1.6093441', '0.42717347', '0.57149774', '0.13353688', '0.49951896', '0.20865981', '0.62176631', '0.20852652', '0.37695719', '0.38057577', '0.3795477', '0.29513767', '0.00061200299', '0.24460663', '0.17356382', '0.33353138', '0.4211924', '0.058121322']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)[c401-041.stampede2.tacc.utexas.edu:146723] 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":41.66,"usertime":51.50,"systime":50.66,"memmax":226272,"memavg":0}

output/kim.log:
---------------
2023-05-03:12:44:37CDT * 0 * information * 0x1740320 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-05-03:12:44:37CDT * 1 * information * 0x1740320 * KIM_LogImplementation.cpp:120 * Log object destroyed.2023-05-03:12:44:37CDT * 0 * information * 0x1740320 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-05-03:12:44:37CDT * 0 * information * 0x1752f20 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-05-03:12:44:37CDT * 1 * information * 0x1752f20 * KIM_LogImplementation.cpp:242 * Log object renamed.  ID changed to '0x1740320_Collections'.2023-05-03:12:44:37CDT * 2 * information * 0x1740320_Collections * KIM_LogImplementation.cpp:246 * Log object renamed.  ID changed from '0x1752f20'.2023-05-03:12:44:37CDT * 3 * information * 0x1740320_Collections * KIM_LogImplementation.cpp:120 * Log object destroyed.2023-05-03:12:44:37CDT * 1 * information * 0x1740320 * KIM_LogImplementation.cpp:120 * Log object destroyed.