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_mC48_15_ae3f_2fParameter names:['a', 'b/a', 'c/a', 'beta', 'y2', 'x3', 'y3', 'z3', 'x4', 'y4', 'z4', 'x5', 'y5', 'z5', 'x6', 'y6', 'z6', 'x7', 'y7', 'z7']model type (only 'standard' supported at this time):standardnumber of parameter sets:1Parameter values for parameter set 0:['7.2218', '1.7345399', '1.0053449', '120.1697', '0.38297265', '0.26809323', '0.12365979', '0.94272102', '0.3097446', '0.10419553', '0.3288151', '0.017903941', '0.21138494', '0.47811122', '0.14057703', '0.10837587', '0.073344259', '0.50606235', '0.15851462', '0.54012699']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:99394] 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":19.21,"usertime":29.99,"systime":37.28,"memmax":95168,"memavg":0}

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