Open rg9400 opened 2 years ago
There are actually two separate errors in your logs:
plexapi.exceptions.BadRequest
during connection attempts, thus stopping it from attempting again. This is not the desired behavior, it has been fixed in 198d1f2cc524ff31ead61d9209d53dcd32c34b4f.Try the latest version and let me know if you still encounter the issue !
Not sure how I can check what version I'm on with Docker, but I experienced this today when I updated my container and PAL never reconnected until I restarted the container. I have debug on, but I don't see much. Also, not sure why, but the container logs are really wonky for me, in terms of how they display, unless I use JQ.
I just had a similar problem when my plex server crashed for ~2 minutes. After restarting the plex docker (working fine), i noticed the PAL CPU usage was going a bit crazy, seemed to be having some recursive errors. Logs: https://gist.github.com/seanecoffey/b71e8e23e8f411cd3c69c69aa689ba5a
I know this feature was supposed to add resiliency if Plex is down - https://github.com/RemiRigal/Plex-Auto-Languages/pull/40
But it seems like either there is a code bug or it still dies after a certain number of attempts: