Every day the box locks up...

[LanceH]

Every day the box becomes wholly unresponsive to the Remote and the VIX "spinner" appears in the top left corner of the screen. This just happens without any human interference...

Am I supposed to power the box on and off using the power button? That's what I did yesterday but it seems a very inelegant way to reboot.

I suppose the obvious question is why could this be happening?

New box, clean install, no added extensions, default skin, most settings at default.

TIA

[abu baniaz]

Enable debug logs. Restart the receiver. When it happens again, upload the debug log to to your thread.

What plugins/scripts have you installed?
Where are you saving your EPG?

Yo are not filling in the image details properly. Which image are you using? I am on 4.2 026

[LanceH]

Will do... 4.2.026 (I've corrected my gaff in the header)

EPG on internal HDD

No plugins or anything else

[danlou]

You don't seem to have mention which box you're using.
If it's an 'old' one you may have to set up a swap file ....

Sent from my Vodafone Smart ultra 6 using Tapatalk

[LanceH]

Errr ... It's in the header??? VU+ Solo2 Brand new from WoS

[danlou]

Ah OK, I'm on Tapatalk hence didn't see and still can't.
Oh well.
Strange one... Presumably you have done a second clean install?


Sent from my Vodafone Smart ultra 6 using Tapatalk

[birdman]

Every day the box becomes wholly unresponsive to the Remote and the VIX "spinner" appears in the top left corner of the screen.

These are related. When the sipnner is spinning the software isn't going to respond to anything.

Am I supposed to power the box on and off using the power button?

You can use telnet (in PuTTy) to connect to the box and type "reboot", which is better.

[LanceH]

OK - I've "hard" rebooted and enabled logs. I will post anything eventful if/when it recurs.

[LanceH]

OK - I've "hard" rebooted and enabled logs. I will post anything eventful if/when it recurs.

Here's the crash log - it happened while I was away. This is the first one since enabling logging and was 2 days after the previous (unlogged) daily crash.

My daughters may have been complicit, who knows...Enigma2_debug_2017-01-15_13-33-40.log

I've not looked at it at all, just come home after a jaunt to loads of moaning...

[ccs]

I can't see a crash at the end of the log, could the box have been powered off at the mains switch?

[LanceH]

Yes - they had to do that to get the box working again. I assume from your question that a crash log will only contain useful info if the box is rebooted via Telnet??? So it isn't a crash log as such then... despite its name?

[ccs]

It's a debug log, and it's got debug in its name. I can't see anything obvious like the spinner being activated.

There are some remote keys pressed just before it's switched off, and there seems to be opkg activity which might be significant.

<103457.116> [InfoBarGenerics] KEY: 114
<103457.733> [IPKG] executing opkg  --add-dest /:/ list-upgradable
<103457.734> [eConsoleAppContainer] Starting /bin/sh
<103457.737> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 95(16)
<103459.716> [Skin] processing screen MessageBox:
<103459.735> [Skin] processing screen MessageBox_summary:
<103459.743> [eMainloop::processOneEvent] unhandled POLLERR/HUP/NVAL for fd 95(16)
<103461.539> [eInputDeviceInit] 1 ae 1
<103461.541> [InfoBarGenerics] KEY: 174 EXIT
<103461.543> [ActionMap] MsgBoxActions cancel
<103461.770> [eInputDeviceInit] 0 ae 1
<103461.772> [InfoBarGenerics] KEY: 174 EXIT
<103462.183> [eInputDeviceInit] 1 ae 1
<103462.186> [InfoBarGenerics] KEY: 174 EXIT
<103462.187> [ActionMap] OkCancelActions cancel
<103462.414> [eInputDeviceInit] 0 ae 1
<103462.415> [InfoBarGenerics] KEY: 174 EXIT
<103462.755> [eInputDeviceInit] 1 ae 1
<103462.757> [InfoBarGenerics] KEY: 174 EXIT
<103462.781> [ActionMap] OkCancelActions cancel
<103462.986> [eInputDeviceInit] 0 ae 1
<103462.988> [InfoBarGenerics] KEY: 174 EXIT
<103562.210> [eDVBDemux] open demux /dev/dvb/adapter0/demux0
<103562.212> [eDVBSectionReader] DMX_SET_FILTER pid=20
<103563.828> [eDVBLocalTimerHandler] diff is -1
<103563.830> [eDVBLocalTimerHandler] diff < 120 .. use Transponder Time
<103563.951> [eDVBLocalTimerHandler] difference between linux time and RTC time is < 60 sec... so the transponder time looks ok
<103563.952> [eDVBLocalTimerHandler] time update to 18:19:16
<103563.953> [eDVBLocalTimerHandler] m_time_difference is -1
<103563.954> [eDVBLocalTimerHandler] set Linux Time
<103563.956> [eDVBChannel] getDemux cap=00

[bbbuk]

Crash log will display what caused the crash (ie the error on screen and it subsequent reboot). Are there no crash logs? I believe they're in round about the same area debug logs (/home/logs) I believe.

[LanceH]

No - in home/root/logs there's just that one which was when the box locked up, apparently.

How do I ensure that a "crash" log is generated when the box locks up?

[Andy_Hazza]

What is your setup? I have a Vu+ Solo2 running the latest ViX image and no such issues. What are your tuner configs, softcam etc. Do you have port forwarding enabled on your router also? Does the freeze/lockup happen without the ethernet cable wired to the skybox?


Sent from my iPhone using Tapatalk