recording service stopped

[snagglewest]

I installed the .dll, flushed all the old logs and rebooted so we'd start fresh.  The good news is I got the error on the first try. 

Scheduled 2 recordings, Morning Express With Robin Meade_20200311_09001000.ts which was scheduled to stop at 10:02  and MSNBC Live With Stephanie Ruhle_20200311_09001000.ts which was supposed to end at 10:00 (both set for default  2 min post padding) .  Live TV was also running on WAVY-HD.  About 10:04ish I noticed live TV locked up.

  This time MSNBC Live With Stephanie Ruhle_20200311_09001000.ts continued recording and didn't stop until I restarted the service like we saw once before.  I know it was recording because the file kept growing and the main GUI page showed it highlighted orange indicating it was recording.  The weird bit is the one scheduled to stop at 10:00 continued to record and the one scheduled to end at 10:02 stopped normally.  Not sure what that means.

Here's logs before I restarted the service and a set after I restarted if it helps.


  logs-20200311-1006.zip (Size: 106.16 KB / Downloads: 3)

  logs-20200311-1008.zip (Size: 67.54 KB / Downloads: 3)

[snagglewest]

I'm guessing these logs aren't much use.  It looks like it's logging 1,000 times a second when the error kicks which is filling the logs in no time.  Is there a way to enlarge the log size or force it to keep more than 4 logs?  From what I can tell it's only giving me about 9 sec of reaction time before the log rolls over.

[snagglewest]

Sub,  I tried again to grab some useful logs.  I scheduled 2 recordings to end at 18:00, both with 2 min post padding.  The recordings were Redskins Nation_20200311_17301800.ts & Pardon the Interruption_20200311_17301800.ts  I didn't get a full lock up, but noticed a short blip in the live TV, maybe 2 sec  so I immediately grabbed some logs.  I noticed this error in the area of both recordings in the log.  In the recording folder both appear to have successfully completed as the ts.map file was gone.  Should have mentioned in the last set we had that locked up the ts.mp was left in both folders.  I didn't realize the  significance until now,  but I'll keep an eye on that too in the future.

Code:

2020-03-11 18:02:11.975    [DEBUG][8]    Closing TSWriter...: /mnt/recordings/PardonRedskins Nation_20200311_17301800.ts

Pardon the Interruption_20200311_17301800.ts the Interruption/Pardon the Interruption_20200311_17301800.ts
2020-03-11 18:02:11.977    [ERROR][34]    Unexpected error writing to OutputSink: System.ObjectDisposedException: Cannot access a closed file.
   at System.IO.FileStream.ValidateReadWriteArgs(Byte[] array, Int32 offset, Int32 count)

  logs-20200311-1802.zip (Size: 1.03 MB / Downloads: 3)

[mvallevand]

I have to laugh about the irony in this quote " Pardon the Interruption_20200311_17301800.ts I didn't get a full lock up, but noticed a short blip "

Martin

[snagglewest]

Yea, on the first read of the logs I thought "Pardon the Interruption" was part of Subs error trapping 

[sub]

Sub,  I tried again to grab some useful logs.  I scheduled 2 recordings to end at 18:00, both with 2 min post padding.  The recordings were Redskins Nation_20200311_17301800.ts & Pardon the Interruption_20200311_17301800.ts  I didn't get a full lock up, but noticed a short blip in the live TV, maybe 2 sec  so I immediately grabbed some logs.  I noticed this error in the area of both recordings in the log.  In the recording folder both appear to have successfully completed as the ts.map file was gone.  Should have mentioned in the last set we had that locked up the ts.mp was left in both folders.  I didn't realize the  significance until now,  but I'll keep an eye on that too in the future.

Code:

2020-03-11 18:02:11.975 [DEBUG][8] Closing TSWriter...: /mnt/recordings/PardonRedskins Nation_20200311_17301800.ts

Pardon the Interruption_20200311_17301800.ts the Interruption/Pardon the Interruption_20200311_17301800.ts
2020-03-11 18:02:11.977 [ERROR][34] Unexpected error writing to OutputSink: System.ObjectDisposedException: Cannot access a closed file.
   at System.IO.FileStream.ValidateReadWriteArgs(Byte[] array, Int32 offset, Int32 count)

Yeah, annoyingly those two appear have completed successfully, so don't show the situation.

I've attached another which should get rid of the 'Cannot access a closed file' messages during the closing. It may also be a factor in the root issue - I'm not sure though.

[snagglewest]

I'll give it a go, but it'll be Saturday before I get a chance. Got 2 days of doubles coming up so I won't have any time to test until then.

[sub]

Ok no worries

[snagglewest]

Sub, haven't has a chance to install the new .dll yet, but last night at about 22:02  I had another short blip with live TV when a recording stopped.  I did get a chance to grab a quick set of logs which might help you though.  It flooded the log for a short time with the "Unexpected error writing to OutputSink" error, but it looks like it eventually cleared itself up.  If it helps I found this at 22:02:00.929.  As a side note, this was noticed on a different TV than the other logs I've sent you.  If it helps to sort things out the main TV is 192.168.1.7,  the laptop I usually access the web ui is 192.168.1.109 and the TV I noticed the blip on is 192.168.1.10, all static IPs. Either way I'll get the new .dll installed this weekend and keep trying.

Code:

2020-03-11 2.2:02:00.929    [DEBUG][8]    Closing TSWriter...: /mnt/recordings/SEAL Team/SEAL Team.S03E14.Objects in Mirror.ts
2020-03-11 22:02:00.930    [ERROR][28]    Unexpected error writing to OutputSink: System.ObjectDisposedException: Cannot access a closed file.
   at System.IO.FileStream.ValidateReadWriteArgs(Byte[] array, Int32 offset, Int32 count)
   at System.IO.FileStream.Write(Byte[] array, Int32 offset, Int32 count)
   at NShared.Writer.OutputSink.Write(Byte[] data, Int32 offset, Int32 length)

  logs-20200311-2218.zip (Size: 1.22 MB / Downloads: 0)

[snagglewest]

Installed the new .dll this am and tried a number of times to create an error  with 2 simultaneous recordings with no luck so I gave it shot with 4 and got a lock up about 15:02 or so.  The recordings didn't all end exactly at the same time, but within a second or so.  It looks like the problem happened on the last recording (Chopped sweets) and I did notice something interesting.  The recordings normally complete and leave an .xml file.  In this case the Chopped Sweets recording didn't have a .xml, just a .ts.map which I'm guessing might be helpful info.  Now that I think about it, I have in the past noticed the left over .ts.map but didn't relate it to the problem.  I'll keep an eye on that to now too.  Here's a list of the recordings and their stop times along with some logs, hopefully they are useful and not too dirty with all the messing around to get a error.

Country Music.S01E02.Hard Times (1933-1945).ts - ended at 3:02:00 PM (created .xml file)
Emeril Pressure Airfryer_20200314_14301500.ts - ended at 3:02:01 PM (created .xml file)
The Office.S07E20.Training Day.ts - ended at 3:02:02 PM (created .xml file)
Chopped Sweets.S01E07.Million Dollar Desserts.ts - ended at 3:02:02 PM ( no .xml, only .ts.map file)

  logs-20200314-1502.zip (Size: 1.43 MB / Downloads: 6)