Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

forrtl: error (78): process killed (SIGTERM)

xiyang

New member
Hello, I encountered an error of 'forrtl: error (78): process killed (SIGTERM)' when running a four layer nested domain. However, I can run a three layer nested domain without setting a 1km resolution. Please help me check where the problem may be. Here are the namelist. wps,namelist. input and rsl files.
 

Attachments

  • namelist (1).input
    4.5 KB · Views: 7
  • rsl.error.zip
    63.7 KB · Views: 3
  • rsl.out.zip
    52.3 KB · Views: 2
  • namelist (2).wps
    1.4 KB · Views: 1
Last edited:
In your namelist.input, the option below is not correct. For 3km and 1km resolution, cumulus scheme should be turned off.

cu_physics = 1, 1, 1, 1,

In addiiton to the segmentation fault, did you see other error messages? How long did the modle run before it crashed?
 
In your namelist.input, the option below is not correct. For 3km and 1km resolution, cumulus scheme should be turned off.

cu_physics = 1, 1, 1, 1,

In addiiton to the segmentation fault, did you see other error messages? How long did the modle run before it crashed?
Sorry for replying so late. I have tried to turn off the cumulus scheme with 3km and 1km resolutions, but still get the same error. In the rsl. error files, I only found the segmentation fault, and the model crashed 22 seconds after it started.
However, when I tried to run with single core on a virtual machine, the error displayed was:
Program received signal SIGSEGV: Segmentation fault - invalid memory reference
Backtrace for this error:
#0 0x7f1104e2ed11 in???
#1 0x7f1104e2dee5 in???
#2 0x7f1104a620bf in???
#3 0x561a5c24eb7d in???
#4 0x561a5c27d8e8 in???
#5 0x561a5c28c4b0 in???
#6 0x561a5bd3b5af in???
#7 0x7f1104c6b86d in???
#8 0x7f1104c19608 in start_ Thread
At/build/glibc-sMfBJT/glibc-2.31/nptl/pthread_ Create. c: 477
#9 0x7f1104b3e162 in???
#10 0xffffffffffffffffffff in???
Timing for main: time 2023-09-26_ 18: 00:22 on domain 4: 5.53903 lapsed seconds
Program received signal SIGSEGV: Segmentation fault - invalid memory reference
Backtrace for this error:
#0 0x7f5018a5ed11 in???
#1 0x7f5018a5dee5 in???
#2 0x7f50186920bf in???
#3 0x55e6a6574b7d in???
#4 0x55e6a65a38e8 in???
#5 0x55e6a65b24b0 in???
#6 0x55e6a60615af in???
#7 0x7f501889b86d in???
#8 0x7f5018849608 in start_ Thread
At/build/glibc-sMfBJT/glibc-2.31/nptl/pthread_ Create. c: 477
#9 0x7f501876e162 in???
#10 0xffffffffffffffffffff in???
===================================================================================
=BAD TERMINATION OF ONE OF YOUR APP PROCESS
=EXIT CODE: 139
=CLEANING UP REMAINING PROCESS
=YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
Dear Application Terminated With THE EXIT STRING: Segmentation fault (signal 11)
This typically refers to a problem with your application
Please see the FAQ page for debugging suggestions

Is there a problem with my compilation environment?
Any useful hints would be greatly appreciated.
 
Top