It is the same issue as I am investigating with diagnostics from a few other users
We are failing to get a dynamic tcp port
The transcoder failed at this time
Apr 10, 2020 10:57:09.075 [8920] ERROR - [Transcoder] [tcp @ 14713600] Connection to tcp://127.0.0.1:32400 failed: Error number -138 occurred
But the scanner got an error earlier
Apr 10, 2020 10:56:56.547 [1584] WARN - HTTP error requesting GET http://127.0.0.1:32400/:/metadata/updateProgressMessage?message=Scanning%20The%20Dark%20Knight%20%282008%29 (7, Couldn't connect to server) (Failed to connect to 127.0.0.1 port 32400: Address already in use)
I have not established yet if there was a change in windows recently to do with this - but I am aware that windows did have bugs in this area and this was already acknowledged in some windows updates - but not recent
For one user the problem mysteriously went away - Recording failures after update to 1.19.1 beta - #16 by sa2000
For another user the problem did not go after windows update to a later version 1909 OS build Transcoder crashes on access errors - #16 by technaholic
So we need to establish if there has been a recent windows change that impacted this or it is only down to Plex Media Server changes
The scanner logs @Subrosian in your zip only go back to Apr 10, 2020 10:56:24
Would be good to capture the first scanner error and to see after how many request (from reboot) does it arise
It may be necessary to increase number of logs - to say 20 - See registry settings for Plex Media Server and how to increase logs using LogNumFiles
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
First need to work out how to reproduce the error -
With 2600 movies - how many scans of the Movies library after a reboot does it need to give the error. There is a 5 minute wait time in windows before a dynamic port can be re-allocated. - With logs covering the first fail and covering whole period since reboot - I can establish how many requests in a given time period would lead to the error
So with a method to reproduce the error after a reboot, I would like to see if downgrading to an older version of Plex Media Server does not give the error.
1.18.9.2578 was mentioned by others and that would be one to try and if it definitely does not fail - then would like to see logs + wireshark pcap file
