"The response ended prematurely"

[nappysolo]

I just tried recording a program with a longer name, containing a colon and an apostrophe, and it worked, so it's not as simple as any of those.

[nappysolo]

I just had this problem occur again (logs attached).

Some background:
I record the same program every Sunday at 22:00. Normally, the series is named "Ed Sullivan" and has been working fine for months. Last Sunday night, it appeared as "The Ed Sullivan Show" and failed (did not find out until the next morning). This week it also had the name "The Ed Sullivan Show", so I was monitoring it when it kicked off and, indeed, it failed again. It created the folder, but did not create any files. I quickly created a manual recording so I wouldn't miss the episode, and that worked. According to the EPG data, next week it goes back to "Ed Sullivan", so it will be interesting to see if the error goes away as well.

[phu]

Hello there,
I receive the same error message when recording some films on my Raspberry Pi 4 with Hauppauge 461e. I can record other stuff on the same channel where the error happened, so the channel does not seem to be the problem. I can neither record scheduled nor when currently running. At first I thought it has something to do with german umlauts (öäü) in the title or description, but it has not, i can verif, that other films with umlauts worked fine.

[mvallevand]

It does seem to be a multi-rec issue that sub will need to look into. Are you ever able to record multiple channels from the same mux?

Martin

[phu]

I don't think that multi-rec is the problem, that worked today on multiple other films. Also I was not recording multiple stuff during the failure. The ones that didn't work (shown in the logs) also already failed a few days ago, also without multi-rec.
Am I able to debug this issue a bit more? I'd like to help as much as I can.

[mvallevand]

For debugging sub the author is going to need to reply. You were definitely using multi-rec

2022-04-17 05:09:55.016 [DEBUG][8] About to start recording (903 on 21): /media/usb/recordings/Jagd auf einen Unsichtbaren/Jagd auf einen Unsichtbaren_20220417_05100658.ts...
2022-04-17 06:57:26.046 [DEBUG][8] About to start recording (898 on 21): /media/usb/recordings/Die nackte Kanone/Die nackte Kanone_20220417_06580841.ts...

Not only did 898 not start, 903 didn't close properly.

I confused by the recording start times too. Before the tuner is even opened, I see your RPi is very slow to start the recording process. I am not talking a second or two, I am talking roughly 30 seconds or more. Occasionally it is ok. Is you server used for other things?

Martin

[phu]

Thanks for your reply. Okay sorry, I missed that, but actually at the very end of the logs there should (thats what I intended to at least?!) be a manual recording failure of the same kind without multi-rec. I am currently not using the rpi for other stuff, it's actually a newly installed raspberry pi os. Also, I watched the last few minutes of 903 and indeed its coruppt at the end. Maybe due to the failure of 898 that effected 903 in some way?

[mvallevand]

Yes any recording after 903 is going to fail, the tuner service hung. It could also be a driver issue, did you check dmesg and journalctl?

Martin

[phu]

I didn't check dmesg, i will next time. From a short overview journalctl does not provide any valuable information. I'll have a deeper look into it tomorrow.

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.

[nappysolo]

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.