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

CESM122 error with SIGSEGV, segmentation fault occurred

N

Nithish

Nithish_Sriramoju
New Member
Hello everyone,

I'm using the CESM 122 version for my work. I'm running a 100-year simulation with user-defined COMPSET "2000_CAM5_CLM45_CICE_DOCN%SOM_RTM_SGLC_SWAV" and setting CCSM_CO2_PPMV=400. My simulation ran for 51 years, then suddenly it halted, prompting an error saying "forrtl: severe (174): SIGSEGV, segmentation fault occurred". Then I restarted it with CONTINUE_RUN="TRUE", but the issue persists after running for a year, and I'm unable to resolve this issue. I read other threads with the same error, for which most suggested answers are changing DEBUG to True (but I don't want to restart the whole experiment again, as it is halfway through) and checking input data (model ran for 52 years, so input data is OK).

Any insights on this issue will be greatly appreciated!

I have attached the CESM logfile and atm logfile for reference, as cam and atm .f90 files are mentioned in error.

Thank you.
 

Attachments

  • cesm.log.251106-020448.txt
    604.5 KB · Views: 3
  • atm.log.251106-020448.txt
    315.6 KB · Views: 3
Sort by date Sort by votes
slevis

slevis

Moderator
Staff member
You mention that "input data is OK" which makes me wonder whether you are using custom input data rather than defaults. Also did you make changes to the code?
 
Vote Upvote 0 Downvote
N

Nithish

Nithish_Sriramoju
New Member
Hello slevis,

I’m using the default input data, and I haven’t made any changes to the source code except for adding the "cd $CASEROOT" command in the short-term archiving section.

When I mentioned that “the input data is OK,” I meant that since the model successfully ran for 52 years, the input data is unlikely to be corrupted.
 
Vote Upvote 0 Downvote
O

oleson

Keith Oleson
CSEG and Liaisons
Staff member
I'm moving this to the CAM Forum because it looks like the error is occurring in the CAM code p_d_adjust.F90 in a call to shr_reprosum_calc. Maybe they have seen this type of error before.
 
Vote Upvote 0 Downvote
P

peverley

Courtney Peverley
Moderator
Staff member
Hi Nithish,

Is it possible for you to update to the CESM2 series? We no longer support CESM1 outside of deep time paleoclimate uses. If you update to CESM2 I can help you further; if that's not possible, I would recommend following through with the idea you've been trying to avoid, and changing to DEBUG=true to see if you get more information.

Sorry I could not be more helpful at this time!
Courtney
 
Vote Upvote 0 Downvote
You must log in or register to reply here.
Top