Can someone please explain the OpenPLi log level system, and what commands are required to get python printing full debug when in console mode.
Log level
Started by Huevos, 03 Jun 2017 15:21
13 replies to this topic
Re: Log level #2
-
- Senior Member
- 1,255 posts
+86
Good
Posted 3 June 2017 - 15:39
try
ENIGMA_DEBUG_LVL=4 enigma2
have a look into at tje log
Distro: openpli
Version:
Build:
Brand: Vu+
Boxtype: mbmini
Machine: Ultimo
Drivers:
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA2_DEBUG settings: Level=4
.................................
.................................
ENIGMA_DEBUG_LVL=4 enigma2
have a look into at tje log
Distro: openpli
Version:
Build:
Brand: Vu+
Boxtype: mbmini
Machine: Ultimo
Drivers:
PYTHONPATH: /usr/lib/enigma2/python
DVB_API_VERSION 5 DVB_API_VERSION_MINOR 10
ENIGMA2_DEBUG settings: Level=4
.................................
.................................
Re: Log level #3
-
- PLi® Core member
- 7,185 posts
+323
Excellent
Posted 3 June 2017 - 15:41
init 4 ENIGMA_DEBUG_LVL=4 enigma2
This sets log level to 4 (= Debug). Default is 3 (= Info).
Xtrend ET-9200, ET-8000, ET-10000, OpenPliPC on Ubuntu 12.04
Re: Log level #4
-
- Senior Member
- 195 posts
+4
Neutral
Posted 24 September 2018 - 18:31
and where change , if need high level before init 4 in console ?
Edited by EnoSat, 24 September 2018 - 18:31.
Re: Log level #5
-
- PLi® Contributor
- 6,155 posts
+261
Excellent
Posted 24 September 2018 - 20:00
Hi,
Explanation is also on the wiki:
https://wiki.openpli...ebugging_Enigma
The higher output level is not supposed to be used in "production" so if you have a problem, connect in telnet enable the debug log and try to reproduce the problem.
Once you have the needed logs to report the bug then type:
init 3
And enigma2 will restart in its normal debug level.
Pr2
NO SUPPORT by PM, it is a forum make your question public so everybody can benefit from the question/answer.
If you think that my answer helps you, you can press the up arrow in bottom right of the answer.
Wanna help with OpenPLi Translation? Please read our Wiki Information for translators
Sat: Hotbird 13.0E, Astra 19.2E, Eutelsat5A 5.0W
VU+ Solo 4K: 2*DVB-S2 + 2*DVB-C/T/T2 (used in DVB-C) & Duo 4K: 2*DVB-S2X + DVB-C (FBC)
AB-Com: PULSe 4K 1*DVB-S2X (+ DVB-C/T/T2)
Edision OS Mio 4K: 1*DVB-S2X + 1*DVB-C/T/T2
Re: Log level #6
-
- PLi® Core member
- 56,968 posts
+696
Excellent
Posted 24 September 2018 - 20:35
I’m planning to add a function restart enigma in debug mode (where we set the level to e.g. 6)... and when enigma2 crashes it auto restarts in debug mode..
Edited by littlesat, 24 September 2018 - 20:36.
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Log level #7
-
- Senior Member
- 195 posts
+4
Neutral
Posted 2 December 2018 - 21:37
I’m planning to add a function restart enigma in debug mode (where we set the level to e.g. 6)... and when enigma2 crashes it auto restarts in debug mode..
woow 
Re: Log level #8
-
- PLi® Core member
- 56,968 posts
+696
Excellent
Posted 2 December 2018 - 22:14
It’s already done... but at this moment it only ‘logs’ at a crash....
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Log level #9
-
- PLi® Core member
- 14,054 posts
+298
Excellent
Posted 3 December 2018 - 18:48
Note that debug output above MAX_DEBUG_LEVEL (defined as "4" by default) will be compiled-out, so to see those, you'll need to compile your own version of enigma2. Setting the debug level to anything above "5" will not actually work on normal releases.
Real musicians never die - they just decompose
Re: Log level #10
-
- PLi® Core member
- 56,968 posts
+696
Excellent
Posted 3 December 2018 - 19:32
Mmm can’t we just make that max a bit higher?
WaveFrontier 28.2E | 23.5E | 19.2E | 16E | 13E | 10/9E | 7E | 5E | 1W | 4/5W | 15W
Re: Log level #11
-
- Senior Member
- 195 posts
+4
Neutral
Posted 26 July 2023 - 18:26
Hi,
Explanation is also on the wiki:
https://wiki.openpli...ebugging_Enigma
The higher output level is not supposed to be used in "production" so if you have a problem, connect in telnet enable the debug log and try to reproduce the problem.
Once you have the needed logs to report the bug then type:
init 3
And enigma2 will restart in its normal debug level.
Pr2
wiki is down again
Re: Log level #12
-
- PLi® Core member
- 69,935 posts
+1,788
Excellent
Posted 26 July 2023 - 19:00
It's monitored 24/7 (both the server directly and the sites from a server in another country), and no issues where reported.
What is your definition of "down"? Is the forum reachable at the same time (they run on the same server)?
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
Re: Log level #13
-
- Senior Member
- 195 posts
+4
Neutral
Posted 27 July 2023 - 11:42
It's okay now. Yesterday when I clicked on the WIKI only the main page was displayed (openpli.org).
Edited by EnoSat, 27 July 2023 - 11:43.
Re: Log level #14
-
- PLi® Core member
- 69,935 posts
+1,788
Excellent
Posted 27 July 2023 - 14:57
That might be a cookie blocking issue locally.
If the GPDR cookie is not accepted (i.e. not present), all our sites redirect you to the main homepage where you need to accept it (is shown in a red bar at the top op te screen).
Currently in use: VU+ Duo 4K (2xFBC S2), VU+ Solo 4K (1xFBC S2), uClan Usytm 4K Ultimate (S2+T2), Octagon SF8008 (S2+T2), Zgemma H9.2H (S2+T2)
Due to my bad health, I will not be very active at times and may be slow to respond. I will not read the forum or PM on a regular basis.
Many answers to your question can be found in our new and improved wiki.
4 user(s) are reading this topic
0 members, 4 guests, 0 anonymous users
