[Wrf-users] Stack trace terminated abnormally

[Ahmad Wan]

Thank you everyone, 

I was pleasantly surprised that a lot of people replied to my last question (Re: [Wrf-users] Better strategy to compress wrf output files). I will definitely post some of you, if I have found another technique. Back to the issue, I have another problem with my control run, that after running for 2 years, it stopped abruptly with segmentation fault message:

Timing for main: time 1983-03-17_22:32:30 on domain   1:    0.30150 elapsed seconds.
Timing for main: time 1983-03-17_22:33:45 on domain   1:    0.30260 elapsed seconds.
forrtl: severe (174): SIGSEGV, segmentation fault occurred
Image              PC        Routine            Line        Source
wrf.exe            08D7C2A0  Unknown               Unknown  Unknown
wrf.exe            0864F0DC  Unknown               Unknown  Unknown
wrf.exe            0867B3B8  Unknown               Unknown  Unknown

Stack trace terminated abnormally.

For you information, I have already unlimited the stack size, and there is no apparent evidence of stability problems (such as warning messages or increasing elapsed seconds). Is it possible that my RAM is not enough? Or is it that some stability problems simply don't produce messages? I have tried the restart run twice, but they each stop at different times (3 months/5 months/1 month into the 2nd year)

Regards,
Wan Ardie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ucar.edu/pipermail/wrf-users/attachments/20120508/328bd4cf/attachment.html