Scheduled Downtime
On Tuesday 24 October 2023 @ 5pm MT the forums will be in read only mode in preparation for the downtime. On Wednesday 25 October 2023 @ 5am MT, this website will be down for maintenance and expected to return online later in the morning.
Normal Operations
The forums are back online with normal operations. If you notice any issues or errors related to the forums, please reach out to help@ucar.edu

Case Run Error

Letitia

New Member
I just started learning how to use CESM.
I have successfully ported CESM2.1.1. And the test ran successfully at that time. Today, I tried according to the official website case, but there was an error in the final operation.
This is my case:./create_newcase--case Exercise1 --res f19_g17 --compset B1850 --machine ibmintel

An error occurred When I submit:

MODEL EXECUTION BEGINS HERE
run command is mpirun -n 96 -genv LD_LIBRARY_PATH /public3/home/interior/cas/cuser038/zy/netcdf4.4-intelf/lib:$LD_LIBRARY_PATH /public3/home/interior/cas/cuser038/CESM/cime/case/Exercise1/bld/cesm.exe >> cesm.log.$LID 2>&1
ERROR: RUN FAIL: Command 'mpirun -n 96 -genv LD_LIBRARY_PATH /public3/home/interior/cas/cuser038/zy/netcdf4.4-intelf/lib:$LD_LIBRARY_PATH /public3/home/interior/cas/cuser038/CESM/cime/case/Exercise1/bld/cesm.exe >> cesm.log.$LID 2>&1 ' failed
See log file for details: /public3/home/interior/cas/cuser038/CESM/cime/case/Exercise1/run/cesm.log.
The last display of cesm.log:

@2ENQ9@$0_ZQ_(8IZVA89$I.png


I don't know what the mistake is and how can I fix it...
THANKS!!
 

erik

Erik Kluzek
CSEG and Liaisons
Staff member
Hmmm, the log file above doesn't tell enough to see what's going on. You should look through all of the log files to see if there's any help in another one of them. You also might want to clean the build and then set DEBUG=TRUE and recompile and rerun to see if that helps. You also might try a simpler case or a lower resolution. It's also helpful to run the case on a machine that's known to work, so you see what normal behavior is, to help diagnose problems on your other machine.
 

Letitia

New Member
I found that the error may be running on the login node. Thanks for your advice. I will try another case.
 
Top