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

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

L

Lue WANG

New member
Hello, I encountered a Segmentation fault error while running wrf.exe. When I tried to rerun using restart, the same error occurred. The error consistently appears in the file rsl.error.0049. I have attached my namelist file and all rsl files in the attachment.
The command I used to run WRF is: nohup mpirun -np 64 ./wrf.exe > wrf_output.log 2>&1 &
The meteorological data I used is hourly data from ERA5. With the same settings and region, I ran other time periods successfully without any errors.

Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Backtrace for this error:
#0 0x767ea2023960 in ???
#1 0x767ea2022ac5 in ???
#2 0x767ea1a4251f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3 0x57794a983a43 in ???
#4 0x57794a9889e3 in ???
#5 0x57794b0751ab in ???
#6 0x57794a7bdea0 in ???
#7 0x577949ca15f7 in ???
#8 0x5779494e2afe in ???
#9 0x5779492d1b3a in ???
#10 0x577948312727 in ???
#11 0x577948286d67 in ???
#12 0x5779482861ee in ???
#13 0x767ea1a29d8f in __libc_start_call_main
at ../sysdeps/nptl/libc_start_call_main.h:58
#14 0x767ea1a29e3f in __libc_start_main_impl
at ../csu/libc-start.c:392
#15 0x577948286224 in ???
#16 0xffffffffffffffff in ???
 

Attachments

  • namelist.input
    3.8 KB · Views: 4
  • namelist.wps
    1.5 KB · Views: 0
  • rsl.zip
    363.2 KB · Views: 2
  • wrf_output3.log
    3.6 KB · Views: 0
Your namelist.input looks fine.
RSL file indicates that this case crashed after about 18 hours of integration. I am suspicious that some physics/dynamics went wrong. Without clear error messages, it is hard to figure out the reason for the crash.
Can you recompile WRF in debug mode, i.e., ./clean -a, ./configure -D and recompile WRF? Then you can restart this case from the latest wrfrst file you saved from your previous run. The RSL file will tell exactly which variable goes wrong first and what place. That information will give you hints how to fix the issue.
 
Ming Chen said:
Your namelist.input looks fine.
RSL file indicates that this case crashed after about 18 hours of integration. I am suspicious that some physics/dynamics went wrong. Without clear error messages, it is hard to figure out the reason for the crash.
Can you recompile WRF in debug mode, i.e., ./clean -a, ./configure -D and recompile WRF? Then you can restart this case from the latest wrfrst file you saved from your previous run. The RSL file will tell exactly which variable goes wrong first and what place. That information will give you hints how to fix the issue.
Click to expand...
Hi, I recompiled WRF in debug mode, and restarted this case. I got new error:
Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.
I also tried other two cases both in same time periods, one with ERA5 hourly data but change time_step to 45s and one with FNL per 6 hours data. they both crashed with same error messages. It looks like that the error occurs in YSU PBL schemes. Does it mean that YSU is not suitable for this case? or some of my settings in namelist.input are not good?
I have tried to run cases with same settings for other time periods in 2018 and 2023 before, and it worked well.

Program received signal SIGFPE: Floating-point exception - erroneous arithmetic operation.

Backtrace for this error:
#0 0x78a0a2a23960 in ???
#1 0x78a0a2a22ac5 in ???
#2 0x78a0a264251f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3 0x5c0073761a6b in __module_bl_ysu_MOD_ysu2d
at /home/super/Build_WRF/WRF/phys/module_bl_ysu.f90:1144
#4 0x5c0073790392 in __module_bl_ysu_MOD_ysu
at /home/super/Build_WRF/WRF/phys/module_bl_ysu.f90:345
#5 0x5c0072e93cbe in __module_pbl_driver_MOD_pbl_driver
at /home/super/Build_WRF/WRF/phys/module_pbl_driver.f90:1202
#6 0x5c007186c149 in __module_first_rk_step_part1_MOD_first_rk_step_part1
at /home/super/Build_WRF/WRF/dyn_em/module_first_rk_step_part1.f90:629
#7 0x5c0070d0c828 in solve_em_
at /home/super/Build_WRF/WRF/dyn_em/solve_em.f90:973
#8 0x5c00709ec1c3 in solve_interface_
at /home/super/Build_WRF/WRF/share/solve_interface.f90:141
#9 0x5c006f2755dc in __module_integrate_MOD_integrate
at /home/super/Build_WRF/WRF/frame/module_integrate.f90:325
#10 0x5c006f27627c in __module_integrate_MOD_integrate
at /home/super/Build_WRF/WRF/frame/module_integrate.f90:362
#11 0x5c006f1f43d7 in __module_wrf_top_MOD_wrf_run
at ../main/module_wrf_top.f90:326
#12 0x5c006f1f2ff0 in wrf
at /home/super/Build_WRF/WRF/main/wrf.f90:29
#13 0x5c006f1f3054 in main
at /home/super/Build_WRF/WRF/main/wrf.f90:6
 
You must log in or register to reply here.
Top