Recorder warns sqlite3 was not shutdown cleanly, despite controlled shutdown
See original GitHub issueThe problem
Recently, I often but not always get a warning that the Recorder’s default sqlite3 DB was not shutdown cleanly. This is despite performing a controlled shutdown via the UI on the Hardware settings page.
Currently running 2022.6.x and HAOS 8.1. This issue started within the past month or so. Hard for me to pinpoint if it’s correlated with HAOS 8.x or the Core version.
I have a feeling this issue will need to be moved to the HAOS repo, but the direct problem that is logged is from Recorder.
I have run HAOS in a VM for a few years (OVA image running within KVM on Proxmox). I always shut it down from within the HAOS guest via the UI.
I am sure there are more diagnostics I can help pull, I am not sure where to start.
Thank you teams!
2022-06-18 09:21:03 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
What version of Home Assistant Core has the issue?
core-2022.6.6
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant OS
Integration causing the issue
Recorder
Link to integration documentation on our website
https://www.home-assistant.io/integrations/recorder/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
Issue Analytics
- State:
- Created a year ago
- Reactions:5
- Comments:9 (1 by maintainers)
Thanks for the info @pvizeli! The issue remains in the 2022.7.x series and on HAOS 8.2.
In my experience it’s very consistent – IIRC anytime I’ve done a controlled shutdown via the UI, the sqlite warning shows up in the logs.
Same here (docker)
2023-01-02 10:40:07.272 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
but it always was a clean shutdown. Maybe sometimes the shutdown does not finish ongoing events? During my test I had this: