45 replies to this topic

[zajkas112]

Hello I am new on forum and also on openPLi please help me why my box crashed. Under is attached the log. Thank you and all the best

Attached Files

•  enigma2_crash.log   56.72KB   7 downloads

[WanWizard]

<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?

[zajkas112]

Hello and thank you for lightspeed reply.
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

[WanWizard]

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.

[zajkas112]

Hello, attached the output of requested command. Thank you

Attached Files

•  gigablueue4k.txt   18.09KB   17 downloads

[WanWizard]

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

[cobus]

Do you have recording on flash of the box?

[WanWizard]

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?

[zajkas112]

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

•  gigablue.PNG   273.1KB   3 downloads

Edited by zajkas112, 26 December 2018 - 21:39.

[WanWizard]

That screenshot shows plenty of free memory.

[zajkas112]

Hello, 

 

Last reply for this 24h   

So here other crash log this all time happen when oscam-emu crash  like previous reply.

Thank you for your free time spent with me.

Attached Files

•  enigma2_crash.log   108bytes   6 downloads

[WanWizard]

This is not a log file, that is a link to a logfile.

[zajkas112]

My bAd 

Attached Files

•  enigma2_crash.log   6.81KB   3 downloads

Edited by zajkas112, 26 December 2018 - 23:36.

[zajkas112]

And other one crash.log

Attached Files

•  crash03.log   12.65KB   4 downloads

[littlesat]

Last two crashdates and the first compile date 10-sep-2018... first update than try again... maybe in between the issue is fixed...

Edited by littlesat, 27 December 2018 - 07:44.

[WanWizard]

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.

[zajkas112]

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.

[zajkas112]

Fast feedback here and now other style of crash log  with enough memory.

About  update  you mean plugins and similar or flash ?

Attached Files

•  enigma2_crash27.log   27.2KB   6 downloads

[WanWizard]

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.

[Erik Slagter]

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".