Skip to Content
Last modified by Erik Bakker on 2024/02/22 12:36
From version 4.1
edited by eMagiz
on 2022/05/05 09:56
Change comment: There is no comment for this version
To version 14.1
edited by Erik Bakker
on 2023/09/28 21:00
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,0 +1,1 @@
1 +Interpreting wrapper.log on-premise
Parent
... ... @@ -1,0 +1,1 @@
1 +WebHome
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.marijn
1 +XWiki.ebakker
Content
... ... @@ -1,32 +1,18 @@
1 -{{html wiki="true"}}
2 -<div class="ez-academy">
3 - <div class="ez-academy_body">
4 -
5 -
6 - <li class="doc-nav__item"><a href="../../docs/microlearning/advanced-advanced-monitoring-index" class="doc-nav__link">Home</a></li>
7 -
8 -
9 -
10 -
11 -
1 +{{container}}{{container layoutStyle="columns"}}(((
2 +{{error}}
3 +Note that the functionality mentioned in this microlearning will become obsolete when migrating to the 3rd generation runtime.
4 +{{/error}}
12 12  
13 -<div class="doc">
14 -
15 -
16 -
17 -= Interpreting wrapper.log on-premise =
18 -
19 19  There is a need to see runtime level logging in cases where it is unclear whether that specific runtime has started up or not. In eMagiz, you won't receive logging if the start-up fails because no established connection can send logging to eMagiz. When this particular runtime runs on-premises, you can see that specific logging on the runtime in the wrapper.log. In this microlearning, we will learn how to find the wrapper log and search within the wrapper log to find the corresponding error and subsequently analyze that error.
20 20  
21 -Should you have any questions, please get in touch with academy@emagiz.com.
8 +Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]].
22 22  
23 -* Last update: November 15st, 2021
24 -* Required reading time: 5 minutes
25 -
26 26  == 1. Prerequisites ==
11 +
27 27  * Advanced knowledge of the eMagiz platform
28 28  
29 29  == 2. Key concepts ==
15 +
30 30  This microlearning centers around interpreting the wrapper.log for an on-premise runtime
31 31  With a wrapper.log, we mean: A file that holds start-up and shut down information on a specific runtime
32 32  
... ... @@ -36,9 +36,6 @@
36 36  * Shutdown information on JVM level
37 37  * Errors on start-up or shutdown
38 38  
39 -
40 -
41 -
42 42  == 3. Interpreting wrapper.log on-premise ==
43 43  
44 44  There is a need to see runtime level logging in cases where it is unclear whether that specific runtime has started up or not. In eMagiz, you won't receive logging if the start-up fails because no established connection can send logging to eMagiz. When this particular runtime runs on-premises, you can see that specific logging on the runtime in the wrapper.log. In this microlearning, we will learn how to find the wrapper log and search within the wrapper log to find the corresponding error and subsequently analyze that error.
... ... @@ -53,7 +53,7 @@
53 53  
54 54  Before we can interpret the wrapper.log, the first action will be to find the wrapper.log. The wrapper.log is available within the data folder of each eMagiz runtime that is running on-premises. To see it, you first need to know the location where you saved and unpacked the runtime zips. Suppose you open the runtime you want to interpret the wrapper log and open the data folder. Within the data folder, there is a folder called log. You will see a file called wrapper which can be opened with a tool such as Notepad++.
55 55  
56 -<p align="center">[[image:advanced-advanced-monitoring-interpreting-wrapper-log-on-premise--wrapper-log-location.png||]]</p>
39 +[[image:Main.Images.Microlearning.WebHome@advanced-advanced-monitoring-interpreting-wrapper-log-on-premise--wrapper-log-location.png]]
57 57  
58 58  === 3.2 Find additional information ===
59 59  
... ... @@ -61,31 +61,12 @@
61 61  
62 62  One way to do so would be to stop the runtime and delete the data folder without deleting the h2 folder. That would initiate a clean restart of the runtime to alleviate the problems. In case of structural issues, you should dive into the logging and analyze the issues in more detail.
63 63  
64 -===== Practice =====
47 +== 45. Key takeaways ==
65 65  
66 -== 4. Assignment ==
67 -
68 -Run your own Academy project on your laptop (on-premise), so you can experiment a bit with analyzing the karaf.log on-premise. This assignment can be completed with the help of the (Academy) project that you have created/used in the previous assignment.
69 -
70 -== 5. Key takeaways ==
71 -
72 -* The karaf.log can be found within the folder called log under the folder data
49 +* The wrapper.log can be found within the folder called log under the folder data
73 73  * You can search the log with the help of tools such as Notepad++
74 74  * By looking at the timestamp in the eMagiz Manage Log, you can run a focused search
75 75  
53 +== 5. Suggested Additional Readings ==
76 76  
77 -
78 -== 6. Suggested Additional Readings ==
79 -
80 -No suggested additional readings for this microlearning.
81 -
82 -== 7. Silent demonstration video ==
83 -
84 -As this is a more theoretical microlearning, we have no video for this.
85 -
86 -
87 -</div>
88 -</main>
89 -</div>
90 -</div>
91 -{{/html}}
55 +No suggested additional readings for this microlearning.)))((({{toc/}}))){{/container}}{{/container}}
advanced-advanced-monitoring-interpreting-wrapper-log-on-premise--wrapper-log-location.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.marijn
Size
... ... @@ -1,1 +1,0 @@
1 -35.8 KB
Content