Reply to thread

Message: <blockquote data-quote="mm1352000" data-source="post: 873973" data-attributes="member: 82144">Hi again It is the server getting itself turned inside out. Technically what we'd call a "subchannel leak" I guess. You didn't have to have more than 1 recording scheduled. The issue is the continual failure to start that one recording. TV Server tries each of your tuners in turn and seems to fail to start the recording on all of them... and crucially, it does not free the tuner for later use after the failed recording attempt. Finding the subchannel leak would be hard and more timeconsuming than I have time for at present. In my opinion it would be more more productive to try and figure out why the recordings are failing to start. I've seen issues like this before, and I've looked at the corresponding code and never been able to nail down exactly where the problem is for certain. However I'm 90% certain the issue is related to networking. So to give you a more detailed run down of what I see...The last thing I see before the problems start is somebody starting to watch Channel 5 at about 6:50am on the morning of the 8th. After that there is basically no real activity until just after 3pm when the scheduler wants to record Countdown on Channel 4 HD. This recording fails at the first attempt, and there the problem seems to really take off. I see very regular "card: unable to connect to slave controller at:HTPC-PC" messages in the error log starting at about 8:30am, and these seem to point to a network connectivity issue starting at that time. I can't see any evidence of a change of IP address in the system logs, so I can't be sure what happened - just that "something bad" happened... TV Server is very heavily reliant on a stable network connection for stable operation. The network connection is used for communication with the database (which contains the schedules, channels etc.) and all MP front ends (even on a standalone installation). Those connections are such a core part of the MP TV "system" that when the network goes down, bad things happen. My standard recommendation to people is that they always use a static IP address on the TV Server, and wired networking where possible - wireless connections seem to have a nasty habit of dropping in and out on occasion. For ultimate reliability, the MS loopback adapter (which is like a dummy network connection) is available, however that is not compatible with a multi-seat installation so is of limited use. I'm afraid that is all the insight I have for you. I can't prove or explain exactly what happened, but I've told you what I suspect is the general cause. Hopefully my comments make sense... mm</blockquote>

Verification