Says Error running recording job, after recording job completes

Second time this has happened. Looks like a timing issue.
Recording completes successfully, connection closes, then error appears.

2025/01/03 11:59:30.003255 [DVR] Starting job 1735934370-105 Ancient Mysteries With Leonard Nimoy on ch=[9026]
2025/01/03 11:59:31.365328 [TNR] Opened connection to M3U-frndlyTV for ch9026 Story Television
2025/01/03 11:59:31.389144 [DVR] Recording for job 1735934370-105 from M3U-frndlyTV ch9026 into "TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg" for 1h1m29.966317135s
2025/01/03 11:59:31.740886 [IDX] Generating video index for job 1735934370-105
2025/01/03 13:01:21.044866 [TNR] Closed connection to M3U-frndlyTV for ch9026 Story Television
2025/01/03 13:01:21.383409 [SNR] Buffer statistics for "TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg": buf=0% drop=0%
2025/01/03 13:01:21.383498 [SNR] Streaming statistics for "TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg": timeouts=0 segment_timeouts=0 playlist_timeouts=0
2025/01/03 13:01:21.485601 [MTS] Statistics for "TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg": discontinuity_detected=0 transport_errors=0 saw_pcr=true saw_pmt=true highest_pts=3715.966667
2025/01/03 13:01:21.547113 [DVR] Error running job 1735934370-105 Ancient Mysteries With Leonard Nimoy: Could not fetch playlist: https://sr-live-weigel1.akamaized.net/v1/manifest/840a24ccd7c75076211d060179b3ad0c64fdc6ca/weigel_movies_nr_rt_new/149b1753-12e4-4e16-ad7d-5736f07a28f4/hdntl=exp=1736020770~acl=%2f*~data=hdntl~hmac=915beb4f6e9c24090b30da808c5a3cebf9ac9847a50e437c9029d704bc3f0b03/1.m3u8: Get "https://sr-live-weigel1.akamaized.net/v1/manifest/840a24ccd7c75076211d060179b3ad0c64fdc6ca/weigel_movies_nr_rt_new/149b1753-12e4-4e16-ad7d-5736f07a28f4/hdntl=exp=1736020770~acl=%2f*~data=hdntl~hmac=915beb4f6e9c24090b30da808c5a3cebf9ac9847a50e437c9029d704bc3f0b03/1.m3u8": Stream closed
2025/01/03 13:01:22.704854 [DVR] Processing file-2885: TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg
2025/01/03 13:01:23.436343 [IDX] Generating video index for file-2885: TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg
2025/01/03 13:01:23.514586 [DVR] Running commercial detection on file 2885 (TV/Ancient Mysteries With Leonard Nimoy/Ancient Mysteries With Leonard Nimoy 2025-01-03 The Lost Treasure of the  2025-01-03-1159.mpg)
2025/01/03 13:01:40.776599 [IDX] Finished video index generation for file-2885 in 17s
       Start time 11:59:31.389144
+  Recording time 01:01:29.966317135
=     Finish time 13:01:01.355461135
Closed connection 13:01:21.044866
     Error logged 13:01:21.547113

highest_pts=3715.966667 says it recorded for 01:01:55.966667
My video editor says the recorded duration is 01:01:55.96

Screenshot 2025-01-03 at 13-52-27 Channels Calendar


The log indicates that the recording started just before noon and ended just after 1pm. Then there is a second attempt to record just after 1pm that fails. Next the log shows the commercial skip ran and succeeded.

So basically, there is some noise in your log yet your desired recording is fine. As this has happened before, and you seem to want a clean log, take a look at the pass for this show as it may be the source of the second recording event.

No second attempt. It recorded normally without interruption.
There is a timing/race condition in Channels DVR causing it to display the recording as failed.
The error appears after the connection to the source is closed.
As though one part of Channels DVR didn't know what the other part was doing.
It shouldn't be trying to read from the stream after it closes the source connection.

My guess is they're verifying the stream has stopped after the connection is closed.

I’ll check it out.

1 Like

Thanks.
I don't have anything recording on that server today, so I picked 4 random 30 minute shows to record from that source at 12:30, 13:30, 14:30 and 15:30. If any fail I'll submit diagnostics.
Running the latest pre-release 2025.01.05.0701

This should fix the issue.

1 Like

Thanks.
My first two random recordings were fine.
I just now updated pre-release and will let you know if any more issues.

The previous recording having the same issue was on 12/28/2024, same source and channel.
I manually scheduled recordings on that channel (FrndlyTV-Story) for the next 14 days. One at 5am and one at 5pm each day. Will post back if issues, or if none after 14 days. :crossed_fingers:

UPDATE: 14 recordings over 7 days and all good so far. Have recordings scheduled for 7 more days.

32 recording from the same channel over 2 weeks and no more errors.
You fixed it.

1 Like