Always stops working after some time (2)

[calande]

Hello,

I was reading the forum messages, and it seems I have the same problem as this user. I scheduled weekly recordings that are supposed to last 2h, but they actually last no more than 5 minutes. I always end up throwing them away, I only have the commercials at the beginning of the TV program, the TV program itself doesn't even begin when the recording is aborted. Here is the section of the log file that I think is relevant, although I don't understand much. From my understanding the NAS receives 200MB of data every ten seconds? This is huge... How is it possible, to begin with? (it's a simple 1080i h.264 TV stream...). 

Code:

2024-10-13 21:14:15.314 [DEBUG][144] Have received 198136960 bytes from rtp source
2024-10-13 21:14:25.414 [DEBUG][144] Have received 198136960 bytes from rtp source
2024-10-13 21:14:35.514 [DEBUG][144] Have received 198136960 bytes from rtp source
2024-10-13 21:14:45.614 [DEBUG][144] Have received 198136960 bytes from rtp source
2024-10-13 21:14:55.714 [DEBUG][144] Have received 198136960 bytes from rtp source
2024-10-13 21:15:00.125 [DEBUG][11] Stopping recording (902 on 21). Past end time of recording. 257
2024-10-13 21:15:00.493 [DEBUG][11] StopStream(257)
2024-10-13 21:15:00.493 [DEBUG][11] StopStream handle: 257
2024-10-13 21:15:00.512 [DEBUG][11] Closing TSWriter....: /recordings/Manual Recordings/FELA_20241013_19102110.ts
2024-10-13 21:15:00.523 [ERROR][11] writer.Close() did not complete in a timely fashion
2024-10-13 21:15:00.523 [DEBUG][11] Close@2
2024-10-13 21:15:00.523 [DEBUG][11] Closing mapAccessor
2024-10-13 21:15:00.576 [DEBUG][11] Closing mapMMF
2024-10-13 21:15:00.576 [DEBUG][11] Closing mapFileStream
2024-10-13 21:15:00.577 [DEBUG][11] deleting /recordings/Manual Recordings/ABC_20241013_19102110.ts.map
2024-10-13 21:15:00.591 [DEBUG][94] Reached end of in-progress recording. Dropping connection.
2024-10-13 21:15:00.595 [DEBUG][11] Close@exit
2024-10-13 21:15:00.596 [DEBUG][11] StopStream@exit
2024-10-13 21:15:00.611 [DEBUG][94] Sent total of 198133200 bytes
2024-10-13 21:15:00.764 [DEBUG][144] Shutting down RTP input stream
2024-10-13 21:15:00.764 [DEBUG][11] stopping legacy hdhr stream
2024-10-13 21:15:01.922 [DEBUG][11] stopping graph
2024-10-13 21:15:01.922 [DEBUG][11] destroying graph
2024-10-13 21:15:01.922 [INFO][11] Stopped
2024-10-13 21:15:02.237 [DEBUG][11] StoreMetaData@exit
2024-10-13 21:15:03.740 [DEBUG][11] PowerManagement AllowSleep (needs implementation)
2024-10-13 21:15:03.740 [DEBUG][11] No longer active
2024-10-13 21:15:04.403 [DEBUG][135] timing closed

More info: I'm using v.6.1.5.231022, in a Docker image, on a QNAP TS-131P NAS (arm32). I have plenty of free space on this NAS.
I have restarted Docker several times, with no improvements.
I am able to record from my computer using the same Ethernet DVB-T tuner for hours trouble-free using DVBViewer (a separate Windows application).
Do you know what may be aborting my recordings?
Thank you!

Note: I'm getting an error message on the forum reporting too many MySQL connections.

[mvallevand]

Could you please download and attach the zipped from from the main NextPVR web page so we can see if it is the same issue.

Also you could try the Windows version of NextPVR on the DVBViewer machine to see if it is a Docker configuration issue.

Others, including myself have noticed that connection issue in the morning GMT.

Martin

[calande]

As it turns out, I also have NextPVR installed on my Windows 11 PC, so that's great, I just tried scheduling an immediate recording on my PC as well, using NextPVR... It says it's recording, but on the front panel of my DVB-T tuner, the LED is off, meaning the tuner is idle and no network device is polling it. That's strange! Also, the .ts file is 0 byte in my directory...
Anyway, here are the two log files attached (one for the Docker image, and the other one for the Windows install).
Thank you!

[mvallevand]

From the logs it look more like the recording froze 198136960 bytes (the logs confirmed that it is a cumulative number of bytes)

2024-10-13 19:11:41.584 [DEBUG][144] Have received 194016564 bytes from rtp source
2024-10-13 19:11:52.548 [DEBUG][144] Have received 198136960 bytes from rtp source

Are you sure you don't have a quota on your recording folder? There is more than enough free space.

For the Windows issue, could you try after restarting the service without an EPG update? To tell you the truth I didn't even the DVB-T tuner had a a legacy version so sub the author of NextPVR would probably need to report on that. However since it worked in Sept, maybe you need to do a rescan?

Martin

[calande]

I scheduled an immediate recording on my Window computer from the NextPVR browser interface at localhost. It started recording shortly after. I had disabled EPG update right before, in the settings. I watched after the recordings directory: the .ts file didn't stop growing, and the LED on the front panel of my tuner was on , so that was good. The recording was set to stop 2h later, which it did. I checked the properties of the .ts file : it's 120 minute long, it's properly recorded. Everything went fine.

Regarding the Docker image, I checked on my NAS, there's no quota on my recording folder... I wonder what may cause this sudden stop recording ?

[calande]

Disabling EPG indeed solved the problem on my NAS with Docker on arm32. I tried again scheduling a 2h recording, which NextPVR recorded successfully, entirely, now that EPG is unchecked.