Server Version#: 1.22.2.4274 (But this has been happening for the last year or so across different PMS versions) Player Version#: Multiple Clients on different platforms (tvOS, Android TV on 2019 Shield TV Pro) spanning different versions including current versions
OS: Windows 10 version 20H2 CPU: Dual Intel Xeon E5-2690 v3 RAM: 128 GB DDR 4 Registered ECC
Reporter Story
Basically, what happens is (often) my TV Shows library gets stuck in a loop of scanning for say 5 seconds / stop scanning for say 1/10th of a second (it won’t actually say it is scanning any shows when I click on the Activity button on the top right of the NavBar) - just says “Scanning TV Shows” then stops for a tenth of a second and starts back up. This has happened for around a year through many different Server versions.
Client Symptoms
While this is happening, on my clients I notice when I go to a movie, or a show or anything - aside from the name of the show, episode or movie, all metadata will briefly disappear and change the focus (if I was previously focused on say the actors) back to the media control buttons.
Back to Server-side Info
On the server side, if I try cancelling the scan just from clicking on the kebab menu icon next to the library - it will stay stuck in the loop. If I click on Settings in the NavBar, then click on Libraries (under MANAGE) then click on the CANCEL SCAN button (next to ADD LIBRARY), it will break the loop for some time. Or I can right click on the Plex icon in the System Tray and click on Cancel library Update - this will also break the loop.
Under SETTINGS then Library, I have the following options configured Scan my library automatically (TRUE) & Run a partial scan when changes are detected (TRUE). When the server is stuck in this scanning loop, nothing is being added or removed from that library.
Thank you so so so much for taking a dive into this issue when you have time @ChuckPa
Craig
EDIT: Added at the top the following next to Server Version:
(But this has been happening for the last year or so across different PMS versions)
I see the transcoder going into sloth mode (waiting for the player)
I see the machine being throttled by Plex.tv attempting remote access (NOT GOOD). Are you trying to force it (on-off-on-off in rapid succession) ???
Apr 02, 2021 11:45:29.721 [4404] DEBUG - MyPlex: Published Mapping State response was 429
Apr 02, 2021 11:45:29.721 [4404] WARN - MyPlex: Invalid response when mapping state (code=429):
Apr 02, 2021 11:45:29.721 [4404] DEBUG - MyPlex: updating mapped state - current state: 'Mapped - Not Published (Bad Response)'
Apr 02, 2021 11:45:29.721 [4404] DEBUG - MyPlex: mapping state set to 'Mapped - Not Published (Bad Response)'.
Are you using jumbo frames on your LAN or anywhere in the chain? That’s about the only time I see this type of sluggishness.
Yeah, I am using CloudFlare for my proxy & FWIW Traefik v2.2 for a reverse proxy.
Assuming that is normal?
When you say trying to force it (on-off-on-off in rapid succession) - not sure what “it” is that is being referred to here but I am not interacting with the server, either through PMS itself or any Plex clients, I am not making any changes to my network, proxy or reverse proxy if that in a way answers this part.
Sorry I did not see #4 as I am responding on the Plex Forums mobile app at the moment. No I am not using jumbo frames on my LAN or anywhere in the chain.
Oh, no I am not turning Remote Access on and off. My Traefik reverse proxy listens on port 443 and that is what I have set my “Manually specify public port” value to (443).
Edit removed image for various reasons.
While it says “Not available outside your network”, it is still available remotely.
Good evening, @ChuckPa, I was doing some thinking and I disabled remote access via the settings page. What you said made complete sense since I already had Traefik handling remote access it was obviously conflicting with PMS. I disabled it and verified my remote clients are still able to access my server and it actually seems more stable now. Who knows maybe that was causing funky behaviour with Scanner as well!
Thanks again for your help - will keep you posted!
No rush getting to this as things are a lot more responsive due to resolving the ‘DDOS’ Remote Access (RA) issue - a problem I didn’t know I had - Honestly, I can’t say thank you enough for pointing that out. My whole network seems happier
However, the scanning loop for my TV Shows library is still occurring.
I captured another 3 sets of logs which will hopefully help us get to the bottom of this. If you are able to read through these some time when you are working next, it would be much appreciated.
That alerts is not intended to provide detail / expand by clicking.
There are also some things there which are false errors (unknown type: folder) because they are future work which is being developed. They are harmless for now.
Your scanner logs show unmatched – which it will continue to try.
Apr 03, 2021 10:07:23.608 [5800] DEBUG - HTTP/1.1 (0.0s) 200 response from PUT http://127.0.0.1:32400/activities/?percentComplete=100 (reused)
Apr 03, 2021 10:07:23.608 [5800] DEBUG - Refreshing section 2 of type: 2
Apr 03, 2021 10:07:23.677 [5800] DEBUG - The show '90 Day Fiancé: TOW Strikes Back!' has unmatched leaves, and show was matched, so we'll refresh.
Apr 03, 2021 10:07:24.725 [5800] DEBUG - The show 'Home' has unmatched leaves, and show was matched, so we'll refresh.
Apr 03, 2021 10:07:25.171 [5800] DEBUG - The show 'Mindhunter' has unmatched leaves, and show was matched, so we'll refresh.
Apr 03, 2021 10:07:25.618 [5800] DEBUG - The show 'S.W.A.T.' has unmatched leaves, and show was matched, so we'll refresh.
Apr 03, 2021 10:07:26.097 [5800] DEBUG - The show 'Welcome to the Blumhouse' has unmatched leaves, and show was matched, so we'll refresh.
Apr 03, 2021 10:07:26.185 [13356] DEBUG - Refreshing 5 IDs.
Thank you so much - I went to check those shows and I do see that there are episodes with no metadata. I confirmed on IMDB that metadata does exist for those episodes. So I just rematched the show and the metadata filled in. (Simply refreshing the metadata did not work for anyone with the same issue)
I will be sure to start giving some love to my scanner logs in the future now that I know what to do when I see that there are unmatched leaves!!!
I am certain resolving this will solve that issue so I will mark that as the solution!
- Honestly, I can’t say thank you enough for pointing that out. My whole network seems happier 
