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', 'Si']AFLOW prototype label:A2B_mC24_5_4c_2cParameter names:['a', 'b/a', 'c/a', 'beta', 'x1', 'y1', 'z1', 'x2', 'y2', 'z2', 'x3', 'y3', 'z3', 'x4', 'y4', 'z4', 'x5', 'y5', 'z5', 'x6', 'y6', 'z6']model type (only 'standard' supported at this time):standardnumber of parameter sets:1Parameter values for parameter set 0:['7.0382', '1.1901196', '0.78304112', '80.0886', '0.81146923', '0.9742149', '0.43188016', '0.69401684', '0.19172755', '0.76169962', '0.81994213', '0.92906867', '0.92873698', '0.50133182', '0.90628269', '0.2498968', '0.70528806', '0.00048762245', '0.71739382', '0.26557668', '0.87432857', '0.78824212']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)[c408-134.stampede2.tacc.utexas.edu:97022] 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":23.93,"usertime":28.70,"systime":33.62,"memmax":157588,"memavg":0}

output/kim.log:
---------------
2023-04-04:10:35:17CDT * 0 * information * 0x20bb5d0 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-04-04:10:35:17CDT * 1 * information * 0x20bb5d0 * KIM_LogImplementation.cpp:120 * Log object destroyed.2023-04-04:10:35:17CDT * 0 * information * 0x20bb5d0 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-04-04:10:35:17CDT * 0 * information * 0x22146d0 * KIM_LogImplementation.cpp:110 * Log object created.  Default verbosity level is 'information'.2023-04-04:10:35:17CDT * 1 * information * 0x22146d0 * KIM_LogImplementation.cpp:242 * Log object renamed.  ID changed to '0x20bb5d0_Collections'.2023-04-04:10:35:17CDT * 2 * information * 0x20bb5d0_Collections * KIM_LogImplementation.cpp:246 * Log object renamed.  ID changed from '0x22146d0'.2023-04-04:10:35:17CDT * 3 * information * 0x20bb5d0_Collections * KIM_LogImplementation.cpp:120 * Log object destroyed.2023-04-04:10:35:17CDT * 1 * information * 0x20bb5d0 * KIM_LogImplementation.cpp:120 * Log object destroyed.