[Support]: eewee OperationalError: no such column: t1.has_been_reviewed #19725
Replies: 3 comments 1 reply
-
|
The error "peewee.OperationalError: no such column: t1.has_been_reviewed" indicates that your Frigate database schema is missing the column has_been_reviewed, which is required for the review feature to work(1)(2)(3). The ReviewSegmentResponse schema expects this column to exist in the database(2)(3). This usually happens if the database was created with an older Frigate version and hasn't been migrated, or if a new database was not initialized after upgrading. To resolve this:
This will resolve the schema mismatch, but you will lose all existing review data in the old database. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
This was done when I upgrade to 0.16.0-rc2, and everything was working until today when I noticed cameras were offline and review was hanging. |
Beta Was this translation helpful? Give feedback.
-
|
If you already recreated the database during your upgrade and things worked for a while before the cameras went offline and review started hanging, this points to a possible corruption or malfunction of the new database file—not just a schema mismatch. Database corruption can happen due to unclean shutdowns, hardware/storage issues, or running out of disk space. The Frigate FAQ explicitly notes that SQLite does not work well on a network share and recommends using a local/internal drive for the database if you see locking or corruption errors(1). Similar symptoms have also been reported if the database becomes malformed after a hard shutdown, and users have been able to recover by running SQLite integrity checks and reindexing, or by recreating the database again(2). To troubleshoot:
If the problem recurs after a new database is created, monitor for hardware or storage issues, and avoid abrupt shutdowns. Check out these potentially useful sources: Frequently Asked Questions, peewee.DatabaseError: malformed database schema (Livingroom)[Support]:, Migrate database and config from Home Assistant /config to addon's /config Would you like a general answer based on my knowledge instead? 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
I figured out what happened, I updated to the stable tag which image was not updated yet so I essentially reverted to 0.15.2 from 0.16.0-rc4. Thanks. |
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.
-
Checklist
Describe the problem you are having
errors in the logs below high cpu and cameras stopping working.
Steps to reproduce
...
Version
0.16.0
In which browser(s) are you experiencing the issue with?
Mozilla/5.0 (X11; Linux x86_64; rv:141.0) Gecko/20100101 Firefox/141.0
Frigate config file
docker-compose file or Docker CLI command
Relevant Frigate log output
Relevant go2rtc log output
Operating system
Other Linux
Install method
Docker CLI
Network connection
Wired
Camera make and model
dahua various
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