Menu
My C++ application crashes periodically. It writes Terminated in terminal and stops. I have no idea what is the reason (gdb is not solution, it is mutithreaded application, and error appears on big amount of threads only that gdb can not process due to its low performance). What does exit code 143 mean on CentOS Linux? Does it contain information about the reason of the crash?
231
Exit Code 143 happens due to multiple reasons and one of them is related to Memory/GC issues. Your default Mapper/reducer memory setting may not be sufficient to run the large data set. Thus, try setting up higher AM, MAP and REDUCER memory when a large yarn job is invoked.
Exit Code 143 means that the container received a SIGTERM signal from the operating system, which asks the container to gracefully terminate, and the container succeeded in gracefully terminating (otherwise you will see Exit Code 137).
This error indicates that the process has been killed using the kill command.
An exit code or exit status is a number that is returned by an executable to show whether it was successful. This is also sometimes called a return code, or in some cases, an error code, although the terminology here may be slightly different.
143 usually means the application caught a SIGTERM signal, meaning the process was killed. This could be because another process killed it, or perhaps because the operating system killed it for using too much memory or some other resource, etc. Without more information, it's hard to know.
191
There are some exit codes which have either defined or generally agreed upon meaning.
In case of 143, which is 128 + 15, that means program died with signal 15, which is SIGTERM
According to the above table, exit codes 1 - 2, 126 - 165, and 255 have special meanings, and should therefore be avoided for user-specified exit parameters.
See the table at http://www.tldp.org/LDP/abs/html/exitcodes.html
38
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
