55 replies to this topic

[ims]

My point was the pyc in the updated plugin should always have a newer timestamp than any py from before the update, which would cause python to use the pyc and ignore the py.

I may be wrong, but with 'hash-based' (python >= 3.7), the hash is checked, and if it doesn't match, a .pyc is generated from the .py file.
I tried after modifying the .py file: touch -t 202401010101 <file.py>, and every time, the .pyc was again generated from .py, when was changed its content.

[WanWizard]

Ah, ok. In that case my knowledge of how it works is out of date. I stand corrected!

[bobbibob]

If it has started up ok, that means we can assume the current epg.dat cache file is correct.

 

My assumption is that somehow something is received (either via EPG refresh, EPG import, or OTA by zapping to a channel with EPG) which contains some corruption. This is stored in epg.dat when you restart Enigma (or the box), and when it starts again, and reads the epg.dat, it crashes.

 

We can test this hypothesis by waiting for the next crash, when that happens rename (not delete) epg.dat and restart. If the hypothesis is correct, it will start correctly, but without pre-loaded EPG. If this is so, please zip that renamed epg.dat file and post it here.

Ok, well before your post I deleted all EPG plugins... Then I noticed EPGImport and EPGRefresh where operational... maybe that is a problem? I reinstalled the EPG plugins but not EPGImport,,, So far it runs smoothly... I will keep you posted... 

 

Bob

[bobbibob]

If it has started up ok, that means we can assume the current epg.dat cache file is correct.

 

My assumption is that somehow something is received (either via EPG refresh, EPG import, or OTA by zapping to a channel with EPG) which contains some corruption. This is stored in epg.dat when you restart Enigma (or the box), and when it starts again, and reads the epg.dat, it crashes.

 

We can test this hypothesis by waiting for the next crash, when that happens rename (not delete) epg.dat and restart. If the hypothesis is correct, it will start correctly, but without pre-loaded EPG. If this is so, please zip that renamed epg.dat file and post it here.

Well there we go again... The renaming of epg.dat does not work, but I wanted send it anyway.... 

But I can not it will not upload.... is it to big? 17 k? 

 

Bob

Attached Files

•  enigma2_crash_1736148335.log   2.12KB   2 downloads
•  enigma2_crash_1736143180.log   80.4KB   2 downloads

Edited by bobbibob, Today, 08:34.

[littlesat]

ZN11eDVBService10isPlayableERK17eServiceReferenceS2

It crashes at an isPlayable check. Something (non utf-8) in your service settings?
What are you doing at the moment of the crash as I understood in the beginning it did work.

Edited by littlesat, Today, 08:52.

[bobbibob]

ZN11eDVBService10isPlayableERK17eServiceReferenceS2

It crashes at an isPlayable check. Something (non utf-8) in your service settings?
What are you doing at the moment of the crash as I understood in the beginning it did work.

I was not doing anything.. It was in stanby mode as i was sleeping...  

Attached Files

•  IMG_4160.jpg   134.98KB   0 downloads

[littlesat]

Then it looks like epg import or epg refresh likely triggered something…. Try disable it first… then still I’m afraid something invalid is included in most likely the service settings eg something non utf-8 in a userbouquet.

[bobbibob]

Then it looks like epg import or epg refresh likely triggered something…. Try disable it first… then still I’m afraid something invalid is included in most likely the service settings eg something non utf-8 in a userbouquet.

Ok, but this all worked fine under version 9.0 

[bobbibob]

The box just started correctly agian... Any suggestion as to what to do? Disable EPGRefresh?

[bobbibob]

Still running, here are the first and last crash logs.... do they suggest anything further? 

 

And the epg.dat file is 44,5 MB is that healthy 

 

Bob

Attached Files

•  enigma2_crash_1736143180.log   80.4KB   0 downloads
•  enigma2_crash_1736154290.log   2.12KB   0 downloads

Edited by bobbibob, Today, 12:17.

[bobbibob]

And what is interesting: the last adjustment in epg.dat sees to be at 01.23 and the problems seems to start at 06.59, just before a recording had to start... 

[WanWizard]

I've seen more reports of this crash in relation to a starting recording...

[bobbibob]

I've seen more reports of this crash in relation to a starting recording...

Can I switch on a reportingtools, or is that always gonna be to late? 

[WanWizard]

You can start Enigma in debug mode, by editing /usr/bin/enigma.sh.

 

On line 13, change

DEBUG_LVL=3

to

DEBUG_LVL=4

and restart Enigma.
 

This will create a detailed debuglog file in /home/root ( keep an eye on it's size, you don't want it to fill your root filesystem ! ).

 

Like with epg.dat, you need to zip this file before uploading it here, as the forum blocks files of those types.

[bobbibob]

You can start Enigma in debug mode, by editing /usr/bin/enigma.sh.

 

On line 13, change

DEBUG_LVL=3

to

DEBUG_LVL=4

and restart Enigma.
 

This will create a detailed debuglog file in /home/root ( keep an eye on it's size, you don't want it to fill your root filesystem ! ).

 

Like with epg.dat, you need to zip this file before uploading it here, as the forum blocks files of those types.

Hmmm, did this, but no debuglog in /home/root

[WanWizard]

Sorry, my mistake, you need to restart the box, restarting Enigma won't restart the startup script (duh, clue is in the name).