Spinner then log manager crash

[pembo]

Had a spinner earlier today and had to power off at the back to get it to respond.
On booting up I got a log manager error complaining about the log file for today not being present.

On looking in the logfile, there was nothing that gave anything away about the spinner, but I saw the following in relation to the logfile error.



[LogManager] Trim Poll Started
[LogManager] Trash Poll Started
[LogManager] probing folders
[LogManager] found following log's: ['/media/hdd/logs', '/home/root/logs']
[LogManager] looking in: /media/hdd/logs
[LogManager] /media/hdd/logs: bytesToRemove 830871095
< 63.004835> [setIoPrio] best-effort level 7 ok
[LogManager] /media/hdd/logs: bytesToRemove< 63.005070> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-17-05-2015_01-00-35.log.del'
828509334
[LogManager] /media/hdd/logs: bytesToRemove 826194978
[LogManager] /media/hdd/logs: bytesToRemove 825830157
[LogManager] /media/hdd/logs: bytesToRemove 825148379
[LogManager] /media/hdd/logs: bytesToRemove 825081446
[LogManager] /media/hdd/logs: bytesToRemove 825009147
[LogManager] /media/hdd/logs: bytesToRemove 824898379
[LogManager] /media/hdd/logs: bytesToRemove 824806543
[LogManager] /media/hdd/logs: bytesToRemove 824644178
[LogManager] /media/hdd/logs: bytesToRemove 824466106
[LogManager] /media/hdd/logs: bytesToRemove 823794568
[LogManager] /media/hdd/logs: bytesToRemove 823745237
[LogManager] /media/hdd/logs: bytesToRemove 823676046
[LogManager] /media/hdd/logs: bytesToRemove 823466463
[LogManager] /media/hdd/logs: bytesToRemove 823405997
[LogManager] /media/hdd/logs: bytesToRemove 822974721
[LogManager] /media/hdd/logs: bytesToRemove 822750367
[LogManager] /media/hdd/logs: bytesToRemove 822697842
[LogManager] /media/hdd/logs: bytesToRemove 822468080
[LogManager] /media/hdd/logs: bytesToRemove 822422033
[LogManager] /media/hdd/logs: bytesToRemove 822378203
[LogManager] /media/hdd/logs: bytesToRemove 822288911
[LogManager] /media/hdd/logs: bytesToRemove -20946741
[LogManager] looking in: /home/root/logs
[NTP]: setting E2 time: 1432663879.92
< 63.046497> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-22-05-2015_06-01-21.log.del'
< 63.057356> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_06-29-36.log.del'
< 63.057745> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_08-24-37.log.del'
< 63.058105> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_11-00-48.log.del'
< 63.058402> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_11-06-29.log.del'
< 63.058658> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_11-16-39.log.del'
< 63.058971> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_11-51-27.log.del'
< 63.059316> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_12-01-21.log.del'
< 63.059558> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_12-32-26.log.del'
< 63.059816> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-24-05-2015_12-50-22.log.del'
< 63.060222> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-01-01-1970_01-00-27.log.del'
< 63.060507> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-01-01-1970_01-00-24.log.del'
< 63.060714> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-25-05-2015_06-40-40.log.del'
< 63.060964> [eBackgroundFileEraser] deleting '/media/hdd/logs/backup.log.del'
< 63.061260> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-25-05-2015_10-44-50.log.del'
< 63.061935> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-25-05-2015_23-01-51.log.del'
< 63.062378> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-25-05-2015_23-08-16.log.del'
< 63.062651> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-25-05-2015_23-09-35.log.del'
< 63.062882> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-26-05-2015_06-21-17.log.del'
< 63.063148> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-26-05-2015_06-22-19.log.del'
< 63.063405> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-26-05-2015_06-23-01.log.del'
< 63.063657> [eBackgroundFileEraser] deleting '/media/hdd/logs/Enigma2-26-05-2015_06-45-13.log.del'



And all logfiles are gone but one from today at the time of the reboot.... :confused:

[rossi2000]

log files are cleaned up after a certain amount of days
configurable by the user

[pembo]

all log files though? this deleted all including the one from today.

[rossi2000]

hmm ye thats not right,
after a quick look in log manager i got the option wrong, its actually delete log files that are older than a certain age.

any chance of the full debug log please?

[pembo]

sure, i'll dig it out and send it over... wasn't anything else of much use in there though, and the spinner cause has gone as the log was deleted :S

[nsw9154]

I always save my log files to the Hard Drive now because i sometimes lost them during a crash :)

[pembo]

I always save my log files to the Hard Drive now because i sometimes lost them during a crash :)

Mine were on the hard drive!

[pembo]

Had another spinner and crash this morning... only log file again was from after the restart of enigma2 (which I killed before checking the logs).
I noticed the enigma2 process was running at 100% cpu in top.

Next time it happens I'll do a bit more investigation, and check the logs before I kill it, as I think the restart might be causing the wipe, and the issue is probably related to whatever is causing the cpu loop...

[pembo]

Ok.. so, error has just occurred again and I caught it this time:

This happens,

<102406.349335> Backtrace:
<102406.349697> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x45D830]
<102406.349996> /usr/bin/enigma2(_ZN9eventDataD1Ev) [0x4A304E]
<102406.350335> /usr/bin/enigma2(_ZN9eEPGCache11sectionReadEPKhiPNS_12chann el_dataE) [0x4A8618]
<102406.350549> /usr/bin/enigma2(_ZN9eEPGCache12channel_data28readFreeSatSc heduleOtherDataEPKh) [0x4A9EA4]
<102406.350754> /usr/bin/enigma2(_ZN17eDVBSectionReader4dataEi) [0x48F638]
<102406.350941> /usr/bin/enigma2(n/a) [0x4636D4]
<102406.351178> /usr/bin/enigma2(_ZN9eMainloop15processOneEventEjPP7_object 9ePyObject) [0x464AC0]
<102406.351386> /usr/bin/enigma2(_ZN9eMainloop7iterateEjPP7_object9ePyObjec t) [0x464DD8]
<102406.351575> /usr/bin/enigma2(_ZN9eMainloop7runLoopEv) [0x464E90]
<102406.351784> /usr/bin/enigma2(_ZN9eEPGCache6threadEv) [0x4A8074]
<102406.351974> /usr/bin/enigma2(_ZN7eThread7wrapperEPv) [0x46D9E0]
<102406.352131> /lib/libpthread.so.0(n/a) [0x76FBF8AC]

Then a constant loop of

<102406.352183> -------FATAL SIGNAL
<102406.352451> PC: 773f7e98
<102406.352541> 00000000 00000001 77539080 775664b4
<102406.352578> 00000000 580af950 00000000 580403dc
<102406.352610> 80808080 0000004e 00000000 00687461
<102406.352641> 2e363034 31323533 203e3338 0045c710
<102406.352671> 580af950 7740b5e8 5e4ecad0 580af950
<102406.352700> 604de67c 604de530 5fc9c530 005c0000
<102406.352730> 00000018 773f7e5c 604e04d4 00000000
<102406.352760> 77567fc0 604de2c8 00000001 774a2888
<102406.353078> Backtrace:
<102406.353293> /usr/bin/enigma2(_Z17handleFatalSignaliP9siginfo_tPv) [0x45D830]
<102406.353435> /usr/lib/libpython2.7.so.1.0(PyObject_Call) [0x773F7E9A]

which causes 100%cpu and the spinner.

I think if I don't catch it quick enough, then it fills the log files quickly, which causes the cleanup job...

[pembo]

EPG appears to have been corrupted also/

I've been having random EPG issues so this is definitely related and you can see the EPG reference.
I've deleted the EPG files a few times to resolve this, and resetup but nothing has an effect.

I've just deleted again, resetup and will wait to see what happens.

[pembo]

and after running cross epg...
[CrossEPG_Loader] loading data with crossepg patch v2
<103501.692906> [EPGC] start crossepg import
<103501.693262> [EPGC] 0 aliases groups in crossepg db
<103502.360311> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
<103502.360999> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
<103502.373819> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
..
repeat
..
<103505.589530> [gRC] main thread is non-idle! display spinner!
<103505.859697> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
<103505.859819> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
..
repeat
..
<103508.331163> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
<103508.331254> [eventData] EPG Cache is corrupt (eventData::~eventData), you should restart Enigma!
<103508.344193> [EPGC] imported 137128 events from crossepg db
<103508.344310> [EPGC] 8819575 bytes for cache used

[pembo]

Just created a new epg file (different name)

[CrossEPG] TUNING
KEY: 352 OK
[CrossEPG_Wrapper] <- OK
[CrossEPG_Wrapper] <- OK
[CrossEPG_Wrapper] <- OK
<104488.791857> [eDVBFrontend] (1)fe event: status 1f, inversion off, m_tuning 2
<104488.791985> [eDVBChannel] OURSTATE: ok
[CrossEPG] ACQUIRING TSID/ONID
<104489.127951> [eDVBFrontend] set dynamic current limiting
[CrossEPG_Wrapper] -> DOWNLOAD skyuk_astra2_28.2
[CrossEPG_Wrapper] <- START
[CrossEPG_Wrapper] <- TYPE READ CHANNELS
[CrossEPG_Wrapper] <- TYPE READ TITLES
[CrossEPG_Wrapper] <- TYPE PARSE TITLES
[CrossEPG_Wrapper] <- TYPE READ SUMMARIES
[CrossEPG_Wrapper] <- TYPE PARSE SUMMARIES
[CrossEPG_Wrapper] <- END
[CrossEPG_Wrapper] -> SAVE
[CrossEPG_Wrapper] <- START
[CrossEPG_Wrapper] <- END
[CrossEPG_Wrapper] -> CLOSE
[CrossEPG_Wrapper] -> QUIT
[CrossEPG_Wrapper] <- OK

Seems to be behaving right now - I'll monitor it!

[pembo]

So taking a look again this morning, I can't see my EPG file on the hard disk.

Is this becase I'm using cross epg and therefore the database is within /media/hdd/crossepg?
Therefore if the database becomes corrupt Ii need to empty out the crossepg directoy and restart?

[Piranha]

EPG.dat is written to your chosen storage location on shutdown. Just check that in EPG configuration it hasn't defaulted to internal flash. If it has, check your HDD mount in ViX Mount Manager. In EPG menu you have the Load/Save/Delete option, so you can Save the cache and then it will appear in media/HDD root as EPG.dat. Hope this helps.

[pembo]

EPG.dat is written to your chosen storage location on shutdown. Just check that in EPG configuration it hasn't defaulted to internal flash. If it has, check your HDD mount in ViX Mount Manager. In EPG menu you have the Load/Save/Delete option, so you can Save the cache and then it will appear in media/HDD root as EPG.dat. Hope this helps.

conf and hd mount are all fine
42841

I guess I don't need to set the save/refesh options as the data comes from crossepg?
I assume the epg data comes from the crossepg directory when using cross epg, as it's all working without the epg file (which I changed to epg1 to try and resolve the issue!)

[bbbuk]

I also ensure auto refresh and save are ticked.

I would tick these two then do another download of EPG data via menu.

I've noticed, for whatever reason, having set my EPG up for 28.2 via CrossEPG that sometimes if box is restarted, it doesn't automatically load the EPG data again from file. To get around this, I just download EPG data again and that's it then it automatically reloads EPG data even on a full restart.

[Piranha]

conf and hd mount are all fine
42841

I guess I don't need to set the save/refesh options as the data comes from crossepg?
I assume the epg data comes from the crossepg directory when using cross epg, as it's all working without the epg file (which I changed to epg1 to try and resolve the issue!)

In EPG Configuration, you can call the file anything you want - try 'Mother-in-law' if you wish - something fairly small but a right pain in the backside an occasion! Whatever you call it, that is what you will find on your designated storage device (e.g. media/hdd/Mother-in-law.dat) whenever the epg cache is saved.

Your system is not working 'without the epg file', it's working with 'live' epg data it has in volatile memory until you reboot. The epg1 file as you have named it will only come into being if you choose to save the epg cache or reboot your box. The epg.dat will still exist, unless you have deleted it via FTP.

The Save/Refresh options have 'repeat every' options to them, with the default being every 24 Hours. I have CrossEPG setup to download every 24hrs and always set the EPG Save/Refresh options to every 24hrs too - therefore the new data will overwrite the old, but the data in EPG.dat on the HDD will be less than 24hrs old at worst.

I guess it depends on where your EPG data is coming from - epg.dat can be on any drive media (box or network) that is available at boot-up, which is when EPG data is written back into volatile memory, therefore the data could come from a source external to the box, if you wanted to do that.

CrossEPG parses the EPG data - Channels/Events/Titles/Summaries (Descriptors) separately and then loads this data into volatile memory. When the system is shut down (or crashes!) this data is written as a single .dat file called 'Mother-in-law' (or whatever) to wherever you have designated.

Hope that this has clarified rather than confused matters even further!