Skip to Content
Last modified by Carlijn Kokkeler on 2024/09/17 15:13
From version 11.1
edited by Tudor Neacsu
on 2024/06/21 09:31
Change comment: There is no comment for this version
To version 3.1
edited by Eva Torken
on 2024/03/22 15:42
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -Runtime Overview Exit codes
1 +No Data Delivered to Backend System
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.TudorNeacsu
1 +XWiki.etorken
Content
... ... @@ -1,34 +1,32 @@
1 1  {{container}}{{container layoutStyle="columns"}}(((
2 -In this microlearning, we will give insights into what is an exit code, the main exit codes returned by a container when it stops and how can that help a Support Engineer to conduct an RCA.
2 +In this document, we will use the information from the actual root cause analysis to make a generic view that can be used if you run into the same or a similar problem in the future. Finally, the document will describe the situation, the problem, the analysis, and the result.
3 3  
4 4  Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
5 5  
6 -== 1. Key concepts ==
6 +== 1. Situation ==
7 7  
8 - In a previous [[microlearning>>https://docs.emagiz.com/bin/view/Main/eMagiz%20Academy/Microlearnings/Crash%20Course/Crash%20Course%20Platform/Runtime%20Overview||target="blank"]] we explained that a container can have multiple statuses. Among these, there is the status Exit. This status comes together with a code. The exit code usually points out the reason why the container stopped. In the section below we go into more details for the most common exit codes that you could see in eMagiz.
8 +No data is delivered to a backend system.
9 9  
10 -[[image:Main.Images.RCA-Knowledgebase.WebHome@rca-knowledgebase-runtime-overview-exit-codes.png]]
10 +== 2. Problem ==
11 11  
12 -== 2. Exit code values ==
12 +The problem in this case was that the backend system was not receiving any data. This was caused by an unstable H2 database.
13 13  
14 -* Exited with code **0**: The application inside the container completed its work successfully without any errors.
14 +== 3. Analysis ==
15 15  
16 -* Exited with code **1**: There was a general error in the application, which could be due to a variety of reasons like incorrect arguments or a failed dependency.
16 +=== 3.1 Reproduction ===
17 17  
18 -* Exited with code **125**: The docker run command was not executed successfully
18 +N/A
19 19  
20 -* Exited with code **126**: The command inside the container was found but cannot be executed. This can be due to permission issues or if the command is not executable.
20 +=== 3.2 Analysis ===
21 21  
22 -* Exited with code **127**: The command was not found. This usually happens if a script is missing or the path is not set correctly.
22 +The problem led us to investigate the health of the H2 database. The database had a very high CPU and had high CPU after the connector underwent auto-healing. After further investigation it seemed that the H2 was reprocessing messages and therefore not taking on new ones.
23 23  
24 -* Exited with code **137**: The container was forcefully stopped. This happens when the container exceeds its memory resource limit (OOM)
24 +== 4. Result ==
25 25  
26 -* Exited with code **139**: The application inside the container crashed due to a segmentation fault, which is usually caused by accessing memory that the process does not have permission to access.
27 -
28 -* Exited with code **255**: Container exited, returning an exit code outside the acceptable range, meaning the cause of the error is not known
26 +The removal and re-addition of the H2 database caused the H2 database to return to normal behavior. Afterwards, the problem did not reoccur.
29 29  
30 -
31 31  == 5. Suggested Additional Readings ==
29 +N/A
32 32  
33 33  
34 34  )))((({{toc/}}))){{/container}}{{/container}}