enigma2 crash log location

[paulus]

Where will I find the enigma 2 crash log (BH 217)?

[Mickha]

Doyou have an internal Hard Drive?
Check Media, HDD, and look for any crash log listings, preferably the most recent.
You could aslo post the problems, you're experiencing, to see if it's a common problem.

[paulus]

Yes, I have an internal HDD - but that only seems to contain XBMC log files, I believe the system log file is something like enigma2_crashlog_******** which I cannot find. Regarding the problem, after two years of rock solid performance my Solo2 is misbehaving. XBMC freezes and judders, most TSmedia doesn't work - so my box is reduced to a sat channel only box. Morfe lately I arrive down in the morning and the box is stuck in some power-up loop and requires a rear switch power-cycle, but the box had been left in standby with only an overnight crossepg update session to perform.

Whilst hunting the XBMC problem I found that a module was missing (python-pkgutil) but more puzzlingly that this module was not loaded by the image. On manually loading it some of my problems improved, but not all. So I have concluded that some damage has been done to the base OS which sits below the image?!? My guess is that analysis og the enigma2 crash log might indicate other module(s) that are missing and need to be manually installed. I deally I would like to reinstall the underying OS - but I don't believe that to be possible?

Thanks for interest, and any help you can give.

[Nikkas]

On most recent images that are configured to run XBMC the crash logs are called xbmc_crashlog for some inexplicable reason and should be stored on the root of the HDD.h.

[echelon]

crashlogs are on the root of the hdd itself , under media/hdd

such as enigma2_crash_1440392397.log

personally, I dont like BH217 at all and prefer either BH216 , or BH215 , or use openBH in the flash and multiboot to load BH215 or BH216 , or openvix , openpli or openatv etc

plugins like xbmc can take up a lot of flashmem so ensure its not overloaded, keeping it below 90%

you have not been using BH217 for 2 years, as its only a 2015 image

[paulus]

you have not been using BH217 for 2 years, as its only a 2015 image

My only mention of two years was "after two years of rock solid performance my Solo2 is misbehaving." so I thought it obvious that it was my Solo2 that is two years old - and (later for additional info) my current image is BH 2.1.7. I never thought I'd need to spell that out.

My HDD only contains XMBC logs so whatever is causing my other problems is not generating a log, however my question is answered by Nikkas, so please close this thread.

[echelon]

my point was that for that 2 years that it wasnt misbehaving it was not using BH217 , SO BY DEFINITION MUST HAVE USED A DIFFERENT IMAGE OR IMAGES, i SUGGEST YOU GO BACK TO THE IMAGES THAT GAVE ROCK SOLID PERFORMANCE !!

ie:- wipe it and reflash with a different image

its unlikely to be a hardware fault, more likely to be a software fault, you chose the BH217 OS , you chose to add XBMC plugins etc, so assume you have corrupted it or that the image has flaws in it

run a rolls royce for 2 years on good petrol or diesel , then put some dodgy stuff in it from the local scally, you cannot expect it to run to the exacting standards demanded by rolls royce

there, I have spelled it out too

thread closed as requested