"The response ended prematurely"

[mvallevand]

Edit: so after some digging I am quite sure that some hardware defects of my external drive caused some of the failures with interrupted streams. But this should not be the reason for the "The response ended prematurely" error.

Why not?  If the stream writer from the tuner gets blocked freezing the tuner server that good actually explain this error.

Martin

[mvallevand]

Also, see my reply earlier (#42). I still have this happen from time to time. Every once in a while, a show/movie scheduled to record will fail with this error, and if the item is being repeated later in the week, it gets the same error on every occurrence. If I notice it, I will create a manual schedule entry for one of the repeats, and that always works. Obviously, if it isn't repeated, I'm out of luck. The one I can always count on is the Ed Sullivan Show. This airs once a week, on Sunday nights. The schedule data sometimes shows the series name as "Ed Sullivan Show" and other times "The Ed Sullivan Show", so I originally had 2 recurring items to capture both. But the one for "The Ed Sullivan Show" failed every time, so now, when I see "The Ed Sullivan Show" is coming up, I create a manual schedule entry and that works.

Your error in #42 is exactly the same as phu is seeing.

Martin

[phu]

I changed the npvr settings to save to sdcard in order to test if the error has something to do with the hard drive. Unfortunately tonight the same error occurred again (also on the same channel again), logs attached (at least I tried uploading them but it seems do be not working - is it possible that I am not able to upload atm?). Sidenote: the last minute of the failed film has been recorded normally within the pre-padding time of another film.

[nappysolo]

I have compiled a list of TV shows (currently 8 of them) for which the following is true:
- any episode scheduled to record (from the guide or search) fails with this error. Every time.
- every episode will successfully record if I enter a manual schedule entry (one time or recurring, both work). Every time.

All of these are "classic" TV shows. Currently, they are all airing on 3 stations: METV, METV+, and Decades. However, one of them has occasionally aired on a PBS channel, and the same problem occurs there. I can record other shows on the same channel without issue.

The 8 shows are:
- 77 Sunset Strip
- The Many Loves of Dobie Gillis
- The Wild Wild West
- The Millionaire
- The Streets of San Francisco
- The Carol Burnett Show
- The Ed Sullivan Show
- The Lucy Show

I have mentioned this before (somewhere), but, occasionally, The Carol Burnett Show and The Ed Sullivan Show come down from SchedulesDirect without the leading "The", and those work OK. But I have also been successful recording newer shows with a leading "The" in the episode name on other channels (currently grabbing The Living and The Dead on a PBS channel). Note the first item: 77 Sunset Strip. I wonder if I might get failures on other items that lead off with a digit. I'll have to try that.

Also of interest: if I search for 77 Sunset Strip in the web interface, it returns nothing. I have to use Sunset Strip. Weird.

I will also note that I have had this failure on a few movie items over time - and, again, it would fail on each additional airing of that movie. The ones I still have in my Failed list are (there have been others):
- Fake: Searching for Truth in the Age of Misinformation
- What She Said: The Art of Pauline Kael (2018)
- Queen of Swing

But, of course, I have also had success on items with a ":" and other special characters.

Some time ago, I tried to look at how these titles are stored in the database to see if maybe there were some non-printable characters the data or something like that. I didn't find anything interesting, but I have no confidence that I was looking in all the right places. But my best less-than-completely-informed guess is that there is some anomaly in the data coming from the schedule source that's causing a problem.

I should add that I am running NextPVR on Ubuntu

[phu]

The error happens about once a week, on different channels and times. Here some more logs from this morning, just in case they are helpful. (It seems that I am still unabled to add more attachments... nevertheless I saved the logs)

[sub]

The error happens about once a week, on different channels and times. Here some more logs from this morning, just in case they are helpful. (It seems that I am still unabled to add more attachments... nevertheless I saved the logs)

Log files need to be zipped. It only accepts a .zip attachment. (and only up to 2MB)

[phu]

Thanks for the hint, logs attached now.