New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Sqlite errors #4709
Comments
As an explainaition what this error means from the docs:
A person on reddit reddit suggested the following. Could you try and report the results?
|
Please also see #4110 if you have the same problem |
Thank you @CommanderStorm I read your links and not sure that they apply to my case. This is the actual content of the folder
The VM is deployed in the corporate private cloud (based on VMware). |
Can you try going into Settings -> Monitor History -> press "Shrink Database"? |
@chakflying So far the monitoring history is set to 0 (I need at least 1 year of data, hoping that in the future the Kuma UI will have a feature to select the time history for the whole year). |
Yes, no data would be deleted, it only runs a command to compact and organize the database file. In general, most people who have reported database errors have had to reduce the retention time to eliminate the errors. I think we currently don't have the expertise to optimize our current usage of SQLite further, so there is no solution for now. If running "Shrink Database" doesn't solve your issue, I think you can wait for external database support in 2.0, and in the meantime consider reducing the retention time after doing whatever backups necessary. |
@chakflying I will try and let you know |
(we track the steps neasesary before a V2.0 release in #4500) @chakflying I don't know if this is related as none of the other cases with this boiled down to this. At the current moment, I suspect a similar problem as in #4110 => a broken disk |
🛡️ Security Policy
📝 Describe your problem
I am having troubles with sqlite, sometimes I see timeouts errors like this one:
I've deployed the software as a docker container with podman in a Virtual machine based on RHEL8 and mounted a volume to a local directory
The only way to resolve those errors is to restart the container.
I have ~30/40 monitors and the max nested depth (they are grouped with Groups) is 4
Can you please help me stabilize the environemnt?
📝 Error Message(s) or Log
🐻 Uptime-Kuma Version
1.23.11-alpine
💻 Operating System and Arch
RHEL8 with podman
🌐 Browser
Edge
🖥️ Deployment Environment
The text was updated successfully, but these errors were encountered: