Readarr ; Causing Plex to lockup? #28

Closed
opened 2023-12-16 20:23:10 -05:00 by sickprodigy · 3 comments
Owner

Shut down readarr and now plex is working again.
Looks like it got hung up on this

Indexers unavailable due to failures for more than 6 hours: ExtraTorrent.st (Prowlarr), NZBgeek (Prowlarr), NZBFinder (Prowlarr), NZBNDX (Prowlarr), EXT Torrents (Prowlarr), DrunkenSlug (Prowlarr)	
Unable to communicate with nzbget-rcs. Name does not resolve (nzbget:6789)	
We are currently experiencing issues with our metadata provider, this will prevent user searches and author refreshes from working. We are working to solve the issue.	
Lists unavailable due to failures: GoodreadsList-Mythologies and Retellings	
Download clients unavailable due to failures: nzbget-rcs

Weird how I couldn't watch plex with it hung up. The iotop was showing high io from readarr. So figured that was the cause.

but now Plex loading again. tf. Maybe plex meta manager

Shut down readarr and now plex is working again. Looks like it got hung up on this ``` Indexers unavailable due to failures for more than 6 hours: ExtraTorrent.st (Prowlarr), NZBgeek (Prowlarr), NZBFinder (Prowlarr), NZBNDX (Prowlarr), EXT Torrents (Prowlarr), DrunkenSlug (Prowlarr) Unable to communicate with nzbget-rcs. Name does not resolve (nzbget:6789) We are currently experiencing issues with our metadata provider, this will prevent user searches and author refreshes from working. We are working to solve the issue. Lists unavailable due to failures: GoodreadsList-Mythologies and Retellings Download clients unavailable due to failures: nzbget-rcs ``` Weird how I couldn't watch plex with it hung up. The iotop was showing high io from readarr. So figured that was the cause. but now Plex loading again. tf. Maybe plex meta manager
Author
Owner

It seems plex logs are jumping righ tnow though. Plex meta manager doing it's thing on top of that crash must of been it. Don't know why readarr was having high IO though, like 1200 k/s or 12 m/s. Not a lot honestly. Was thinking it was 1200 m/s which would be a lot for the SSD i just bought. Would having 2 double the available speed in actuality? Wonder what it's max speed is anyways. Still keep getting busy .

Plex Logs: database is busy every so often.
[Req#2f5ac2] Waited over 10 seconds for a busy database; giving up.
[Req#2fb6d6] Held transaction for too long (/data/jenkins/server/3537965286/Library/MetadataCollection.cpp:523): 0.180000 seconds

Looks like it's server like 100's per second transactions. Maybe 10-20

It seems plex logs are jumping righ tnow though. Plex meta manager doing it's thing on top of that crash must of been it. Don't know why readarr was having high IO though, like 1200 k/s or 12 m/s. Not a lot honestly. Was thinking it was 1200 m/s which would be a lot for the SSD i just bought. Would having 2 double the available speed in actuality? Wonder what it's max speed is anyways. Still keep getting busy . Plex Logs: database is busy every so often. [Req#2f5ac2] Waited over 10 seconds for a busy database; giving up. [Req#2fb6d6] Held transaction for too long (/data/jenkins/server/3537965286/Library/MetadataCollection.cpp:523): 0.180000 seconds Looks like it's server like 100's per second transactions. Maybe 10-20
Author
Owner

Testing with kodi vs plex.

Seeing if it's just a plex issue or if my download speed is actually being bogged

5 mins no issues, definitely not the server. The only difference is I'm downloading straight away through local and plex.rcs1.xyz goes through cloudflare then comes back around.
So there's a lot that could go wrong in the line vs me thinking the io is what's wrong. I bet it's database is getting accessed too much. probably sqlite or something.

Interesting article about sqlite: https://www.sqlite.org/limits.html

Testing with kodi vs plex. Seeing if it's just a plex issue or if my download speed is actually being bogged 5 mins no issues, definitely not the server. The only difference is I'm downloading straight away through local and plex.rcs1.xyz goes through cloudflare then comes back around. So there's a lot that could go wrong in the line vs me thinking the io is what's wrong. I bet it's database is getting accessed too much. probably sqlite or something. Interesting article about sqlite: https://www.sqlite.org/limits.html
sickprodigy self-assigned this 2023-12-19 11:42:28 -05:00
Author
Owner

False positive. Just having other issues in general. too many containers running.

False positive. Just having other issues in general. too many containers running.
Sign in to join this conversation.
No description provided.