+- Kodi Community Forum (https://forum.kodi.tv)
+-- Forum: Support (https://forum.kodi.tv/forumdisplay.php?fid=33)
+--- Forum: General Support (https://forum.kodi.tv/forumdisplay.php?fid=111)
+---- Forum: OS independent / Other (https://forum.kodi.tv/forumdisplay.php?fid=228)
+---- Thread: Constantly RE-Setting content (/showthread.php?tid=191618)
Constantly RE-Setting content - jacintech.fire - 2014-04-07
I have quick question: the lady of the house sent me an email the other day, explaining a problem she has encountered, whereby a previously configured video source (configured as either Movie, Tv Show or Music Video) would all of the sudden dispappear from the library.
And once you browse that location from the VIDEO ==> FILE [LOCATION] and launch the context menu, instead of seeing the [SCAN FOR NEW CONTENT] option, you see [SET CONTENT]
apparently this has happened several times.
By the way, we are using a beta version of XBMC 13.0...
RE: Constantly RE-Setting content - jacintech.fire - 2014-04-20
Wow. Nobody?
RE: Constantly RE-Setting content - jmarshall - 2014-04-20
Unfortunately, nobody in the know can reproduce this fault.
What you'll want to do to troubleshoot is, when everything is working (i.e. you know you have content set on a path) take a copy of your database.
Then, when it breaks, grab another copy.
Take a look in each and see what content is set on the path table.
RE: Constantly RE-Setting content - Kib - 2014-04-20
You also share your sqlite databases over the network and use them with multiple clients, right?
I told you previously this will cause database corruption.
Re: Constantly RE-Setting content - nickr - 2014-04-20
@Kib So you did, and he scoffed.
RE: Constantly RE-Setting content - Kib - 2014-04-20
I have been waiting for this thread ever since. :-)
RE: Constantly RE-Setting content - nooryani84 - 2014-04-20
Don't forget 512TB NoRaid.. 1 TB partitions..
RE: Constantly RE-Setting content - jacintech.fire - 2014-06-09
Ha!
found the source: IN ALL CASES, this was a virtual-drive specific issue that HAD NOTHING TO DO with the database itself. It was rooted on one of my automation scripts* un-mounting a virtual drive and not re-mounting correctly. So there :-)
*=I have a whole suite of scripts that perform several server maintenance/fine-tuning functions