Kodi Community Forum

Full Version: XBMC's Log is far,far too big too quick.
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
Why is my nightly build of Eden debugging like a madman?

System > Settings > Enable debug logging. Is OFF.

All Add-ons debugging is OFF.

Yet, I have literally thousands of these in my Log.

Quote:00:38:52 T:3035614064 DEBUG: Previous line repeats 1 times.
00:38:52 T:3035614064 DEBUG: GetStackedTvShowList query: select idShow from tvshow where c00 like (select c00 from tvshow where idShow=92) order by idShow
00:38:52 T:3035614064 DEBUG: RunQuery took 3 ms for 0 items query: select * from episodeview where idShow = 92 and (c12=9 or (c12=0 and (c15=0 or c15=9)))

Just for kicks, this is a Pastebin of a single second (71 Lines!) that is being created by XBMC -
http://pastebin.com/s4W8j9nu

Can I manually make sure Debugging is forced OFF permanently somewhere by hacking the code? I'm having problems with my XBMC keep freezing - fun trying to find out why!!

My XBMC.log is up to 11Mb's within 15 minutes, it crashes then tranfers to XBMC.old.log, and starts the process all over again (once I reboot).

This has been driving be barmy the last week, been updating the nightly's constant in the hope it stops, on 20111116 and it's still doing it...
mysql related?
I'm not sure.

MySQL works great as XBMC has full control over it and can do exactly as it pleases - root access.

I seem to have managed to calm it down loads using this in the advancedsettings.xml
Code:
<loglevel hide="false">0</loglevel>
In my unprofessional opinion, I'm going to shout 'Bug' as it has had to be forced off.

So far, upto 3 minutes and it's staying at 654Kb.
I'll rescan my Library and see if it has another fit. The Log still has loads of DEBUG entries though.

EDIT-
Oh, and since off'ing it, by XBMC has not hung. Not sure if it's related yet.

EDIT2-
Because MySQL Databases are still 'Experimental', is everything they do Debugged by default? That seems to be the case. Can it be turned off to save Log from being spammed?
I guess the nightlies are debug builds, which have debug logging turned on even if the debug logging setting is off.
That's what I though would be the issue.

I seem to have made a small break through. The log was getting pretty huge, I guess it would seeing as my TV library is in excess of 4,000 episodes - I'm a Tele Whore.

Everytime it gets to a certain size, I've been deleting it. The Scan for the library has gone further than it did before and has almost finished. It seems as though it only gets large when it's Updating the Library, and not as big when Scanning for New Content.

Once it's built, perhaps the Debugging will calm down. Fingers crossed. In the meantime I'll just keep deleting the Log.

Would love a way to permanently turn off MySQL Debugging, but it's not in the Advancedsettings.xml settings (yet Wink).

EDIT-
Nope, still growing in size rapidly. Looks to be MySQL Debugging information too.
Code:
01:39:20 T:3045055344   DEBUG: Connecting to mysql:192.168.0.2:MyVideos57
01:39:20 T:3045055344   DEBUG: Connecting to mysql:192.168.0.2:MyVideos57
01:39:21 T:3045055344   DEBUG: GetStackedTvShowList query: select idShow from tvshow where c00 like (select c00 from tvshow where idShow=99) order by idShow
01:39:21 T:3045055344   DEBUG: RunQuery took 3 ms for 0 items query: select * from episodeview where idShow = 99 and c12=0
01:39:21 T:3045055344   DEBUG: Connecting to mysql:192.168.0.2:MyVideos57
01:39:21 T:3045055344   DEBUG: Previous line repeats 1 times.
01:39:21 T:3045055344   DEBUG: GetStackedTvShowList query: select idShow from tvshow where c00 like (select c00 from tvshow where idShow=99) order by idShow
01:39:21 T:3045055344   DEBUG: RunQuery took 9 ms for 24 items query: select * from episodeview where idShow = 99 and (c12=1 or (c12=0 and (c15=0 or c15=1)))
01:39:21 T:3045055344   DEBUG: Connecting to mysql:192.168.0.2:MyVideos57

This is while playing a TV Show. The thousands of connections to MySQL that XBMC needs are being used by the looks...!?
I've since changed the logging to by completely suppressed (-1), but it's still creating the log and still making it huge.

MySQL Databases are unusable at this time. Sad