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

iCESM1_2_0_1. "no cpl.log file" when running a case (a port to a new machine)

L

liuxiaoqing

Xiaoqing Liu
New Member
I'm porting iCESM1_2_0_1 on a new machine, and an error "cpl.log.220920-112559: No such file or directory" showed up when running a case with the component set of X.
The attached zip file includes the related config/machines files and a cesm.log file showing the error. I'm using Intel Fortran Compiler 19.0.5 build 281. The following is the error from the log file after the initialization.

(seq_comm_printcomms) 25 0 4 1 GLC:
(seq_comm_printcomms) 26 0 4 1 CPLGLC:
(seq_comm_printcomms) 27 0 128 1 ROF:
(seq_comm_printcomms) 28 0 128 1 CPLROF:
(seq_comm_printcomms) 29 0 128 1 WAV:
(seq_comm_printcomms) 30 0 128 1 CPLWAV:
forrtl: No such file or directory
forrtl: severe (29): file not found, unit 99, file /cesm_caseroot/test1/run/cpl.log.220920-112559
Image PC Routine Line Source
cesm.exe 0000000000F3741B Unknown Unknown Unknown
cesm.exe 0000000000F556F0 Unknown Unknown Unknown
cesm.exe 0000000000896B91 shr_file_mod_mp_s 894 shr_file_mod.F90
cesm.exe 00000000004259FF ccsm_comp_mod_mp_ 784 ccsm_comp_mod.F90
cesm.exe 0000000000502EC1 MAIN__ 47 ccsm_driver.F90
cesm.exe 0000000000414EA2 Unknown Unknown Unknown
libc-2.17.so 00002AD20F7C4555 __libc_start_main Unknown Unknown
cesm.exe 0000000000414DA9 Unknown Unknown Unknown
srun: error: bell-a027: task 0: Exited with exit code 29
srun: Terminating job step 20290099.0
 

Attachments

  • CaseX.zip
    32 KB · Views: 2
L

liuxiaoqing

Xiaoqing Liu
New Member
jedwards said:
none at this time.
Click to expand...
I solved this issue. The run directory I set is $RCAC_SCRATCH/cesm_caseroot/$CASE/run, and $RCAC_SCRATCH is the scratch directory path on Purdue's cluster, but somehow $RCAC_SCRATCH was not working, so I changed it to the absolute path. Then it works.

I'm still working on porting and using compset B1850C5CN for testing, and the restart file I used is b.e12.B1850C5CN.f19_g16.iPI.01.
I put this file in the run directory, I changed RUB_REFCASE and RUN_REFDATE, and set GET_REFCASE to FALSE. Then, I built and ran the case. When running the case, I got the errors saying "(shr_sys_abort) ERROR: GETFIL: FAILED to get b.e12.B1850C5CN.f19_g16.iPI.01.cam.i.0511-01-01-00000.nc" and "(shr_sys_abort) WARNING: calling shr_mpi_abort() and stopping". Any suggestions to fix the errors?
 
J

jedwards

CSEG and Liaisons
Staff member
I'm not sure - one possible issue is that the run directory is not available on all of your compute nodes, but it seems like if that were the problem you would see other errors before you got to this point.
 
L

liuxiaoqing

Xiaoqing Liu
New Member
jedwards said:
I'm not sure - one possible issue is that the run directory is not available on all of your compute nodes, but it seems like if that were the problem you would see other errors before you got to this point.
Click to expand...
I see. Thanks for your help and quick reply.
 
L

liuxiaoqing

Xiaoqing Liu
New Member
jedwards said:
I'm not sure - one possible issue is that the run directory is not available on all of your compute nodes, but it seems like if that were the problem you would see other errors before you got to this point.
Click to expand...
I put the restart file in the directory of the input data, the GETFIL error disappeared, but I got a new error "forrtl: severe (408): fort: (8): Attempt to fetch from allocatable variable REGION_G when it is not allocated". What does this error mean?
 
Q

Qubl-ouc

Binglin Qu
New Member
liuxiaoqing said:
I put the restart file in the directory of the input data, the GETFIL error disappeared, but I got a new error "forrtl: severe (408): fort: (8): Attempt to fetch from allocatable variable REGION_G when it is not allocated". What does this error mean?
Click to expand...
Dear Liu,
I have a similar problem to yours. Did you solve this problem in the past weeks?
 
L

liuxiaoqing

Xiaoqing Liu
New Member
Qubl-ouc said:
Dear Liu,
I have a similar problem to yours. Did you solve this problem in the past weeks?
Click to expand...
This issue was resolved, but I did not record how I resolved it, since some other errors also showed up. If you're using iCESM1.2, I would recommend to follow the instructions here
 
You must log in or register to reply here.
Top