Hi everyone,

[dharmendraks841]

Could you please look at the following error in CAM6 run
ERROR: Command: 'mpiexec_mpt -p "%g:" -np 360 omplace -tm open64 -vv /glade/scratch/dksingh/spcontrail18/bld/cesm.exe >> cesm.log.$LID 2>&1 ' failed with error '' from dir '/glade/scratch/dksingh/spcontrail18/run'

---------------------------------------------------

2023-08-09 03:18:12: case.run error

ERROR: RUN FAIL: Command 'mpiexec_mpt -p "%g:" -np 360 omplace -tm open64 -vv /glade/scratch/dksingh/spcontrail18/bld/cesm.exe >> cesm.log.$LID 2>&1 ' failed

See log file for details: /glade/scratch/dksingh/spcontrail18/run/cesm.log.2457519.chadmin1.ib0.cheyenne.ucar.edu.230809-022650

---------------------------------------------------

 

[nuvolet]

I would start by looking at the log file indicated:

See log file for details: /glade/scratch/dksingh/spcontrail18/run/cesm.log.2457519.chadmin1.ib0.cheyenne.ucar.edu.230809-022650

And from there see what is the problem.

Good luck

 

[dharmendraks841]

hi are you trying....to resolve this, any help will be appreciated

 

[nuvolet]

hi are you trying....to resolve this, any help will be appreciated

Could you upload the file indicated (/glade/scratch/dksingh/spcontrail18/run/cesm.log.2457519.chadmin1.ib0.cheyenne.ucar.edu.230809-022650)?.
Looking at this file we'll have more details about the problem and most probably it could be easier to indentify the error.
Thanks

 

[dharmendraks841]

I am astonished that when I ran for only one month (May 2018) with the separate case it was running and archived successfully.

You can see my case directory for 1 month here /glade/work/dksingh/contrail_23/may18_case_spinup

BUT
When I ran again from January to December 2018 with a new case, I found again the same error of May 2018 as previous (ran from Jan to April successfully) and May 2018 failed, please check the new case below:

/glade/work/dksingh/contrail_23/spcontrail18

 

[peverley]

Hi Dharmendra,

It seems you are having some memory issues. One thing you can try is, instead of running for X amount of time all at once, you can have the model stop and restart at intervals. For example, instead of running continuously for 1 year, you can instead run it for two months and have it restart 5 times (for a total of 12 months). To do this particular example:

./xmlchange STOP_N=2
./xmlchange STOP_OPTION=nmonths
./xmlchange RESUBMIT=5

Hope that helps.

Courtney

 

[dharmendraks841]

Hi Dharmendra,

It seems you are having some memory issues. One thing you can try is, instead of running for X amount of time all at once, you can have the model stop and restart at intervals. For example, instead of running continuously for 1 year, you can instead run it for two months and have it restart 5 times (for a total of 12 months). To do this particular example:



Hope that helps.

Courtney

Not work, and same error message. please try to resolve it if possible at your end.