Upgrading from v13 to v14 and issues with Recordings #15523
Replies: 4 comments 11 replies
-
We need to see the beginning of the error in the logs, this will be the problem |
Beta Was this translation helpful? Give feedback.
-
In addition to the error logs @NickM-27 requested, there are many optimizations you can/should make for your 0.14 setup, much has changed since 0.13. In no particular order:
|
Beta Was this translation helpful? Give feedback.
-
Thank you for the quick and accurate help, things have been running for an hour now and seem to be working perfectly after updating the SHM size. Since the documentation indicated my old values were more than sufficient, I'm not sure how to calculate what it should be, but as mentioned, V15 should require new calculations and have updated documentation. |
Beta Was this translation helpful? Give feedback.
-
So the tmp/cache stopped updating again. I've raised my SHM to 2048 MB now, but it still doesn't seem to want to work. The recordings folder for the recent run/hour has only 1 of 3 cameras in it. The log shows cleanup of the tmp/cache folder from the previous run, and a single copy but not much else, and then some messages about onvif, but I'm not trying to use ONVIF or PTZ functionality
The go2rtc log is small but does have a warning about an empty URL
I'm switching back to v13 for now, might be able to take a look at any suggestions during the week. Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
I have been trying off and on for a few months to upgrade from v13 to v14 in Docker. I have parallel containers (one for each environment), and directories on my Synology NAS.
While v13 seems to continue to work without issue, I am having problems (particularly with storing recordings) with v14.
I have use the config.yaml from v13 and let the upgrade process convert it, but started with empty db/media, etc. I modified the v14 config.yaml and it seems to have no issues. I was getting recordings in v14 sporadically for a bit but they have completely stopped now.
The following is what I see happening with v14:
I realize that the Troubleshooting page mentions high CPU may be an issue for recordings, but the same CPU usage is being seen with v13. In addition, v14 seems to be using my TPU where v13 does not.
I commented out the "detect" roles to see if this made a difference and noted the following:
I'm not sure where to go from here, everything seems to work fine (occasional hiccups with losing my doorbell camera) on v13, but I can't seem to get this migration to v14 to work out.
Version
0.14.1-f4f3cfa
What browser(s) are you using?
Google Chrome 131.0.6778.140
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
2024-12-15 21:43:04.054978994 [INFO] Preparing new go2rtc config... 2024-12-15 21:43:04.552825270 [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually 2024-12-15 21:43:04.642439297 [INFO] Starting go2rtc... 2024-12-15 21:43:04.864344277 21:43:04.864 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2024-12-15 21:43:04.864392783 21:43:04.864 INF config path=/dev/shm/go2rtc.yaml 2024-12-15 21:43:04.864916139 21:43:04.864 INF [api] listen addr=:1984 2024-12-15 21:43:04.865002630 21:43:04.864 INF [rtsp] listen addr=:8554 2024-12-15 21:43:04.865373639 21:43:04.865 INF [webrtc] listen addr=:8555 2024-12-15 21:43:14.040483912 [INFO] Starting go2rtc healthcheck service...
FFprobe output from your camera
Frigate stats
Install method
Docker CLI
docker-compose file or Docker CLI command
No longer have this, use Portainer to copy from previous existing container.
Object Detector
Coral
Network connection
Mixed
Camera make and model
EZVIZ (x2), HeimVision
Screenshots of the Frigate UI's System metrics pages
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions