Custom M3U/RTSP Issues After Installing Beta

I have having an issue with a TVE channel an upgraded to the latest beta from the the latest stable. It fixed my TVE issue but now I have a new one. I use a custom channel / M3U to pull in my Unfi security cameras. This was working before the upgrade but after the channels app displays a 503 error and the log has the message below. I have confirmed the stream(s) for the cameras still work in other apps so I can only assume a change in the beta is the cause of the issue here.

Diagnostic: 73fc2dac-1c4f-456b-b399-3b387a4cbe21

2022/11/22 15:43:54.351042 [ERR] Failed to start stream for ch1000: runtime error: invalid memory address or nil pointer dereference
2022/11/22 15:43:54.414374 [HLS] Couldn't generate stream playlist for ch1000-dANY-ip192.168.130.114: runtime error: invalid memory address or nil pointer dereference
1 Like

Same error here.

Likewise.

same here:

2022/11/22 23:38:31.262931 [ERR] Could not start stream for M3U-SecurityCameras ch0.5 All Cameras: runtime error: invalid memory address or nil pointer dereference
2022/11/22 23:38:50.033536 [ERR] Could not start stream for M3U-SecurityCameras ch0.2 Driveway View: runtime error: invalid memory address or nil pointer dereference

submitted diagnostics as well

1 Like

@tmm1 could you take a look at this? It is broken after a server update a while back. I just submitted diagnostics after the error occurred.

Yup been broken for last few updates. I originally thought it had something to do with linux stuff I was testing but then my nas stopped working.

Is it rtsp only?

@tmm1 rtsp is the only thing that I am running that has this issue. All other custom channels are fine

I submitted diagnostics for this issue yesterday. My security cameras are rtsp. (Edited)

This has been fixed. The issue started around 11/19

1 Like

@tmm1 It doesn't work if you view from the web console or use hls streaming on a client. In those cases it throws errors in the logs. I submitted diagnostics from the client just now and from the server
4dd03609-c536-46d1-8327-750f38049418. If I turn off hls then it works ok.

2022/11/30 19:56:04.863568 [TNR] Opened connection to M3U-SecurityCameras for ch0.5 All Cameras
2022/11/30 19:56:04.865736 [HLS] Starting live stream for channel 0.5 from 172.16.1.11
2022/11/30 19:56:05.006345 [HLS] ffmpeg: rtsp-MultiCameraView:  [rtsp @ 0x7e81600] method SETUP failed: 461 Unsupported transport
2022/11/30 19:56:05.365936 [HLS] Stopping transcoder session ch0.5-dANY-ip172.16.1.11
2022/11/30 19:56:05.366078 [ERR] Probe failed for live stream after 500.103186ms and 0 bytes
2022/11/30 19:56:05.366144 [ERR] Error during stream M3U-SecurityCameras ch0.5 All Cameras: read |0: file already closed
2022/11/30 19:56:05.366164 [TNR] Closed connection to M3U-SecurityCameras for ch0.5 All Cameras
2022/11/30 19:56:05.370240 [HLS] Couldn't generate stream playlist for ch0.5-dANY-ip172.16.1.11: Stream stopped
2022/11/30 19:56:07.066297 [HLS] ffmpeg: rtsp-MultiCameraView:  [mpegts @ 0x7ea4ac0] Non-monotonous DTS in output stream 0:0; previous: 26581, current: 0; changing to 26582. This may result in incorrect timestamps in the output file.
2022/11/30 19:56:07.066314 [HLS] ffmpeg: rtsp-MultiCameraView:  [mpegts @ 0x7ea4ac0] Non-monotonous DTS in output stream 0:0; previous: 26582, current: 1621; changing to 26583. This may result in incorrect timestamps in the output file.
2022/11/30 19:56:07.066316 [HLS] ffmpeg: rtsp-MultiCameraView:  [mpegts @ 0x7ea4ac0] Non-monotonous DTS in output stream 0:0; previous: 26583, current: 7741; changing to 26584. This may result in incorrect timestamps in the output file.
2022/11/30 19:56:07.066319 [HLS] ffmpeg: rtsp-MultiCameraView:  [mpegts @ 0x7ea4ac0] Non-monotonous DTS in output stream 0:0; previous: 26584, current: 15481; changing to 26585. This may result in incorrect timestamps in the output file.
2022/11/30 19:56:07.066322 [HLS] ffmpeg: rtsp-MultiCameraView:  av_interleaved_write_frame(): Broken pipe
2022/11/30 19:56:07.066408 [HLS] ffmpeg: rtsp-MultiCameraView:  Error writing trailer of pipe:: Broken pipe

This topic was automatically closed 365 days after the last reply. New replies are no longer allowed.