-
-
Notifications
You must be signed in to change notification settings - Fork 19
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
Read timeout error #74
Comments
Yes, that's exactly what I'm seeing as well. It would be nice to be able to either (1) increase the read timeout from 30s to something higher (since my Plex does always come back, I guess sometimes it takes longer than 30 seconds) or, (2) be able to survive that timeout, and right itself once it regains connection. |
I just issued a pull request, I've actually never done it before so I don't know if I did it right. My recommended change would adjust the default 30 second timeout and make it 60 seconds instead. |
Yes it is, I've just been struggling to get some time to work on this project lately.
I would prefer making PAL more resilient to those timeouts, increasing the tolerance will only reduce the number of occurrences. |
I agree 100%, that is definitely the better option. Hopefully you'll have a way to make it more resilient! |
I have the same issue, and somewhat constantly: My NAS seems to go into overload whenever I start or restart a container, which I assume leads to Plex never responding in time on startup. Plex itself runs fine and things smoothen shortly after the Docker service did its thing, but as PAL seems to never recover from the error caused by the slowdown, I basically cannot use it. Is there any workaround yet? |
plex-auto-languages | Traceback (most recent call last): Same here. Restarting the container fixes the issue temporarily, but after a while, it times out again. |
Redeploy PAL with label "autoheal=true" then add autoheal container
|
Thank-you, I am trying that now.
…On Mon, 19 Feb 2024 at 20:15, edrock200 ***@***.***> wrote:
Redeploy PAL with label "autoheal=true" then add autoheal container
https://github.com/willfarrell/docker-autoheal
—
Reply to this email directly, view it on GitHub
<#74 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADXRBWTFC4CC2KQR6LSDUYLYUOXGBAVCNFSM6AAAAAAWOY4CXGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNJTGEYDQOJTGM>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
-------------------------------------------------------------------------------------
Jason Calvert
***@***.***
|
Is this project being developed any more? It's fantastic when it works, but I'm finding that I am getting fairly regular read timeouts where it seems like pal loses its connection with Plex.
requests.exceptions.ReadTimeout: HTTPConnectionPool(host='127.0.0.1', port=32400): Read timed out. (read timeout=30)
It would be great if pal could somehow survive these timeouts, because when it happens, I end up having to restart the service. If it could just pick up again once the connection is resumed, that would be great.
The text was updated successfully, but these errors were encountered: