home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Queueing files
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="RoChess" data-source="post: 950342" data-attributes="member: 18896"><p>Well we are getting closer.</p><p> </p><p>Log file seems indeed to indicate everything went perfect (would need to see movpic scraper-debug enabled log file to make sure the filmtipset.se scraper-script you are using is not causing any issues though).</p><p> </p><p>But as you stated, the issue is more when you re-open MovPic config again after closing it first.</p><p> </p><p>Are you able to provide the movingpictures.log file on that?</p><p> </p><p>See one problem for example could be that filmtipset.se changed their website result, and the scraper-script uses "some bad string" as the year for example. Moving-Pictures expects a 4-digit number and freaks out and corrupts the database. This then causes the queue issue when MovPic config is restarted as MovPic normally rescans the database for integrity. Now I'm pretty sure that MovPic has a lot of safety guards in place to prevent that scenario, but it is one of those plausable scenarios to think off, as it can then help figuring out next debug step.</p><p> </p><p>Which in that case would require you to recreate the exact same movingpictures.log file you just posted, except then with MovPic scraper-debug log mode enabled.</p><p> </p><p>Instructions on enabling that mode @ <a href="http://code.google.com/p/imdbplus/wiki/WikiInstallScraper" target="_blank">http://code.google.com/p/imdbplus/wiki/WikiInstallScraper</a></p><p> </p><p>And try to get both log files, as in the one were everything imports perfect and the one directly following where you re-open MovPic config afterwards and it 'stalls'.</p><p> </p><p>That actually reminds me of another possible cause. I use a batch script myself to ensure that I do not launch MovPic config when any MediaPortal related item is still running. Sometimes it takes a few seconds for MediaPortal to properly 'close' itself, so I get a nice warning to not launch MovPic just yet. Database corruption and other weird behaviour can happen quickly if that is the case, so are you sure when you re-launch MovPic config that you did not do it 'too quick'? The batch scripts I use are available on forum here, search for "PluginConfigLoader", and they are inside zipped attachment to solve old 64-bit OS issue.</p></blockquote><p></p>
[QUOTE="RoChess, post: 950342, member: 18896"] Well we are getting closer. Log file seems indeed to indicate everything went perfect (would need to see movpic scraper-debug enabled log file to make sure the filmtipset.se scraper-script you are using is not causing any issues though). But as you stated, the issue is more when you re-open MovPic config again after closing it first. Are you able to provide the movingpictures.log file on that? See one problem for example could be that filmtipset.se changed their website result, and the scraper-script uses "some bad string" as the year for example. Moving-Pictures expects a 4-digit number and freaks out and corrupts the database. This then causes the queue issue when MovPic config is restarted as MovPic normally rescans the database for integrity. Now I'm pretty sure that MovPic has a lot of safety guards in place to prevent that scenario, but it is one of those plausable scenarios to think off, as it can then help figuring out next debug step. Which in that case would require you to recreate the exact same movingpictures.log file you just posted, except then with MovPic scraper-debug log mode enabled. Instructions on enabling that mode @ [url]http://code.google.com/p/imdbplus/wiki/WikiInstallScraper[/url] And try to get both log files, as in the one were everything imports perfect and the one directly following where you re-open MovPic config afterwards and it 'stalls'. That actually reminds me of another possible cause. I use a batch script myself to ensure that I do not launch MovPic config when any MediaPortal related item is still running. Sometimes it takes a few seconds for MediaPortal to properly 'close' itself, so I get a nice warning to not launch MovPic just yet. Database corruption and other weird behaviour can happen quickly if that is the case, so are you sure when you re-launch MovPic config that you did not do it 'too quick'? The batch scripts I use are available on forum here, search for "PluginConfigLoader", and they are inside zipped attachment to solve old 64-bit OS issue. [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 1
MediaPortal 1 Plugins
Popular Plugins
Moving Pictures
Queueing files
Contact us
RSS
Top
Bottom