Hello, I also have the currently released version of plex (1.14.1.5488) and am running windows 10 on my htpc; I have been encountering frequent crashing, attached are my logs, could you review and ensure that this new beta/upcoming 1.15 release will resolve the crashing issues?Plex Media Server Databases_2019-02-02_12-04-23.zip (2.1 MB)
Plex Media Server Logs_2019-02-02_12-04-22.zip (1.3 MB)
No.
Appears to be rare crash in uPnP discovery. .
Could be some device on the local network returning some unexpected SSDP discovery responses or some non-standard network setup
I cannot see any local IP addresses in the logs - nor any network interface discovery.
Please look into how you setup the local network
Thank you sa2000,
I am using a netgear nighthawk R7000P with the latest firmware and nothing un-traditional about my local area setup (at least to my knowledge). Is there a log report within plex I should provide to give you what you need? Could please outline specifically what values you’d be looking for to help troubleshoot this?
I recently upgrade my htpc hardware in late december early jan, that’s the only significant change I can think of as of late but not sure how this would have effected it like that.
I appreciate your help and support!
I am surprised we have not logged the presence of any local network interface. Are you directly connected to the internet or there is a local network with subnet like 192.168.0.xx or 192.168.1.xx etc ?
Could you get me the output of ipconfig /all copied into a text file
Also check Windows Network and Internet Settings and see what it shows for Network Status and then click on Change adapter options and see if what adapters show up and if enabled
Thank you for the guidance, it appears the Network and Internet Setting mirror what I see in the ipconfig.txt file (output of ipconfig /all) in terms of what is connected and disconnected. I am not sure what the ether net 2 option is, should I try and remove that?
With the htpc upgrade I did change out the motherboard so it is a new adapter, but it’s the same manufacturer, so I hope its not hardware related.
Tell me what you see and what other info I can provide?ipconfig.txt (1.9 KB)
All look good. No need to delete anything
If the crash is predictable and can be reproduced at will, then we could run wireshark and capture packets and see what came in before the crash
For now, lets just reboot the router and after router fully operational then reboot the PC and get me another ipconfig /all and logs from Plex Media Server after 30 minutes of running - just to see that the Network Interfaces detection is logged (may be it is just a logging issue)
I did the full router reboot and then the pc shut down and power back on. Attached are the server logs from right after
rebooting.
ipconfig.post.reboot.txt (1.9 KB)
Plex Media Server Databases_2019-02-08_16-19-14.zip (2.1 MB)
Plex Media Server Logs_2019-02-08_16-19-13.zip (950.4 KB)
Here are the files from 30 min after reboot, it doesn’t appear to have crashed yet, however if I observe it does then i will open back up and extract the files and provide. Hopefully you find a clue as to what is causing it.
ipconfig.post.reboot.30min.txt (1.9 KB)
Plex Media Server Databases_2019-02-08_16-53-01.zip (2.1 MB)
Plex Media Server Logs_2019-02-08_16-52-59.zip (957.5 KB)
Thanks - i just noticed that your server local IP changed from 192.168.1.2 to 192.168.1.33 - it is best to try and make this IP fixed to avoid interruptions when it changes and the change gets detected by Plex Media Server and the client apps
Could you look into adding it to the DHCP Reservations list
Adding entry for Charon for Mac Hardware Address 70:85:C2:AE:38:27 to be fixed - decide on whether to stick with the new IP 192.168.1.33 or 192.168.1.2
After you do this restart the PC to confirm that it does have the IP that is setup in the DHCP Reservation table
Added it to the DHCP reservation list, and rebooted. I did notice prior to the reboot it took a few attempts to get the server up and running, i.e. i’d open the application… it would load… and then immediately crash. Once it stabilized I downloaded the logs and are attached below, do you see anything that stands out?
If it continues to crash I’ll download the logs and come back and look for guidance, let me know if you see anything odd or have any further actions I should take? Thank you again for your help!
Plex Media Server Databases_2019-02-09_10-36-16.zip (2.1 MB)
Plex Media Server Logs_2019-02-09_10-36-15.zip (486.3 KB)
I expect to have a development build available tomorrow with a potential fix for the memory related crashes - but I would like confirmation first that the issue is still there and then we can easily see if the upgrade to this new version makes a difference
1 Like
Yes, the issue is still there, even with version 1.15.0.659 installed. As soon as I enable automatic and partial scanning and trash emptying, I consistently get a crash in about an hour. I have been running with them disabled for more stability and have still experienced a few crashes after attempting manual scans to update my library.
1 Like
38 posts were merged into an existing topic: Server crashing after latest update to 1.15.0 - Logs included
I have sent you a link to download development build 1.15.1.686
This has changes to memory handling for the scheduler which is the area that was spiking memory usage - due to the high number of scheduled recordings.
Please update to this version and run with debug logging enabled. If you have any issues please provide logs with details of the issue and time
Thank you
Successfully installed 1.15.1.686 and debug logging is enabled.
This feedback may be premature, but I am seeing an immediate improvement in memory usage and no crashes so far with automatic library scanning and trash emptying enabled.
Previously, VMMap memory would remain at 1,700,000K, spike wildly and would keep creeping to 2GB before eventually crashing.
Currently, with version 1.15.1.686 memory in VMMap is stable at 667,648K with virtually no movement up or down.
I will continue to monitor.
Thanks.
Thanks - hopefully it is not premature !
Thanks and do let me know how it goes
It has been just over 24 hours since I installed 1.15.1.686 and I have good news to report. No crashes and PMS has been functioning as it should.
Memory usage started out at 677,648K after install and has remain stable without any wild spikes. The VMMap timeline shows the memory has remained flat, however, it has slowly crept up to its current level 807,868K, still well below the crashing point. I am not an expert with VMMap and do not know if this is normal for PMS. The memory usage does appear to be growing, but at a much slower rate. The memory has not dropped back down to the 677,648K level since install.
One thing I have noticed is the DVR recording is much better. I was consistently getting failed or partial recordings. Since I updated yesterday, I have not had any failures and everything that was supposed to record has recorded properly.
Thank you for the feedback and all your help in getting to the cause of the problem
Anytime, I appreciate your help!
