Multiple "airing was in progress" errors popping up

General Discussions Plex Features
1

Last night I noticed that two of my TV Shows did not get recorded. I’ve seen this happen before with a typical ‘airing was in progress’ error since I have them set to not start if they miss the start time (to prevent episodes from being incomplete).

Then just now (4 minutes ago), the same thing happened to another TV recording (the mist and zoo last night, star trek just now)

I’ve attached server logs in case they’re of help. My system has been online (for days) so it’s not like they weren’t able to start recording when the time came.

2

Error is not very descriptive is it. This is all I see in the log you submitted:

Aug 18, 2017 15:45:00.982 [0x2b89a1200700] DEBUG - DVR:Grabber: Starting operation for ‘Star Trek - E24 - Turnabout Intruder’.
Aug 18, 2017 15:45:00.982 [0x2b89a1200700] DEBUG - Activity: registered new activity b14f5fc6-e63e-4218-ac3a-ca7dbbc5f86e - Recording
Aug 18, 2017 15:45:00.982 [0x2b899b001700] DEBUG - Completed: [10.0.0.39:59746] 200 GET /status/sessions/background (21 live) TLS GZIP 0ms 397 bytes (pipelined: 355)
Aug 18, 2017 15:45:00.982 [0x2b89a1200700] DEBUG - DVR:Grabber: HDHomerun starting a media grab on device device://tv.plex.grabbers.hdhomerun/13259206 (Silicondust HDHomeRun PRIME, supported) tuner 0.
Aug 18, 2017 15:45:00.983 [0x2b899ae00700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Aug 18, 2017 15:45:00.983 [0x2b899ae00700] DEBUG - Auth: authenticated user 1 as Endda
Aug 18, 2017 15:45:00.983 [0x2b899ae00700] DEBUG - Auth: Came in with a super-token, authorization succeeded.
Aug 18, 2017 15:45:00.983 [0x2b89a2e06700] DEBUG - Request: [10.0.0.39:59747 (Allowed Network)] GET /status/sessions/background (20 live) TLS GZIP Signed-in Token (Endda)
Aug 18, 2017 15:45:00.983 [0x2b89a1200700] DEBUG - DVR:Subscription: Resolved subscription to library item ‘Star Trek’ (32142)
Aug 18, 2017 15:45:00.983 [0x2b899b001700] DEBUG - Completed: [10.0.0.39:59747] 200 GET /status/sessions/background (20 live) TLS GZIP 0ms 470 bytes (pipelined: 279)
Aug 18, 2017 15:45:00.984 [0x2b89b7c05700] DEBUG - DVR:Grabber: Freed a tuner (now 3 available)
Aug 18, 2017 15:45:00.984 [0x2b89b7c05700] DEBUG - DVR:Grabber: Recording for ‘Star Trek - E23 - All Our Yesterdays’ stopped with status cancelled.
Aug 18, 2017 15:45:00.984 [0x2b89b7c05700] DEBUG - DVR:Grabber: Scheduling ‘Star Trek - E23 - All Our Yesterdays’ for assimilation.
Aug 18, 2017 15:45:00.984 [0x2b89a380b700] DEBUG - DVR:Recorder: Asked to stop recording ‘Star Trek - E23 - All Our Yesterdays’.
Aug 18, 2017 15:45:00.985 [0x2b899b202700] DEBUG - DVR:Subscription: Resolved subscription to library item ‘Star Trek’ (32142)
Aug 18, 2017 15:45:00.985 [0x2b89a1200700] DEBUG - There were 1 top-level paths for Star Trek.
Aug 18, 2017 15:45:00.986 [0x2b89a1200700] DEBUG - DVR:Grabber: Saving recording to /DVR/.grab/7a3318be5377596e616fee0cdddbd7bf7a93823b
Aug 18, 2017 15:45:00.987 [0x2b899b202700] DEBUG - There were 1 top-level paths for Star Trek.
Aug 18, 2017 15:45:00.987 [0x2b899b202700] DEBUG - DVR:Grabber: Postprocessing, we’re going to put Star Trek - E23 - All Our Yesterdays in /DVR/Star Trek (1966)/Season 03/Star Trek (1966) - S03E23 - All Our Yesterdays.ts
Aug 18, 2017 15:45:00.988 [0x2b899b202700] DEBUG - DVR:Grabber: Moving /DVR/.grab/8f4087c929d624f4ab05b25fafff594d83412030/Star Trek (1966) - S03E23 - All Our Yesterdays.ts to /DVR/Star Trek (1966)/Season 03/Star Trek (1966) - S03E23 - All Our Yesterdays.ts
Aug 18, 2017 15:45:00.989 [0x2b89a7a02700] INFO - Library section 1 (TV Shows) will be updated because of a change in /DVR/Star Trek (1966)/Season 03
Aug 18, 2017 15:45:01.023 [0x2b899ae00700] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Aug 18, 2017 15:45:01.023 [0x2b899ae00700] DEBUG - Auth: authenticated user 1 as Endda
Aug 18, 2017 15:45:01.023 [0x2b899ae00700] DEBUG - Auth: Came in with a super-token, authorization succeeded.
Aug 18, 2017 15:45:01.023 [0x2b89a6602700] DEBUG - Request: [10.0.0.39:59746 (Allowed Network)] GET /status/sessions/background (18 live) TLS GZIP Signed-in Token (Endda)
Aug 18, 2017 15:45:01.024 [0x2b899ae00700] DEBUG - Completed: [10.0.0.39:59746] 200 GET /status/sessions/background (18 live) TLS GZIP 0ms 397 bytes (pipelined: 356)
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Grabber: Going to record for 4499 seconds, final URL is http://10.0.0.3:5004/auto/v756
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Grabber: Setting timer to stop grab of ‘Star Trek - E24 - Turnabout Intruder’ in 4499 seconds.
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Grabber: Waiting for a tuner (3 available).
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Grabber: Allocated a tuner (2 left)
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Recorder: Asked to stop recording ‘Star Trek - E23 - All Our Yesterdays’.
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Grabber: Freed a tuner (now 3 available)
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] ERROR - DVR:Recorder: Error 3 (The recording was aborted) starting the record, shutting things down.
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Recorder: Asked to stop recording ‘Star Trek - E23 - All Our Yesterdays’.
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - DVR:Grabber: Operation for Star Trek - E24 - Turnabout Intruder completed with status error (The recording was aborted)
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] DEBUG - Activity: Ended activity b14f5fc6-e63e-4218-ac3a-ca7dbbc5f86e.
Aug 18, 2017 15:45:01.049 [0x2b89a1200700] ERROR - DVR:Grabber: Starting media grab failed.

As your Star Trek E23 is finishing Plex tries to start recording E24 which is aborted. No real error message to describe the error other than Error 3. Perhaps a Plex Employee @keithah or @BigWheel or a Plex Ninja @DaveBinM can provide some more insight into what an Error 3 is.

3

Hmmm. I can’t say I personally know what error 3 is, but I’ll see if I can find out. If it’s something that’s happening consistently, having a sample directly from the tuner could be useful too. Essentially the idea is to capture a raw stream from the tuner in the time before, during, and after the error (which can be useful in reproducing). I’ll have a look at the logs in the morning… getting pretty late here!

4

@DaveBinM said:
Hmmm. I can’t say I personally know what error 3 is, but I’ll see if I can find out. If it’s something that’s happening consistently, having a sample directly from the tuner could be useful too. Essentially the idea is to capture a raw stream from the tuner in the time before, during, and after the error (which can be useful in reproducing). I’ll have a look at the logs in the morning… getting pretty late here!

It’s not like it happens on every recording, but I have seen it pop up time and time again (probably a dozen or two times since I started using it, which was a month or three after Plex DVR was launched).

I’m not sure what type of sample you’re looking for (a Plex DVR recording in .TS format?) or just some logs that I can pull from the tuner? I have gone through and enabled the ‘allow partial airings’ option, just because I shouldn’t have to babysit this type of stuff. That was three shows in 2 days that were missed, and I would rather have a minute or two cut from the start of the show than to miss anymore (and have to baby sit the DVR schedule).

thanks looking into the issue for me. Let me know if you find anything in the logs (when you have time) and/or if I can help isolate this issue somehow

5

To capture a stream what he would need is from a command line issue a curl command with the URL Plex tried to record sending the output to a file. I think the command would look something like: Curl http://10.0.0.3:5004/auto/v756 > testfile.ts, not at a computer at the moment to verify syntax.

6

@johnm_ColaSC said:
To capture a stream what he would need is from a command line issue a curl command with the URL Plex tried to record sending the output to a file. I think the command would look something like: Curl http://10.0.0.3:5004/auto/v756 > testfile.ts, not at a computer at the moment to verify syntax.

How long do I let this run? Just until it completes?

7

I would only let it run for 10-20 seconds unless he wants a longer capture.

8

@DaveBinM said:
Hmmm. I can’t say I personally know what error 3 is, but I’ll see if I can find out. If it’s something that’s happening consistently, having a sample directly from the tuner could be useful too. Essentially the idea is to capture a raw stream from the tuner in the time before, during, and after the error (which can be useful in reproducing). I’ll have a look at the logs in the morning… getting pretty late here!

Not sure if this is what you want, since I can’t predict when the error will happen, so I can’t prepare ‘before, during and after’. This was just taken during a random time when Plex wasn’t recording anything

9

What @johnm_ColaSC said is right about the capturing of data (I was trying to find the post I made with instructions, but it was 1am, and I was replying on my phone). Unfortunately though, a capture that occurs while Plex isn’t recording and doesn’t exhibit that issue isn’t much help. It really needs to be a capture from when Plex is recording and the issue occurs. I appreciate it can be a little annoying to do that sort of thing (having done it many times myself), but unfortunately it’s the only way to get an issue like this resolved.

10

@DaveBinM said:
What @johnm_ColaSC said is right about the capturing of data (I was trying to find the post I made with instructions, but it was 1am, and I was replying on my phone). Unfortunately though, a capture that occurs while Plex isn’t recording and doesn’t exhibit that issue isn’t much help. It really needs to be a capture from when Plex is recording and the issue occurs. I appreciate it can be a little annoying to do that sort of thing (having done it many times myself), but unfortunately it’s the only way to get an issue like this resolved.

Yea… “little annoying” is an extreme understatement. I have a job, I have responsibilities and this is a product/service that I pay for (and recommend to tens of thousands time and time again with my online presence). I am perfectly fine helping out when I can (the last bug I had to deal with for Plex 2 two months of going back and forth before the origin was discovered).

But no, I’m not going to babysit the DVR recording schedule and type in a command through Putty in hopes of striking gold here. Hopefully the setup I have going now will eliminate the issue, but if I see too many negative results (cutting off too much of a show) then I’ll look elsewhere.

I tried out Emby while I was working through that last bug that took two months to fix. . .and there are dozens of other PVR/DVR solutions out there. Thanks for the response though