[Support]: Cant watch recordings, alerts, detections: server returns 503 and track count mismatch, first clip had 0 current clip has 1 media type 1 while sending to client
#19137
Replies: 15 comments 57 replies
-
Beta Was this translation helpful? Give feedback.
-
go2rtc:
streams:
corridor_camera:
- rtsp://192.168.31.25:554/stream1
- ffmpeg:corridor_camera#video=copy#audio=aac
...
cameras:
corridor_camera:
ffmpeg:
inputs:
- path: rtsp://192.168.31.25/stream1
roles:
- detect
output_args:
record: preset-record-generic-audio-aac |
Beta Was this translation helpful? Give feedback.
-
I've started getting these errors too with a camera that I just added. Other cameras work just fine. I checked a few segments between those timestamps and they all seem fine, all have video and audio. Also running Frigate (0.16.0-d96efdb)
|
Beta Was this translation helpful? Give feedback.
-
Ok, so adding the forced re-encoding didnt work, I just ran into this error again, but I think I may have a data point. When an event (alert/detection) is still recording and you go to view that event while its recording is when it seems to happen. Im 90% sure thats what happened last time as well because I went to watch the footage right after getting the alert as I was away from home at the time. All the other times I've viewed events is after they are done being an active event and everything is written to disk. Also, this camera is set to record all for 3 days (IDK if that's relevant). Edit: Is the playback library the one throwing the errors? or is this backend code from frigate? is there a way to just watch the video track without audio? force it or something? |
Beta Was this translation helpful? Give feedback.
-
All my segments had audio & video too. Somehow the issue magically fixed itself after a few days, but I'm doing 24/7 recording on all cameras so maybe that helped too? |
Beta Was this translation helpful? Give feedback.
-
Can someone here please get a screenshot of the network tab when this issue happens |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Glad to see it's not just me having these issues. Mine is on a brand new install, running it in a docker container. |
Beta Was this translation helpful? Give feedback.
-
Same thing here with Tapo cameras so it's not restricted to Reolink. Only started after upgrading to 0.16 |
Beta Was this translation helpful? Give feedback.
-
Same here on 0.16. BUT... It pretty reliably hangs when I am using Firefox or Chromium on linux. Howver it always seems to work using Safari on an iPhone. I can even be looking at the same piece of history simultaneously on the desktop and the iphone, but with it only working on the iphone. FWIW My go2rtc streams are all of the form
as the cameras can't output aac. |
Beta Was this translation helpful? Give feedback.
-
Just upgraded to 0.16.1 - problem fixed. |
Beta Was this translation helpful? Give feedback.
-
I'm also facing this issue:
Checked my database: ![]() The segments are in the database, and exist on disk. When I use 1758568055 instead of 1758568056 as start, everything works fine. @NickM-27 do you want me do something special to help debug this issue? |
Beta Was this translation helpful? Give feedback.
-
Is the commonality between all these cases Tapo and Reolink cameras? |
Beta Was this translation helpful? Give feedback.
-
I thought the updated fixed my issues, but this is now becoming a bigger issue on my instance. Only happening on my Reolink camera. Can't even export. It's ironic, Frigate always seems to be an issue when I need it most or when something actually happens outside I need to clip
@baudneo can you reopen this? |
Beta Was this translation helpful? Give feedback.
-
Is there any update on this issue? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
So this is very weird. This just happened but I cant figure it out. I have retain set to 2 days
all
for this camera alongside alerts snapshots and detections. So, I am trying to review an incident of homeless coming and doing damage and I can't view the alert or the timeline from 11pm to current.I can view anything before 11PM, if I set the timeline history view to 10:59:30 and let it run, it freezes at 10:59:59. No errors, no warning, no nothing. I've rebooted, I've restarted frigate from UI, I've done a
docker compose up -d --force-recreate
all with the same result.Haven't seen this before. Of course, it happens for the exact time period I need to review. Will try the recording in VLC and hopefully its not corrupt or whatever.
Its the
alley
camera.Any ideas?
Version
0.16.0-ea576e7
What browser(s) are you using?
Brave 1.79.123 (Official Build) (64-bit) Chromium: 137.0.7151.104
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
Install method
docker
docker-compose file or Docker CLI command
Object Detector
TensorRT
Network connection
Wired
Camera make and model
N/A
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
Search revealed a cpl thing sbut didnt seem related (other issues were after upgrades). Mine happened while running.
Beta Was this translation helpful? Give feedback.
All reactions