Gigablue UE 4k crash.
Re: Gigablue UE 4k crash. #2
Posted 26 December 2018 - 15:52
<3>[ 271.170013] Out of memory: Kill process 1729 (enigma2) score 836 or sacrifice child
What are you doing that makes a high-end box like that run out of memory?
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: Gigablue UE 4k crash. #3
Posted 26 December 2018 - 16:00
I do nothing extraordinary. There is installed just few plugins and softcam ( oscam-emu latest) from feed.
Maybe in some case oscam restart with unknow command ant restart also the box gui. It is possible every restart generate a new instance of oscam and fill up the ram ? Just ask a dunno. Thank you
Re: Gigablue UE 4k crash. #4
Posted 26 December 2018 - 16:05
I doubt Oscam is causing this, it tends to be very stable.
Login to the box with telnet, and enter the command "top -m" to show memory usage. Make a screenshot and post that here so we can have a look.
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: Gigablue UE 4k crash. #5
Re: Gigablue UE 4k crash. #6
Posted 26 December 2018 - 18:02
Thanks. Nothing out of the ordinary here, but I miss the top line, which looks like this:
Mem total:567932 anon:112492 map:36240 free:271188
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: Gigablue UE 4k crash. #7
Re: Gigablue UE 4k crash. #8
Posted 26 December 2018 - 20:23
That could not cause an "out of memory" (RAM), but an "out of disk space" in flash.
The interesting bit in the log is:
<4>[ 34.552876] oscam-emu invoked oom-killer: gfp_mask=0x200da, order=0, oom_score_adj=0
which suggests that oscam-emu is eating up all memory, as it already crashes after 34 seconds.
Is that the oscam-emu from our feeds? ECM cache active?
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: Gigablue UE 4k crash. #9
Posted 26 December 2018 - 21:38
Hello,
Here is a capture of ssh session.
ECM cache ... where I have to check please advise me better in On or Off ?
About Oscam-emu is from feed 11443 if I remember right.
Error of oscam :
2018/12/24 19:30:35 5B97F315 c (dvbapi) E1
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0xDF00A0E1
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) DF
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0x00A0E1DF
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) 00
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0xA0E1DF00
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) A0
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0xE1DF00A0
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) E1
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0xDF00A0E1
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) DF
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0x00A0E1DF
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) 00
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0xA0E1DF00
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) A0
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown socket command received: 0xE1DF0000
2018/12/24 19:30:35 5B97F315 c (dvbapi) Unknown command:
2018/12/24 19:30:35 5B97F315 c (dvbapi) E1
Sorry I know here is no support for oscam just please give me advise.
Thank you
Attached Files
Edited by zajkas112, 26 December 2018 - 21:39.
Re: Gigablue UE 4k crash. #10
Posted 26 December 2018 - 21:55
That screenshot shows plenty of free memory.
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: Gigablue UE 4k crash. #11
Re: Gigablue UE 4k crash. #12
Posted 26 December 2018 - 23:20
This is not a log file, that is a link to a logfile.
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: Gigablue UE 4k crash. #13
Re: Gigablue UE 4k crash. #14
Re: Gigablue UE 4k crash. #15
Re: Gigablue UE 4k crash. #16
Posted 27 December 2018 - 14:17
In all cases it is the OOM killer that terminates Enigma due to lack of memory.
That is unlikely to be a bug, something is running on that box that eats up all available RAM, either on it's own, or as a plugin in Enigma.
The only two I know of are the ECM caching in Oscam (if configured wrong it can use large amounts of memory) and EPG in Enigma (which is all stored in memory). Having said that, the UE 4K is a modern box with tons of memory...
I would start with flashing the box again, do not restore a backup, do not install any plugin, just watch some FTA channel, and see what happens. If it remains stable, install the softcam, and check again. If it remains stable, install the first plugin from your list, repeat, until you have found the culprit.
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: Gigablue UE 4k crash. #17
Posted 27 December 2018 - 15:08
Hello and thank you for support. I made some check&fix on my config. ECM cahce =15s and bad CW is drop not loged or stored but other interesting config is about oscam stream relay wich was on now it is disabled. EPG is just for future nothing stored for past.
I will test with new settings and come back with feedback after few days, Again thank you for valuable support.
Re: Gigablue UE 4k crash. #18
Re: Gigablue UE 4k crash. #19
Posted 27 December 2018 - 15:27
I meant flash the box with the latest image, do you restore or autoinstall anything, configure the box by hand, and one at the time add the softcam and plugins, to see what is causing the problem.
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: Gigablue UE 4k crash. #20
Posted 28 December 2018 - 12:59
Three possibilities to get an OOM
- software with a memory leak, wasting memory
- a driver bug, leaking memory (but then everyone using that model should have the same phenomenon), these are really hard to spot, nothing seen in user space
- ramdisk getting full
The last one is quite easy to spot, using "df -h /tmp".
* Wavefrontier T90 with 28E/23E/19E/13E via SCR switches 2 x 2 x 6 user bands
I don't read PM -> if you have something to ask or to report, do it in the forum so others can benefit. I don't take freelance jobs.
Ik lees geen PM -> als je iets te vragen of te melden hebt, doe het op het forum, zodat anderen er ook wat aan hebben.
7 user(s) are reading this topic
0 members, 7 guests, 0 anonymous users