2013-02-10, 01:20 AM
...and this on the client.
2013-02-10, 01:20 AM
...and this on the client.
2013-02-10, 02:27 AM
(This post was last modified: 2013-02-10, 04:42 AM by mvallevand.)
I have both patches, I don't have registry files but this might show something. I was just letting it run to see if it hung. Note I stopped the recording service at 21:22.
I tried again a couple time, same thing. Martin
2013-02-10, 06:08 AM
Here is another set with this trace
Code: System.ArgumentOutOfRangeException: Value to add was out of range.
2013-02-10, 04:59 PM
mvallevand Wrote:Here is another set with this traceDid you have both patches installed? You can get this if your front end didn't have that updated TS reader.
2013-02-10, 05:02 PM
mvallevand Wrote:I have both patches, I don't have registry files but this might show something. I was just letting it run to see if it hung. Note I stopped the recording service at 21:22.So what happened, did it hang? You said you were running it to see if it hung, but don't explicitly say it hang. Either way, if is still hanging could you please also collect the stream.log as well. Thanks.
2013-02-10, 05:14 PM
It is blocked somehow, video is on one screen and it says not responding until I killed the recording service and then I get a trace error that the socket is gone and logging so it wasn't a crash. I sent this in case you wanted to fix the lease since clearly the client and server get out of sync.
The second log is a crash when I continued Martin
2013-02-10, 05:24 PM
mvallevand Wrote:It is blocked somehow, video is on one screen and it says not responding until I killed the recording service and then I get a trace error that the socket is gone and logging so it wasn't a crash. I sent this in case you wanted to fix the lease since clearly the client and server get out of sync.Sorry I'm not sure I follow you. What do you mean about the lease?
2013-02-10, 05:47 PM
The client continues to lease the live stream long after the server has stopped the stream and closed the graph.
Martin
2013-02-10, 10:21 PM
Here is my first attempt with client logging I had the same trace as the last set of logs.
Code: See the end of this message for details on invoking but this time I could continue, and then I had to stop the recording service Martin
2013-02-10, 10:27 PM
I have the server side log too if you need them. In this case because of the trace crash, recording kept on.
10/02/2013 5:20p 104,038,400 live-MTIMEHD-2637-2.ts 10/02/2013 5:14p 1,424,883,712 live-MTIMEHD-2637.ts Martin |
|