-
-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Movies passing the rules not being added to the Collection #1068
Comments
Hey! It seems that the rule encountered an undefined statistics object, which is unexpected considering the object is initialized at the start. While it's possible that this issue could stem from a sluggish Plex server response, the error isn't what i'd expect in such scenarios. API calls to Plex are configured with a timeout value of 5 seconds. If this limit is exceeded, the returned item is likely to be null. Although some calls are retried, not all Plex calls benefit from this mechanism. Maintainerr relies on an external library for Plex API communication, which currently lacks a built-in retry feature. Is this the first time you encountered this issue? Does the problem resolve itself upon next rule executions? |
Hi-- I've had the issue since 5/1/24 when you see from the screenshot that items were mysteriously removed but are still resolving as true when evaluated individually. The error I posted only occurs once. I have not been able to reproduce that error since the one occurrence. To test, I restarted the Maintainerr container and manually ran the Movies Rules. I only see this in my logs, it's been 5 hours since I ran the rules manually:
Is there any way I can increase the logging to see what's happening? |
After another day, the movies returned to the Collection. The countdown dates are reset, but they are back. I'm fine with closing this, or I can provide some logs to help track down if there is a bug. Thanks again. |
The only method to enhance logging is by enabling the 'DEBUG' flag in your Docker Compose/run command. However, I'm uncertain if this will provide additional information in this scenario. If you encounter this issue again, it would be great if you were able to obtain some debug logs from Maintainerr and Plex's side. But it may not be straightforward to gather them when the problem doesn't happen consistently. I'll leave this issue open for a few weeks. Please keep me informed if it reoccurs. Otherwise, I'll close it later. Thank you for reporting this! |
Hey
Did you manage to catch Plex logs when this failed? I'm still leaning towards network issues. As for the timestamp, what time does it log the executions in the container log? Perhaps the UI is misinterpreting the timestamp fetched from the database. |
Hi there- I witnessed live when the error occurred, but I'm not having much luck diagnosing it.
[maintainerr] | 27/05/2024 14:46:19 [INFO] [CollectionsService] Removing media with id 4027 from collection..
|
If Plex crashes, some API calls may return empty responses. This could explain why Maintainerr detects discrepancies in some rule data. Do you think Maintainerr is overwhelming Plex? Maintainerr has built-in rate limiting & caching, so it shouldn't overload Plex. However, it might still be too aggressive. Are you running Maintainerr against a large library? If your library is substantial, rule handling could take several hours due to the rate limiting. |
Describe the bug
Been using Maintainerr for some time, with no changes to my rules. Recently a number of movies have been removed from my Collection, but are still passing the rule when evaluated.
Other than TMDB items not being found, I only see this error in my logs:
[maintainerr] | 02/05/2024 14:07:03 [INFO] [RuleComparatorService] Something went wrong while running rule Movies Leaving Plex Soon
[maintainerr] | 02/05/2024 14:07:03 [ERROR] [ExceptionsHandler] Cannot read properties of undefined (reading 'stats')
I do not use the exclusions feature, so it's not that.
One potential culprit is that my Plex has been slow to respond to metadata queries at times. I'm not sure how resilient maintainerr is to retry if a query fails? I have a heafty Plex server but it has a large library. I've been running some cleaning scripts to clean up the bundles, etc.
Screenshots
Device (please complete the following information):
The text was updated successfully, but these errors were encountered: