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

Error on model day 2 00:30:00 while running wrf.exe forrtl: severe (174): SIGSEGV, segmentation fault occurred

nikhilhale

New member
I am using WPS-4.2 and polar version of WRF 4.1.3. I pre-processed ERA5 data using WPS-4.2, obtained met_em* files and use those to run polar WRF-4.1.3 from model date Feb 01, 2013, 00:00:00. But on model date Feb 02, 2013 00:30:00, I encounter the following error.
Timing for main: time 2013-02-02_00:30:00 on domain 1: 0.54954 elapsed seconds
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image PC Routine Line Source
wrf.exe 0000000023035E1A for__signal_handl Unknown Unknown
libpthread-2.31.s 0000155551BB68C0 Unknown Unknown Unknown
wrf.exe 0000000021F90A7D Unknown Unknown Unknown
wrf.exe 0000000021F6FE71 Unknown Unknown Unknown
wrf.exe 0000000021F67A16 Unknown Unknown Unknown
wrf.exe 0000000021F5787D Unknown Unknown Unknown
wrf.exe 0000000021681F41 Unknown Unknown Unknown
wrf.exe 0000000021A3E138 Unknown Unknown Unknown
wrf.exe 00000000210CCEC0 Unknown Unknown Unknown
wrf.exe 0000000020E98790 Unknown Unknown Unknown
wrf.exe 000000002016702B Unknown Unknown Unknown
wrf.exe 00000000200176D1 Unknown Unknown Unknown
wrf.exe 0000000020017684 Unknown Unknown Unknown
wrf.exe 0000000020017612 Unknown Unknown Unknown
libc-2.31.so 00001555517E029D __libc_start_main Unknown Unknown
wrf.exe 000000002001752A Unknown Unknown Unknown


I have attached the rsl.error.0000 file and the namelist.input.

Can you please help me figure out what's going wrong?
 
This error message is not helpful. I would suggest that you recompile WRF-Polar in debug mode, i.e., ./configure -D, then rerun this case. The log file will tell exactly when and where the model first crash, which will give you some clues what is wrong.

Also, please talk to people in Polar WRF group, since they made quite a few modifications of WRF.
 
Top