- 23 Jan 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Troubleshooting Non-zero exit status 137
- Updated on 23 Jan 2024
- 1 Minute to read
- Print
- DarkLight
- PDF
Introduction
Problem description
On Premise processing fails and displays the error code on your computer: Non-zero exit 137. Returned.
Checking the log file
This error code is associated with a memory issue.
The error message is displayed when the amount of RAM in the computer is too low for the size of the dataset.
You can check the RAM size listed in the post-processing log after the processing starts with the minutes included in the dataset.
Specifically, the processing log can be found under the following path:
/PATH/TO/datasets_proc/2023-MM-DD_HH.MM.SS/logs/processing.log
Around 37th line of the processing log there listed the host system's resource overview, by searching the keyword “Host” one can also find this section.
Host:
CPU: logical cores: 96 / physical cores: 48 / allocated cores: 24
Memory: physical: 186.9 GiB, available: 172.3 GiB, 8% used,
allocated memory: 44.9 GiB
Storage: total: 480.0 GiB, used: 35.2 GiB, free: 444.8 GiB, 7% used
System Specification Recommendations
The amount of physical memory of the computer you are using to process the data is very important, shown here are the system specification recommendations:
For short NavVis M6 mappings: ~32GB RAM is necessary.
For long NavVis M6 mappings: ~64GB RAM is necessary.
For NavVis VLX 1/2 mappings: 64GB RAM is minimum, 128 GB RAM is recommended.
For NavVis VLX 3 mappings: 128 GB RAM is minimum, 192 GB RAM is recommended.
Troubleshooting procedure
Perform the following steps to clear the error message, after each step try reprocessing the data, and check to see if the error message has been cleared.
Clear some RAM memory in your device.
Process the dataset using another device that has more RAM installed.
If possible, try to process the data at a larger resolution e.g. at 10mm or larger, rather than at 5mm.
Split the data set in half at a logical break in the data set, refer to nv cut database for details on how to perform this step.