Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
I can see that the video scans are most likely due to qax, but I've no idea why the YouTube add-on is running after each video scan - do you have some Kodi configuration or add-on that causes this?
My guess is that the YouTube add-on should be more tolerant of a locked database as it's not the only "user" of the SQLite3 database and should therefore expect to encounter locking from time to time. qax will be deleting movies from the MyVideos* database before kicking off the next video scan, and clearly the YouTube add-on doesn't like that.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 328
Joined: Jul 2011
Reputation:
7
Hmmm.... No addons really other than Youtube...
One thing of note is that I'm running a MySQL backend...
Given that it's reproducable, but not every night, I wonder if the triggering of Youtube is due to "sometimes" my family leaving the Kodi screen on the Youtube Addon vs other nights where it's in the core TV Shows or Movies screen...
Will try to test that out...
Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
If you can find a way to reproduce I'll be able to investigate a bit further. Enabling the texturecache.py logfile (@logfile=tc.log) would allow comparison of the kodi.log timestamp with whatever texturecache.py is doing.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 328
Joined: Jul 2011
Reputation:
7
I've had a couple of more crashes, although again, neither with Kodi debug log turned in...
I do have a "normal Kodi log" and Texture Cache log which I'll upload later tonight.
The consistent thing in each hard crash is that the screen was left on YouTube Addon's search/trending page when the Texture Cache Activities were triggered. Can't say it crashes 100% of the time, but seems 100% of crashes share this in common.
I know it's a workaround for more than likely a Kodi issue, but maybe an option to put Kodi on the Home Screen before triggering the activities would help?
Anyways, will post logs later tonight...
Posts: 328
Joined: Jul 2011
Reputation:
7
Ah, perfect, I didn't know that option existed... It's absolutely good enough
Posts: 328
Joined: Jul 2011
Reputation:
7
Updating that ever since adding the command to take Kodi back to home screen before running the other commands, I have not had a single crash of the application.
Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
2016-10-08, 23:10
(This post was last modified: 2016-10-08, 23:13 by Milhouse.)
As the message says, the "Xd" command requires read/write access to the Thumbnails folder (which is on your RPi). It's one of the few commands that requires direct folder access (the others are "f", "F", "r", "R", "S" and "X"). All other commands can be run remotely.
You need to run the "Xd" command on the RPi itself, rather than remotely, or somehow map the Thumbnails folder on the machine that is running texturecache.py (tricky when it's Windows) and configure the mapped Thumbnails location in your config file.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
As it says in the first post, it's an example properties file. You don't have to use it. You should only use (ie. configure) the properties you need.
To answer your question, the command line properties trump the cfg file properties.
My advice would be to include in your cfg file only those properties that are different from the default. Most people don't need a cfg file at all.
Properties that might change from one invocation to another (eg. qa.nfo.refresh) are better left on the command line IMHO. A property such as qaperiod, which defaults to 30, should be added to your cfg as "qaperiod=-1" if you always want to use an infinite period.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.
Posts: 17,855
Joined: Jan 2011
Reputation:
1,055
Milhouse
Retired Team-Kodi Member
Posts: 17,855
Yes, to rescrape the whole database you might as well just delete it and start again!
You can use the texturecache.py imdb option (for movies and tvshows), or the add-on. The obvious advantage of the former is that it's easier to script, but both should be doing similar things (I guess - I've never looked at or used the add-on so don't really know where it get it's data from, or how accurate it is). I know for sure that the texturecache.py version will only update the imdb values in the database and won't touch any local NFO files.
Texture Cache Maintenance Utility: Preload your texture cache for optimal UI performance. Remotely manage media libraries. Purge unused artwork to free up space. Find missing media. Configurable QA check to highlight metadata issues. Aid in diagnosis of library and cache related problems.