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

After ndown get SIGTERM error

yenehnglin

New member
Hi,
I am running WRF 4.6 with 30 km (time_step = 180) and 6 km (time_step = 36) and encountering rsl.error.0000: "forrtl: error (78): process killed (SIGTERM)" and rsl.error.0140: "forrtl: severe (174): SIGSEGV, segmentation fault occurred" when I attempt to run wrf.exe after ndown.exe.

However, I can run two domains simultaneously without issues.
Additionally, when I run domain 02 after ndown.exe with time_step = 12, it operates correctly. I wonder what the possible reasons are for the errors I encounter when using time_step = 36 after ndown.



Thank you.
 
Wow I am having the same error messages. Can you specify more about how you changed the domain sizes? Thanks.
 
@xjhuang and @sophiazjjj
A segmentation fault is a very generic error that can be caused by an array of different things. Your issues are likely not the same as the one originally posted to this thread. Please open new threads to describe your issue, and it helps if you attach your error logs (all rsl* files packed into a single *.tar file) and your namelist.input, in your new threads. Thanks!
 
Top