Skip to content
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

[Bug] Removed Plex Library while rules were attached to that library #1302

Open
ydkmlt84 opened this issue Oct 5, 2024 · 1 comment
Open
Labels
bug Something isn't working enhancement New feature or request

Comments

@ydkmlt84
Copy link
Collaborator

ydkmlt84 commented Oct 5, 2024

I removed a library from inside of Plex that was attached to multiple rules. When I added the library back, with a new Library section ID (but the same media), Maintainerr was not working properly during Rule Execution. The only indication in the log was below:

[maintainerr] | 05/10/2024 11:14:20  [WARN] [PlexApiService] Plex api communication failure.. Is the application running?
[maintainerr] | 05/10/2024 11:14:20  [DEBUG] [PlexApiService] Cannot read properties of undefined (reading 'MediaContainer')

It was not immediately clear why my rules were giving me that error, until I looked in the Plex logs and found this:

Oct 05, 2024 15:09:57.668  DEBUG - Request: GET /library/sections/16/all?includeGuids=1&type=1 (12 live) #159a TLS Page 0-49 GZIP Signed-in Token (ydkmlt84) (129.0.0.0)
Oct 05, 2024 15:09:57.668 WARN - [Req#159a] Invalid library section ID 16 passed.

Which led me to think about my "new" library and then realize that I needed to update the rules' library. Then I went to my rules and found that each Rule that had that old library attached, was now showing "undefined".

A better log indication would be more helpful since there wasn't an actual communication issue with the Plex API, which is where I initially looked.

@ydkmlt84 ydkmlt84 added bug Something isn't working enhancement New feature or request labels Oct 5, 2024
@jorenn92
Copy link
Owner

jorenn92 commented Oct 7, 2024

Good point, Maintainerr won't notice the ID change. I agree a better log message would help a lot in this case.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants