I’m running PMS Version 1.11.1.4730 on a Synology DS1815+. DVR will record a couple shows, then just stop recording altogether. I’ve missed days of content multiple times due to this. I just now looked at the logs, and I see several errors in several of the logs (attached). Everything worked great until an update or two ago (I don’t keep up with when I install a certain version, but I will from now on).
I have a similar installation with PMS and Synology. Running PMS on Windows 10 box with amble CPU (i5 @ 2.5GHz) with 8GB of RAM. I am experiencing similar issues. The HDHomeRun application tunes to stations without fail, but the PMS gives me a message that it is unable to tune to the channel. The PMS process grinds to a halt - 0% CPU used.
Update: I just checked the recording schedule vs the program guide. The recording schedule for today looks nothing like what the program guide says should be airing today. Additionally, none of the programs from yesterday have the “Play” symbol on them, and the shows that should be currently recording do not have the “Record” symbol on them. I restart PMS and everything seems to refresh, but now my Recording Schedule does not show any shows for the past several days, which I assume indicates that they haven’t been recorded.
Would be great to know if this issue is limited to a platform (NAS vs Linux vs Windows) and if there is a workaround.
Update: The issue has persisted even through all the recent PMS updates that have been released. Now, the issue is that PMS stops running completely on my NAS. Just upgraded to 1.12.3.4973, but I don’t see anything related to this problem in the release notes. Anyone able to help?
I have a similar issue. Records fail after a few seconds or few minutes. They show as completed. Logs say signal interruption. Here is the stinger, i switched back to my plex dvr on my Shield and everything records fine, whole week of recordings with no issue. went back and tried Windows 10 AND windows 7, both same failures on 2 different workstations.
i’m out of ideas.
I had this issue running PMS on a Synology NAS. Recordings ending shortly “successfully”. Sometime only few seconds, other times few minutes. I stopped using PMS on my NAS for the last 4 months. 2 days ago, I decided to give it another try. Updated to the latest plex pass version. Same thing. Since I didn’t care about the metadata on this install, I did a clean install. I flushed everything related to plex on my NAS and started from scratch. It’s been running flawlessly since. It’s only been 2 days with around 30 recordings. I don’t know if it will last or not. The only difference is that I did not activate hardware acceleration yet. But since I don’t transcode on the fly the recordings, I don’t see why this would be related.
What tuner do you have? If it’s HDhomerun and if you are using an ethernet link, 1 thing that may be the cause could be burst of packet loss. Since you are on windows, I would try silicondust recommendations about network card settings:
https://forum.silicondust.com/forum/viewtopic.php?t=5877
I don’t say this is the issue, but worth the try.
This is of some interest also. I have solved most issues of timeouts setting tcp to 28800 (in linux/ubuntu 16.04)
The number of seconds a connection needs to be idle before TCP begins sending out keep-alive probes. Keep-alives are only sent when the SO_KEEPALIVE socket option is enabled. The default value is 7200 seconds (2 hours).
For example set value to 2400 seconds:
echo 2400 > /proc/sys/net/ipv4/tcp_keepalive_time
You can make changes to /proc filesystem permanently using /etc/sysctl.conf
