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 stops half way

fipoucat

Member
My simulation stops after 2days 16hours with error messages rsl.error:

Timing for main: time 2022-06-02_16:02:46 on domain 2: 1.05082 elapsed seconds
corrupted double-linked list

Program received signal SIGABRT: Process abort signal.

Backtrace for this error:
#0 0x14a3cba23ad0 in ???
#1 0x14a3cba22c35 in ???
#2 0x14a3cae4251f in ???
at ./signal/../sysdeps/unix/sysv/linux/x86_64/libc_sigaction.c:0
#3 0x14a3cae96a7c in __pthread_kill_implementation
at ./nptl/pthread_kill.c:44
#4 0x14a3cae96a7c in __pthread_kill_internal
at ./nptl/pthread_kill.c:78
#5 0x14a3cae96a7c in __GI___pthread_kill
at ./nptl/pthread_kill.c:89
#6 0x14a3cae42475 in __GI_raise
at ../sysdeps/posix/raise.c:26
#7 0x14a3cae287f2 in __GI_abort
at ./stdlib/abort.c:79
#8 0x14a3cae896f5 in __libc_message
at ../sysdeps/posix/libc_fatal.c:155
#9 0x14a3caea0d7b in malloc_printerr
at ./malloc/malloc.c:5664
#10 0x14a3caea184b in unlink_chunk
at ./malloc/malloc.c:1635
#11 0x14a3caea46aa in _int_malloc
at ./malloc/malloc.c:4307
#12 0x14a3caea52e1 in __GI___libc_malloc
at ./malloc/malloc.c:3321
#13 0x5621e3a61242 in ???
#14 0x5621e3a682cd in ???
#15 0x5621e31a6762 in ???
#16 0x5621e268e63c in ???
#17 0x5621e1ecdf7e in ???
#18 0x5621e1cbd0ca in ???
#19 0x5621e0d031a3 in ???
#20 0x5621e0d03833 in ???
#21 0x5621e0d03833 in ???
#22 0x5621e0c84d37 in ???
#23 0x5621e0c841be in ???
#24 0x14a3cae29d8f in __libc_start_call_main
at ../sysdeps/nptl/libc_start_call_main.h:58
#25 0x14a3cae29e3f in __libc_start_main_impl
at ../csu/libc-start.c:392
#26 0x5621e0c841f4 in ???
#27 0xffffffffffffffff in ???
How to solve this? in case someone had this before
Thank you
 
Hi,
Does it always stop after 2 days, 16 hours, regardless of what time you start the simulation, or is it just this particular start time? It will be helpful if you can attach your namelist.input file, and then package all of your error/out files (e.g., rsl.error.* and rsl.out.*) together and attach them, as well. Thanks!
 
Top