Recordings don't stop, end up 40+gb! (1 Viewer)

[Wizard_TPG]

I had a recording that did not stop again last night.
My machine had been rebooted about an hour before.
Does not seem to be anything I can put my finger on as to why this is happening.

 

[KevinCostner]

Same problem here

Hi guys!
I've got the same problem as described with MPS 1.0 RC1 and RC2:
minimum once a week a randomly EPG recording doesn't stop until I stop and restart the TVService.

What I found in tv.log:
a "good" recording stops like this:

2008-10-16 18:55:19.703125 [6]: diskmanagement: recording Marienhof ended. type:Once max episodes:2147483647
2008-10-16 18:55:19.703125 [6]: ConflictManager: Updating conflicts list
2008-10-16 18:59:16.531250 [6]: Schedules List built 236828,125 ms
2008-10-16 19:03:48.484375 [6]: ConflictManager: Update done within 508781,25 ms
2008-10-16 19:03:48.500000 [6]: Scheduler: stop record Das Erste 16.10.2008 18:20:23-16.10.2008 18:50:00 Marienhof
2008-10-16 19:03:48.515625 [4]: card: StopRecording 1
2008-10-16 19:03:48.515625 [4]: card: StopRecording for card:1
2008-10-16 19:03:48.515625 [4]: analog:StopRecord()
2008-10-16 19:03:48.546875 [4]: analog: Encoder mode setting to VariableBitRateAverage
2008-10-16 19:03:48.578125 [4]: analog: Encoder mode set to VariableBitRateAverage
2008-10-16 19:03:48.578125 [4]: analog: Encoder BitRate setting to Medium
2008-10-16 19:03:48.578125 [4]: analog: Encoder BitRate Min 2500000 Max 8500000 Delta 1
2008-10-16 19:03:48.625000 [4]: analog: Encoder BitRate set to 6460000
2008-10-16 19:03:48.625000 [4]: card: remove user:scheduler597 sub:0
2008-10-16 19:03:48.625000 [4]: user:scheduler597 remove
2008-10-16 19:04:00.984375 [4]: card: free subchannel sub:0
2008-10-16 19:04:00.984375 [4]: tvcard:FreeSubChannel:1 #0
2008-10-16 19:04:00.984375 [4]: analog subch:0 Decompose()
2008-10-16 19:04:00.984375 [4]: Analog: StopTimeShifting()
2008-10-16 19:04:01.750000 [4]: analog: StopGraph state:Running
2008-10-16 19:04:02.187500 [4]: analog: Graph stopped
2008-10-16 19:04:02.218750 [4]: analog: StopGraph state:Stopped

a "bad" never ending recording looks like this:

2008-10-16 22:30:14.421875 [17]: diskmanagement: recording Odysso - Wissen entdecken ended. type:Once max episodes:2147483647
2008-10-16 22:30:14.484375 [17]: ConflictManager: Updating conflicts list
2008-10-16 22:32:46.578125 [17]: Scheduler: stop record SWR 16.10.2008 22:00:17-16.10.2008 22:30:00 Odysso - Wissen entdecken
2008-10-16 22:32:49.484375 [7]: card: StopRecording 1

That's all!! Next entries are the schedules for next recordings which will fail because of the TV card still busy.

This is what I found in error.log:
2008-10-16 22:32:54.843750 [7]: card: unable to connect to slave controller at:hpc


This is very annoying, because You'll have to keep the TV Server under observation to not miss any recording.

If I can help anyhow to find out more - please let me know.


Karsten

 

[Klathman]

I had this same problem but it was consistently failing to stop.

In the end I turned off the comskip plugin in TV Server and all seems good again.

I doubt that it is the plugin itself that it causing the problem but maybe the version of comskip I was using. I have had it working fine in the past but have recently rebuild on vista and as part of this downloaded the latest comskip version. Other than that the config should be the same including it starting when the recording starts.

I tried a full reinstall including deleting the DB and config files but this didn't seem to make a difference. What I didn't think about is that each time I set it back up I enabled comskip just as standard behaviour.

Would be interesting to see if the same thing works for others.

 

[KevinCostner]

Thank You Klathman! But I do not use the comskip plugin. I only use conflicts manager.
I think the problem is related to the "unable to connect to slave controller" error which I found in the error.log. Does anyone else have such error.log entries?

Cheers,
Karsten

 

[HappyTalk]

I upgraded to rc3 over weekend and today I had a recording that had filled all remaining space on the drive so MP could no longer work. Previously I had MP set to delete recordings to free up space which meant when this happened it deleted every single recording on the drive to allow for the rogue recording to eat up the space

IMHO this is the worst bug currently in mediaportal as it makes it pretty much unuseable. If as indicated at start of thread it is unlikely to get fixed I'll have to dump MP and go to MCE, which I've avoided doing as I like the multiplex record in MP. Though it just occured to me if I added another dual tuner card so I had 4 then this would be much less of a problem. Features are great but not if the core functionality is broken.

 

[tourettes]

HappyTalk, as you can see there isnt that many people who can reproduce the issue you are having, so fixing it is almost impossible.

Did you do a complete clean install when installing RC3?

 

[KevinCostner]

Hi HappyTalk!
Last night I got that issue again.
What about Your LOG-Files? Could You please have a look at those snippets I posted above - maybe You can find something like that in Your LOGs too?
It seems as if none of the current development team is really interested in this issues - so maybe I've to get the dev environment and debug it myself.
Cheers,
Karsten

 

[HappyTalk]

Yes I totally uninstalled mp then installed rc3. I didn't reinstall sql server, but each rc uses a new database. I understand that it may be hard to reproduce BUT if you examine the code that actually stops the recordings and see how it handles errors. When it tries to close the file and can't maybe due to file locking or something what does it do. Maybe exceptions get swallowed?

Alternatively maybe (wild guess) if you are recording 2 programs on same multiplex on same card and one program finishes while the other doesn't, maybe it doesn't stop the first one. I think I have 3+ recordings at some time later tonight so I'll see tomorrow.

If logs indicate nothing awry then the code that decides its time to end a recording is maybe failing under certain circumstances.

Is there an option to rename/move a file after recording is finished. If so this would fail as file would still be recording and so locked.

To Mr Kostner, I posted logs in the first posts of this thread. I see others have now posted on here, so I am not alone, likely many more than would come on here to post.

 

[tourettes]

but each rc uses a new database

Unfortunately RC2 and RC3 use the same DB name.

 

[HappyTalk]

I C, I had uninstalled rc2 so I'm not sure if DB was still there. It has only happened once so far on rc3 so seems better than rc2. Next time it happens I will look at the db to see if the record is wrong. That said I can't remember from my original logs if it thought it had tried to stop recording but had been ignored or had never tried.