[Camera Support]: Video will not play after switching to history - Nginx shows "invalid number of elements..." #14706
-
Checklist
Describe the problem you are havingSwitching from a live camera feed to the history does not playback video once a previous recorded time is selected. Steps to reproduceClear steps to reproduce are not available beyond the steps outlined in the section above VersionFrigate 0.14.1-f4f3cfa In which browser(s) are you experiencing the issue with?No response Frigate config filemqtt:
enabled: false
birdseye:
enabled: true
mode: continuous
go2rtc:
streams:
trackmix_wide:
- rtsp://XXXX:[email protected]:554/h264Preview_01_main
trackmix_zoom:
- rtsp://XXXX:[email protected]:554/h264Preview_02_main
doorbell:
- rtsp://xxxxxxx:[email protected]:554/cam/realmonitor?channel=1&subtype=0
cameras:
doorbell:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/doorbell
input_args: preset-rtsp-restream
roles:
- detect
detect:
enabled: true # <---- disable detection until you have a working camera feed
width: 1280
height: 720
zones:
nearDoor:
coordinates: 0.723,0.489,1,0.459,1,1,0.703,1
loitering_time: 0
inertia: 3
review:
alerts:
required_zones: nearDoor
motion:
threshold: 48
contour_area: 10
improve_contrast: 'true'
trackmix_wide:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/trackmix_wide
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://XXXXX:[email protected]:554/h264Preview_01_sub # was sub <----- The stream you want to use for detection
roles:
- detect
detect:
enabled: true # <---- disable detection until you have a working camera feed
width: 896
height: 512
onvif:
host: 192.168.178.167
port: 8000
user: admin
password: admin555
trackmix_zoom:
enabled: true
ffmpeg:
inputs:
- path: rtsp://127.0.0.1:8554/trackmix_zoom
input_args: preset-rtsp-restream
roles:
- record
- path: rtsp://XXX:[email protected]:554/h264Preview_02_sub # was sub <----- The stream you want to use for detection
roles:
- detect
detect:
enabled: true # <---- disable detection until you have a working camera feed
width: 896
height: 512
onvif:
host: 192.168.178.167
port: 8000
user: XXX
password: XXX
zones:
fensterseite:
coordinates: 0.52,0.998,0.535,0.039,0,0.036,0.007,0.991
loitering_time: 0
inertia: 3
review:
alerts: {}
version: 0.14
detectors:
coral:
type: edgetpu
device: usb
record:
enabled: True
retain:
days: 3
mode: all
events:
retain:
default: 30
mode: motion
# Optional
ui:
# Optional: Set a timezone to use in the UI (default: use browser local time)
# timezone: America/Denver
# Optional: Set the time format used.
# Options are browser, 12hour, or 24hour (default: shown below)
time_format: 24hour
logger:
logs:
frigate.record.maintainer: debug
camera_groups:
birdseye:
order: 1
icon: LuTarget
cameras: birdseyedocker-compose file or Docker CLI commandversion: "3.9"
services:
frigate:
container_name: frigate
privileged: true # this may not be necessary for all setups
restart: unless-stopped
image: ghcr.io/blakeblackshear/frigate:stable
shm_size: "512mb" # update for your cameras based on calculation above
devices:
- /dev/bus/usb/003/003:/dev/bus/usb # Passes the USB Coral, needs to be modified for other versions
volumes:
- /etc/localtime:/etc/localtime:ro
- /mnt/nfsSharePool/frigate/config:/config
- /mnt/nfsSharePool/frigate/storage:/media/frigate
- type: tmpfs # Optional: 1GB of memory, reduces SSD/SD Card wear
target: /tmp/cache
tmpfs:
size: 2G
ports:
- "8971:8971"
# - "5000:5000" # Internal unauthenticated access. Expose carefully.
- "8554:8554" # RTSP feeds
- "8555:8555/tcp" # WebRTC over tcp
- "8555:8555/udp" # WebRTC over udp
environment:
FRIGATE_RTSP_PASSWORD: "password"Relevant Frigate log outputType
info
Timestamp
2024-10-31 15:25:24
Tag
GET
Message
2024/10/31 15:25:24 [error] 165#165: *5839 media_set_parse_durations: invalid number of elements in the durations array 2863 while sending to client, client: 192.168.178.194, server: , request: "GET /vod/trackmix_wide/start/1730383200/end/1730386800/master.m3u8 HTTP/1.1", host: "192.168.178.174:8971", referrer: "https://192.168.178.174:8971/review"Relevant go2rtc log output2024-10-31 12:40:09.851004679 [INFO] Preparing new go2rtc config...
2024-10-31 12:40:10.141172086 [INFO] Starting go2rtc...
2024-10-31 12:40:10.249263127 12:40:10.249 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-10-31 12:40:10.249267115 12:40:10.249 INF config path=/dev/shm/go2rtc.yaml
2024-10-31 12:40:10.249583113 12:40:10.249 INF [rtsp] listen addr=:8554
2024-10-31 12:40:10.249675687 12:40:10.249 INF [webrtc] listen addr=:8555/tcp
2024-10-31 12:40:10.249789723 12:40:10.249 INF [api] listen addr=:1984
2024-10-31 12:40:19.850001847 [INFO] Starting go2rtc healthcheck service...
2024-10-31 13:34:34.601357219 13:34:34.598 INF [streams] can't add track error="wrong response on DESCRIBE"
2024-10-31 13:34:34.602830243 13:34:34.601 WRN github.com/AlexxIT/go2rtc/internal/streams/producer.go:171 > error="start from CONN state" url=rtsp://admin:[email protected]:554/cam/realmonitor?channel=1&subtype=0Operating systemOther Install methodDocker Compose Network connectionWired Camera make and modelRealink Trackmix, Dahua Doorbell Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpfulNo response |
Beta Was this translation helpful? Give feedback.
Answered by
hawkeye217
Oct 31, 2024
Replies: 1 comment 4 replies
-
How long ago did you change the mode compared to the time you're trying to view in History? In other words, did you switch the mode 5 minutes ago and now you're trying to look at History from 10 minutes ago? |
Beta Was this translation helpful? Give feedback.
4 replies
-
|
Its not the case that the time of recording requested via the history UI slider is before the time i switched recording [mode to "all the time".](mode: all) But the distance to the point in time i switched that setting seems to have an effect indeed. From the time of switching the recording mode at least 9 hours have passed now. Requesting a recording from about 2h ago works as expected. Details: Change time on config.yaml is shown as The earliest time i can successfully request is around the 16:00 mark. Requesting the video for approximate 15:55 yields again this error in the nginx logs and no video playback.
Iam not sure if that is conclusive but the amount of files in the recording directory makes me believe the 15:XX timeframe should be available in the history and should have been recorded. |
Beta Was this translation helpful? Give feedback.
-
|
NGINX has a max limit on the number of segments that can be requested in a single playlist. The only other time I've seen this is when a camera is sending corrupt data and the PTS / DTS timestamps are incorrect, which results in more segments being than configured (which should be every 10 seconds). If you look at some of your segment times at the beginning of the hour, it looks like a new segment is being generated every second: But later in the hour, they are 10 seconds apart: This would almost certainly indicate the problem is with the camera. Since you're using go2rtc, I'd suggest trying the go2rtc |
Beta Was this translation helpful? Give feedback.
Answer selected by
pr10dr
-
|
Excellent detective work! Your point seems very valid. I will implement the changes you suggested and only report back if the error scenario remains. Thank you! I would consider this request to be adressed (Please close as you see fit) |
Beta Was this translation helpful? Give feedback.
-
|
Happy to help! I'll close this, but feel free to reopen if you are still experiencing the issue. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
NGINX has a max limit on the number of segments that can be requested in a single playlist.
The only other time I've seen this is when a camera is sending corrupt data and the PTS / DTS timestamps are incorrect, which results in more segments being than configured (which should be every 10 seconds).
If you look at some of your segment times at the beginning of the hour, it looks like a new segment is being generated every second: