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

Exit_status=265 or 137, no error log

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.

zmenzo

Member
Hello,

I am successfully creating a static.nc file. However, when I try to create an init.nc file, the process stops at the same point, regardless of the options I choose. Unfortunately, an error log is not created, making troubleshooting difficult. The only hint I have is the Exit Status of 265 or 137. Yet, without knowing what those mean, I am at a loss of what to do next. Do you have any ideas on what these statuses could be suggesting? Attached is a screenshot of the point where my init_amtopshere executable stops each time.

Thank you in advance for your continued assistance.

Zach
 

Attachments

  • stopping.png
    stopping.png
    467.2 KB · Views: 1,245
I think exit codes that are greater than or equal to 128 indicate the job was killed by a signal (see Section 14.9.3 of the PBS Administrator's Guide). So an exit code of 137 suggests the job was terminated with a signal 9 (SIGKILL). As I mentioned in this thread, it may be that your job is running out of memory. Can you try the job on, say, four nodes to see if that resolves the issue?
 
Top