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

wrf.exe error

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

enoma3169

New member
Dear all.

I got a problem during running wrf.exe.
when i run wrf.exe below message keep appear.
Code:
===================================================================================
=   BAD TERMINATION OF ONE OF YOUR APPLICATION PROCESSES
=   EXIT CODE: 139
=   CLEANING UP REMAINING PROCESSES
=   YOU CAN IGNORE THE BELOW CLEANUP MESSAGES
===================================================================================
YOUR 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

so i typed 'tail rsl.error.0000' command. and i got message below.
Code:
#2  0x1484B89E44AF
#3  0x233FF1D in __module_sf_sfclayrev_MOD_psim_stable
#4  0x23448B0 in __module_sf_sfclayrev_MOD_sfclayrev1d
#5  0x2348B81 in __module_sf_sfclayrev_MOD_sfclayrev
#6  0x1BBAC45 in __module_surface_driver_MOD_surface_driver
#7  0x1528E99 in __module_first_rk_step_part1_MOD_first_rk_step_part1
#8  0x10B322E in solve_em_
#9  0xFA8ABC in solve_interface_
#10  0x46B8FC in __module_integrate_MOD_integrate
#11  0x407D33 in __module_wrf_top_MOD_wrf_run

I typed 'limit stacksize unlimited' and re-ran wrf.exe. but same error keep accur.
what should i do?

I want to run 7days of simulation days and I attached namelist.input code.
 

Attachments

  • namelist.input
    4.6 KB · Views: 82
Hi,
Can you package all of your rsl* files into a single *.TAR file and attach that so that I can take a look? Thanks!
 
I really appreciate for your reply.
here is rsl* files.
Thank you very much.
 

Attachments

  • rsl_files.tar
    90.5 KB · Views: 77
Thanks for sending those. One of the most common reasons for a segmentation fault is CFL errors. If you search your rsl* files:
Code:
grep cfl rsl.*
you'll see multiple statements like this printed out:
Code:
rsl.out.0007:d01 2016-08-24_03:01:20         1347  points exceeded cfl=2 in domain d01 at time 2016-08-24_03:01:20 hours
rsl.out.0007:d01 2016-08-24_03:01:20  MAX AT i,j,k:           79         133          32  vert_cfl,w,d(eta)=   3.42593384       33.4523697       1.32842744E-02
rsl.out.0007:d01 2016-08-24_03:01:20         1540  points exceeded cfl=2 in domain d01 at time 2016-08-24_03:01:20 hours
rsl.out.0007:d01 2016-08-24_03:01:20  MAX AT i,j,k:           79         133          40  vert_cfl,w,d(eta)=   45.9022675       51.6451378       5.77545585E-03
rsl.out.0007:d01 2016-08-24_03:01:40         1523  points exceeded cfl=2 in domain d01 at time 2016-08-24_03:01:40 hours
rsl.out.0007:d01 2016-08-24_03:01:40  MAX AT i,j,k:           41         134          31  vert_cfl,w,d(eta)=   3.05643082       0.00000000       1.47420028E-02
This indicates that the model has become unstable. Take a look at this FAQ that discusses seg-faults, and particularly some work-arounds for CFL errors: https://forum.mmm.ucar.edu/phpBB3/viewtopic.php?f=73&t=133
 
@Peeyush174,

I first would like to apologize for the long delay in response. I've been traveling for the past few weeks and am just now catching up on the forum inquiries. If you are still having problems, will you open a new inquiry and provide additional information (e.g., your error log files, namelist, version, etc.)? Thanks!
 
Top