I noticed that this morning there was a spike in DNS requests. Apparently about once a day my plex server makes thousands of DNS requests for both the A and AAAA records of tmsapi.plex.tv.
Jan 27 03:14:16 - 03:26:30: 5711
Jan 28 04:58:41 - 05:08:20: 2154
Does anyone have any idea of why Plex would be making so many requests?
This is on FreeBSD, if it matters.
I presume these requests are to do with the Program Guide and the updates to the EPG
+1
Also on my network meta.plex.tv , musicbrainz.plex.tv and lastfm-z.plex.tv all seem to get hammered by the server as well. Is there something which is causing Plex servers to do lots of unnecessary lookups?
Same thing, noticed 30,000+ requests at 5am to tmsapi.plex.tv.
A problem has just been identified in use of cache on the server and a fix is expected in the next beta - hopefully in PMS 1.12.3. Requests are being repeated instead of using the cached data
@sa2000 that doesn’t entirely explain why I’ve had over 100,000 requests today alone with one media server with under 500 items, an HDHR prime (no EPG).
I’ll use the linked thread to discuss/TS, just wanted to share the concern here since I already commented.
It is the DVR EPG refresh that is Fetching the data and unfortunately is repeating requests
@sa2000 I do not have the EPG feature enabled (checked) in my DVR settings.
Responding for @sa2000 at his request
@rideekulous and all who find this thread.
As stated, correction in hand and working its way through QA now. Logs and further investigation not required.
Plex Media Server version 1.12.3.4947 has just been released as beta
It has a fix for caching bug where the cache was not correctly checked before making EPG requests to tmsapi.plex.tv. With this fix, the volume of requests should reduce significantly - 75% reduction has been observed.
See Release Note http://forums.plex.tv/discussion/comment/1650553/#Comment_1650553
I’m on version 1.13.2.5102
5,388 dns requests for tmsapi.plex.tv last night
@AlVal said:
I’m on version 1.13.2.51025,388 dns requests for tmsapi.plex.tv last night
The caching that was introduced should have reduced the volume significantly. I would expect it to be less than that
Could you run with debug logging and monitor DNS requests for the period and can look into the logs
Suggest starting with a restart of the server
Might need to increase the number of log files
See Advanced setting LogNumFiles https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
Also you could check to see if there are a lot of cache files for the EPG
See directory Cache\Http v.plex.providers.epg.onconnect within the Plex Media Server data area
For debug logging
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
For downloading logs zip file see
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
