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

CESM2.1.3 was killed in./case.submit

yongsheng zheng

Yongsheng zheng
Member
When I was using CESM2.1.3, I created a compset_QPC6 that aborted when the case was forcibly killed at./case.submit. The following are the aborted details, the runlog and my CESM2.1.3 configuration file.

[zys@zys compset_QPC6]$ tail -n 50 /home/zys/cesm_files/output/compset_QPC6/run/cesm.log.240520-172935
cesm.exe 000000000043345B cime_comp_mod_mp_ 1231 cime_comp_mod.F90
cesm.exe 0000000000441CE9 MAIN__ 114 cime_driver.F90
cesm.exe 00000000004242E2 Unknown Unknown Unknown
libc-2.17.so 00007FA9FC8C0555 __libc_start_main Unknown Unknown
cesm.exe 00000000004241E9 Unknown Unknown Unknown
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
cesm.exe 0000000001BAD0AA Unknown Unknown Unknown
libpthread-2.17.s 00007FED924E8630 Unknown Unknown Unknown
cesm.exe 00000000012849B0 mo_drydep_mp_inte 2320 mo_drydep.F90
cesm.exe 0000000001281DAC mo_drydep_mp_dvel 1927 mo_drydep.F90
cesm.exe 0000000001264D40 mo_chemini_mp_che 188 mo_chemini.F90
cesm.exe 00000000010D3206 chemistry_mp_chem 882 chemistry.F90
cesm.exe 00000000006ECF42 physpkg_mp_phys_i 822 physpkg.F90
cesm.exe 000000000050DF86 cam_comp_mp_cam_i 201 cam_comp.F90
cesm.exe 0000000000505797 atm_comp_mct_mp_a 209 atm_comp_mct.F90
cesm.exe 0000000000444CD3 component_mod_mp_ 267 component_mod.F90
cesm.exe 000000000043345B cime_comp_mod_mp_ 1231 cime_comp_mod.F90
cesm.exe 0000000000441CE9 MAIN__ 114 cime_driver.F90
cesm.exe 00000000004242E2 Unknown Unknown Unknown
libc-2.17.so 00007FED91E2B555 __libc_start_main Unknown Unknown
cesm.exe 00000000004241E9 Unknown Unknown Unknown
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
cesm.exe 0000000001BAD0AA Unknown Unknown Unknown
libpthread-2.17.s 00007FA1B80CB630 Unknown Unknown Unknown
cesm.exe 00000000012849B0 mo_drydep_mp_inte 2320 mo_drydep.F90
cesm.exe 0000000001281DAC mo_drydep_mp_dvel 1927 mo_drydep.F90
cesm.exe 0000000001264D40 mo_chemini_mp_che 188 mo_chemini.F90
cesm.exe 00000000010D3206 chemistry_mp_chem 882 chemistry.F90
cesm.exe 00000000006ECF42 physpkg_mp_phys_i 822 physpkg.F90
cesm.exe 000000000050DF86 cam_comp_mp_cam_i 201 cam_comp.F90
cesm.exe 0000000000505797 atm_comp_mct_mp_a 209 atm_comp_mct.F90
cesm.exe 0000000000444CD3 component_mod_mp_ 267 component_mod.F90
cesm.exe 000000000043345B cime_comp_mod_mp_ 1231 cime_comp_mod.F90
cesm.exe 0000000000441CE9 MAIN__ 114 cime_driver.F90
cesm.exe 00000000004242E2 Unknown Unknown Unknown
libc-2.17.so 00007FA1B7A0E555 __libc_start_main Unknown Unknown
cesm.exe 00000000004241E9 Unknown Unknown Unknown

===================================================================================
= BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
= PID 13806 RUNNING AT zys
= EXIT CODE: 9
= CLEANING UP REMAINING PROCESSES
= YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR APPLICATION TERMINATED WITH THE EXIT STRING: Killed (signal 9)
This typically refers to a problem with your application.
Please see the FAQ page for debugging suggestions
 

Attachments

  • cesm.log.240520-172935.txt
    93.3 KB · Views: 4
  • config_machines.xml.txt
    1.7 KB · Views: 0
  • config_compilers.xml.txt
    1.2 KB · Views: 0
  • config_batchs.xml.txt
    131 bytes · Views: 0
Top