1.2.2 - Missing recordings (1 Viewer)

[elsmandino]

Hi,

I have just upgraded to the latest version of MP, but have twice now missed loads of recordings. What seems to happen is that it starts to record a 1 hour programme but then records it forever (it did this for seven hours the first time!). Until I stop the recording and re-set the computer, no other recordings happen.

Has anyone else had this problem or is there a setting that perhaps I need to look at (I did a fresh install for 1.2.2, thus might have picked a weird option that is messing things up).

Thanks v much.

 

[mm1352000]

Hi elsmandino

When recordings run over it can indicate problems with the network or DB connection. I'm sure that logs would show what is going on.

mm

 

[elsmandino]

Hi there,

Thanks for that, I have attached a copy of the five log files that I have found in the Server Folder for today.

View attachment 96056

View attachment 96057

View attachment 96058

View attachment 96059

View attachment 96060

Unfortunately, I am not sure what to be looking for and hopefully someone might be able to lend a hand diagnosing.

 

[elsmandino]

If it is any further help, the programme that would not stop recording was Nature's Weirdest Events, which started to record a few minutes before 8PM.

Thanks

 

[mm1352000]

Hi elsmandino

The problem is that the scheduler thread was deadlocked by a TsWriter deadlock that occurred when TV Server attempted to start the second recording ("How to Cook Like Heston"). These deadlocks have been noticed before but unfortunately at this time I don't have any silver bullet to solve them as I don't fully understand the cause. You can read a little more -->here<--. The standard suggestion is to disable CRC checking on the EPG grabber but I'm starting to think there is a more fundamental problem than that. Sorry I can't offer more information.

mm

 

[elsmandino]

Many thanks mm.

I shall certainly give that suggestion a go and see how I get on with things.

Are there any side effects from disabling the CRC checking? - to be honest, I am not sure what it really does anyway.

elsmandino

 

[mm1352000]

Hi again

No side-effects if your TV signal is reasonable. The CRC check is a way to check that the stream from the tuner is not corrupt but if performing the CRC check causes problems then it is better to disable it in my opinion.

mm

 

[elsmandino]

Thanks for very much for that - I have been trying without CRC and, as you said, it makes no difference.

Unfortunately, the same thing still happened - stuck recording a program for 21 hours - ***k

View attachment 96594

This the log - would you mind at all just checking if it is the same problem as per before please? Just so I can't start to get an idea of what is triggering this really irritating problem.

Once idea is that I did, on one of my clients, get the error "cannot play stream: 3.0" though I am not sure what time this is. Is it possible that the client computer might be messing up the server?

Thanks

 

[mm1352000]

Hi elsmandino

Thanks for very much for that - I have been trying without CRC and, as you said, it makes no difference.

Okay, well in that case you will either need to disable the DVB EPG grabbers or use process of elimination to find the channel(s) that is/are causing problems for the grabber.

This the log - would you mind at all just checking if it is the same problem as per before please? Just so I can't start to get an idea of what is triggering this really irritating problem.

I need the tv.log to be able to check, not the TsWriter log. The symptom is that when you attempt to tune a channel you will see TV Server deciding which tuner to use and then suddenly stop tuning when it hits a line containing something like GetNewSubchannel - that is when TV Server tries to communicate with TsWriter and gets locked up. At that point TV Server must be restarted to enable you to tune channels again.

Once idea is that I did, on one of my clients, get the error "cannot play stream: 3.0" though I am not sure what time this is. Is it possible that the client computer might be messing up the server?

No, trust me on this one. I am aware of the problem, I know it is annoying and I know we need to do something about it. The trouble is:
1. Finding people who have the skills to look at the problem. We have few TV Server devs and only some of them understand TsWriter enough to be able to look at the code.
2. Finding the time to try and do something about the problem. All our TV Server devs are very busy at present, both with real life and with other work. I can't force anyone to drop what they are doing to work on this.
3. Finding the cause of the problem - deadlocks like this are *incredibly* hard to resolve sometimes, especially when you can't reproduce them (I can't). It can take hours upon hours upon hours upon hours. You need a lot of luck.

mm