[Support]: Too many SQL variables #22829
Replies: 4 comments 2 replies
-
|
I see this was also raised 4 years ago here: #3014 |
Beta Was this translation helpful? Give feedback.
-
|
The linked issue is different than yours. This is a generic SQL error that usually isn't hit unless there is a configuration or setup issue. Did you recently upgrade Frigate? What is your full config? What is your Docker compose? |
Beta Was this translation helpful? Give feedback.
-
|
I didn't recently upgrade, however I did recently move a camera to 0 days retention which has probably kicked off a bunch of deletes. Compose: Frigate configuration attached. |
Beta Was this translation helpful? Give feedback.
-
|
In case it helps, what I also did recently which may have caused this is I removed a camera in the config by commenting it out, restarting, then commenting it back in, and restarting again. If I remove the same camera from the config a second time (again, commenting out), Frigate will start normally. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the extra detail, that confirms what happened. When you commented out the camera, Frigate deleted its region grid entry. When you added it back, it tried to rebuild the grid from the entire event history for that camera, which must have tens of thousands of events for it to exceed SQLite's variable limit. As a workaround, you can run this from inside the container to skip the backfill: If the row doesn't exist yet, comment the camera back out, start Frigate, then stop it and run: Then comment the camera back in and restart. The next version of Frigate has better handling for disabling/deleting cameras from the config, but this generally shouldn't be an issue unless you have a large number of tracked objects for each camera, as seemingly is your case. We could probably handle this better with batching, but yours is an isolated case, and it won't fix your immediate issue. |
Beta Was this translation helpful? Give feedback.
-
|
While changes in the next version of Frigate should already mitigate this issue in the future, I made additional improvements in this PR: #22828 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Checklist
Describe the problem you are having
Getting this error on restarting Frigate 0.17.1-416a9b7.
Steps to reproduce
Version
0.17.1-416a9b7
In which browser(s) are you experiencing the issue with?
Edge
Frigate config file
N/Adocker-compose file or Docker CLI command
N/ARelevant Frigate log output
Relevant go2rtc log output
Operating system
Proxmox
Install method
Docker Compose
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
No response
Beta Was this translation helpful? Give feedback.
All reactions