Reply to thread

Message

<blockquote data-quote="RoChess" data-source="post: 1182665" data-attributes="member: 18896">When a scraper-debug log file is not 500kB+ for a single movie import you did something wrong (although I have made a suggestion to developers that got implemented to reduce that in the future) <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite1" alt=":)" title="Smile&nbsp; &nbsp; :)" loading="lazy" data-shortname=":)" />Activate MediaPortal debug mode for more data if you want more details.In short, those errors of &quot;27-Apr-2016 19:03:37&nbsp; Warn [&nbsp; WebGrabber]: Connection failed: Reached retry limit of 5. URL=<a href="http://ofdbgw.org/movie/284359" target="_blank">http://ofdbgw.org/movie/284359</a>&quot;&nbsp; do not have to mean that you have a bad internet connection, but the server at ofdbgw.org might be down, show a 404 error of page not found, or &quot;server is to busy right now, try again later&quot; type of error. Moving-Pictures does not exactly give full HTTP header diagnostics to verify that in the moment that it happens, and when you manually try later it might work just fine.The fact that directly following you see &quot;27-Apr-2016 19:03:37 Error [&nbsp; ScraperNode]: Scraper Script XPATH parsing failed: Das Stammelement ist nicht vorhanden.&quot; is a FilmInfo+ oversight in that it fetches the URL, stores it in a variable, and then plans to parse the result. With the fetching failing and not verifying that, then the parsing results in an error. I have the same in IMDb+ were I was forced to add dozens and dozens of extra lines to account for all the &quot;what if it goes wrong&quot; BS.So yeah, the whole ofdbgw.org mirror is highly unreliable, because the systems behind it are nowhere near the S3/Amazon capabilities that drive a site like IMDb.com, so especially when thousands of users hit it, you will have to deal with connection issues originating from their side. Wait a few hours and try again is the best course of action then, but that can not exactly be automated in MovPic.</blockquote>

[QUOTE="RoChess, post: 1182665, member: 18896"] When a scraper-debug log file is not 500kB+ for a single movie import you did something wrong (although I have made a suggestion to developers that got implemented to reduce that in the future) :) Activate MediaPortal debug mode for more data if you want more details. In short, those errors of "27-Apr-2016 19:03:37 Warn [ WebGrabber]: Connection failed: Reached retry limit of 5. URL=[URL]http://ofdbgw.org/movie/284359[/URL]" do not have to mean that you have a bad internet connection, but the server at ofdbgw.org might be down, show a 404 error of page not found, or "server is to busy right now, try again later" type of error. Moving-Pictures does not exactly give full HTTP header diagnostics to verify that in the moment that it happens, and when you manually try later it might work just fine. The fact that directly following you see "27-Apr-2016 19:03:37 Error [ ScraperNode]: Scraper Script XPATH parsing failed: Das Stammelement ist nicht vorhanden." is a FilmInfo+ oversight in that it fetches the URL, stores it in a variable, and then plans to parse the result. With the fetching failing and not verifying that, then the parsing results in an error. I have the same in IMDb+ were I was forced to add dozens and dozens of extra lines to account for all the "what if it goes wrong" BS. So yeah, the whole ofdbgw.org mirror is highly unreliable, because the systems behind it are nowhere near the S3/Amazon capabilities that drive a site like IMDb.com, so especially when thousands of users hit it, you will have to deal with connection issues originating from their side. Wait a few hours and try again is the best course of action then, but that can not exactly be automated in MovPic. [/QUOTE]

Verification