I have looked all through the forum and I get why but no SOLUTION if I missed it I am sorry but I can not find it, so I will attempt to ask the question hopefully in a way that plex understands and the only acceptable answers, or either the server MUST do this or plex programmers will look into this ONGOING issue of users computer resources being wasted.
Again this is continuing to happen and my server is constantly pinging this address. THIS IS A WASTE of RESOURCES. This problem is all over the forum but plex has not addressed this issue. I see that you just want to explain what it is. Thatās good and all but we all want it to stop. AGAIN it is a waste of resources. PLEASE make it STOP
it is and it has been. I have nothing assigned to this IP Address. PMS has chosen to attempt to get info from this address which has no computer assigned to it. If the server was going through my entire network range I should be getting over a hundred of IP errors but no. I only get one and always the same address 192.168.0.254 and it continually tries to get info from it.
Iām guessing that address is for your router. PMS is basically pinging your router to look for devices on your network. This is nothing more than what other devices on your network do. Very little resources should be used to accomplish this. Plex could probably stop logging that but the action is needed.
Wrong Guess. For everyone out there, THIS ADDRESS 192.168.0.254 IS NOT assigned to any machine ON, IN or AROUND my network. This is an IP address that PMS has decided to ping all on its own. This IP address is also being pinged by other PMS machines as I have seen this complaint on other post (no reason or remedy has ever been given). This is something that the programmers need to address as again if it was attempting to ping all my IP addresses in my network sub net (before the dumb question is asked, my sub net is 255.255.255.0), I would be getting thousands or warning of all the IP addresses that I am not using and my machine would slow to a crawl. When any ones machine is transcoding, not wasting the machines resources is a good thing, but instead it is not, it is just this ONE IP address that it feels it must ping over and over and over and over and over and over and over and over and over and over and over and over and over (see how it becomes annoying) again. So, I will reiterate. NEVER in the history of my LAN have I ever assigned a physical machine this (192.168.0.254) IP address, NEVER, EVER. So again why does PMS waste my resources by pining this address for infinity?
In addition to the logs @anon18523487 requested, can you also provide:
The full output of running āip addrā on your system.
The ssdp.txt file which results from running the following command:
$ sudo tcpdump -vv -A -i eth0 āport 1900ā 2>$1 | tee ssdp.txt
Let this run for a minute or two, or until youāre certain the issue has been reproduced.
If eth0 isnāt your primary interface please replace it with the correct one. This command will dump all SSDP traffic in human-readable form to the console and the ssdp.txt file and should show PMSā SSDP discovery requests and all responses. The tcpdump utility should be installed by default on most Ubuntu-based distros.
The ssdp.txt file you provided only covers from around 12:11 to 12:15, so it doesnāt capture the activity displayed in the log snippet you provided. They need to cover the same time period so they can be compared. If you can, please start the tcpdump again and then monitor your logs for the error to occur again. Then wait another 30 seconds and stop the trace (Ctrl-C).
Once this is done, attach the new ssdp.txt file and logs showing the error. Also, the command below has been updated a bit:
sudo tcpdump -vv -A -n -i eno1 'port 1900' 2>&1 | tee ssdp.txt
The new capture definitely covers the correct period, but did not capture any SSDP traffic for that IP address. Iād expected to see either a discovery response or a service advertisement. If youāre interested in troubleshooting further we can try a different dump, by IP address.
sudo tcpdump -vv -A -n -i eno1 host 192.168.0.254 2>&1 | tee ssdp.txt
Ideally:
Stop Plex Media Server.
Run the command above and leave it running.
Start Plex Media Server.
Wait for the error to occur and then wait 30 seconds.
Stop the command with Ctrl-C.
If this doesnāt show anything interesting, Iāll have to puntā¦
If nothing else, this pretty definitively shows that there is nothing currently (reachable) on your network with IP address 192.168.0.254. Those ARP requests appear to be PMS trying to find the MAC address where to send its HTTP query and there is no response.
I still canāt tell you why PMS is trying to send it though. I also run a 192.168.0.0/24 network here and my PMS doesnāt try to send any traffic to 192.168.0.254; I assume that means its not hard-coded, at least not on any of my servers. I have three, my primary on macOS and two test servers, one each on Linux (Pop!_OS 19.10) and Windows 10.
Sorry I couldnāt be more help. Perhaps if you can provide those debug logs @anon18523487 requested a while back they can find something useful.
So I guess the big question would be, is the console interface in PMS just a snap shot of my entire network or is it just what plex is doing? If it is just what plex is doing then why is plex pinging all my devices? This is kinda crazy. I mean talk about wasting resources. Something is ping my .254 address all the time which is driving me crazy. I know it is just my OCD kicking in but, it does not need to happen, as I see no upside to have it constantly pinging this address. Once maybe but not every few seconds. The console shows that Plex is even pinging all my amazon devices, again unless console is just a overview of my entire network traffic and not just what plex is doing.
Iāll add that I am not the only PMS user that this address is being pinged. ( āSSDP: Error parsing device schema for http://192.168.0.254:49152/wps_device.xmlā this is from another thread where the same no solution follow up questions are being asked, the PMS user is not even on that network range.), Which leads me to believe that the console is a snap shot of what PMS is doing. So some where in the code PMS has been told to ping this address. Unless if PMS has some how gained consciousness and is doing it all on its own with no programmer input.
PLEASE will a PMS PROGRAMMER address this ISSUEā¦
PMS is checking that address because something on your network says itās there. Are you positive nothing is at that address. It might not be an actual computer, it could be a Smart Home device or a gaming device. Or some other network device like a repeater or additional access point.
Nothing Nothing at all. I am sure. Did a TCP dump nothing with that address. This is PMS doing this as I mentioned before if PMS went though my entire net/masl of 254 IPs I would have hundreds of error not just one IP address which happens to be the same IP address that amny other PMS users are having. Check your console and see if your PMS is pinging that address it might beā¦
