CoolDreamZ 1 Posted December 20, 2015 Posted December 20, 2015 This is causing: a) A lot of unneccesary traffic to themoviedb resulting in timeouts (and consequently delaying updates to Actors and Directors) My logs to fill up with themoviedb errors e.g. in some cases music artists are aggregated e.g. "John+Lennon+%26+Paul+McCartney" and themoviedb doesn't seem to like that!
Luke 42077 Posted December 20, 2015 Posted December 20, 2015 Hi there. In order to best help you, please see how to report a problem so that you can provide additional information. Thanks.
CoolDreamZ 1 Posted December 20, 2015 Author Posted December 20, 2015 2015-12-20 16:42:58.6363 Info App: HttpClientManager GET: http://api.themoviedb.org/3/search/person?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Neil+Sedaka+%26+Philip+Cody2015-12-20 16:42:58.7422 Info App: HttpClientManager GET: http://api.themoviedb.org/3/search/person?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=Burt+Bacharach+%26+Hal+David2015-12-20 16:42:58.8610 Info App: HttpClientManager GET: http://api.themoviedb.org/3/search/person?api_key=f6bd687ffa63cd282b6ff2c6877f2669&query=John+Lennon+%26+Paul+McCartney
Luke 42077 Posted December 20, 2015 Posted December 20, 2015 I don't think you read the above article.
CoolDreamZ 1 Posted December 20, 2015 Author Posted December 20, 2015 If you are implying that I should post the entire log file that is not possible (it is > 1Gb) this is partly due to being full of errors as a result of the problem reported here 1
CoolDreamZ 1 Posted December 23, 2015 Author Posted December 23, 2015 I have analysed my 3Gb collection of emby log files and observe the following behaviour with the people scanner: 1. It doesn't seem to ignore "misses" i.e if it fails to obtain data it simply trys the same 'person' again on the next iteration 2. It does not handle tmdb timeouts gracefully - this spams tmdb and fills the log with errors until the end of the iteration 3. It searches tmdb for Music Artists (this results in a lot of 'misses' e.g. those described in this post) 4. Increasing the frequency of People Scans does not result in more metadata - just more errors in the logs I think this has a serious consequence: Once the number of 'misses' exceeds the available tmdb query bandwidth then no new metadata will be retrieved - the only effect of the scanner being to fill the logs and spam tmdb at this point After a few days of running emby I think my setup has reached that point and I have now disabled the people scanner
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now