starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

code: 'SQLITE_CORRUPT' #916

New issue

Closed

opened 2026-02-28 02:03:34 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-28 02:03:34 -05:00

Owner

Originally created by @JGNi on GitHub (Mar 20, 2022).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

📝 Describe your problem

I have a similar problem as https://github.com/louislam/uptime-kuma/issues/51 but can't see the solution there. Or maybe I'm just not hardcore Docker man enough.
I get the following error:
errno: 11,
code: 'SQLITE_CORRUPT'
}
Start Uptime-Kuma failed due to issue patching the database
Patching the database failed!!! Restoring the backup

Whole error message can be seen here: https://pastebin.com/Zwmh6PBx

I've had uptime-kuma before, but deleted it again. Now I wanted to install it again, and got that error.

🐻 Uptime-Kuma Version

Last Update: Mar 18, 2022

💻 Operating System and Arch

unRAID, Docker

🌐 Browser

Chrome

🐋 Docker Version

20.10.5

🟩 NodeJS Version

No response

Originally created by @JGNi on GitHub (Mar 20, 2022). ### ⚠️ Please verify that this bug has NOT been raised before. - [X] I checked and didn't find similar issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### 📝 Describe your problem I have a similar problem as https://github.com/louislam/uptime-kuma/issues/51 but can't see the solution there. Or maybe I'm just not hardcore Docker man enough. I get the following error: errno: 11, code: 'SQLITE_CORRUPT' } Start Uptime-Kuma failed due to issue patching the database Patching the database failed!!! Restoring the backup ------------------------------------------------------------------------------------------- Whole error message can be seen here: https://pastebin.com/Zwmh6PBx I've had uptime-kuma before, but deleted it again. Now I wanted to install it again, and got that error. ### 🐻 Uptime-Kuma Version Last Update: Mar 18, 2022 ### 💻 Operating System and Arch unRAID, Docker ### 🌐 Browser Chrome ### 🐋 Docker Version 20.10.5 ### 🟩 NodeJS Version _No response_

deekerman

2026-02-28 02:03:34 -05:00

closed this issue
added the
help
label

deekerman commented

2026-02-28 02:03:41 -05:00

Author

Owner

@rezzorix commented on GitHub (Mar 21, 2022):

How do you start your docker container?
Can you post the docker cli or yml file here?

@rezzorix commented on GitHub (Mar 21, 2022): How do you start your docker container? Can you post the docker cli or yml file here?

deekerman commented

2026-02-28 02:03:42 -05:00

Author

Owner

@weirlive commented on GitHub (Mar 21, 2022):

are you using NFS for your volume mount?

@weirlive commented on GitHub (Mar 21, 2022): are you using NFS for your volume mount?

deekerman commented

2026-02-28 02:03:42 -05:00

Author

Owner

@JGNi commented on GitHub (Mar 21, 2022):

I would like to, but how do that in unRAID?
Or can I start it, or see it in the CLI??

@JGNi commented on GitHub (Mar 21, 2022): > I would like to, but how do that in unRAID? Or can I start it, or see it in the CLI??

deekerman commented

2026-02-28 02:03:42 -05:00

Author

Owner

@JGNi commented on GitHub (Mar 21, 2022):

are you using NFS for your volume mount?

Maybe. I'm still a little new into this. Do you know how I see it?

@JGNi commented on GitHub (Mar 21, 2022): > are you using NFS for your volume mount? Maybe. I'm still a little new into this. Do you know how I see it?

deekerman commented

2026-02-28 02:03:42 -05:00

Author

Owner

@weirlive commented on GitHub (Mar 21, 2022):

well you would know based on your docker-compose file where your volume mount is pointing. using NFS for a database is usually a bad idea and will lead to corruption.

(i'm open to someone correcting me as this is just what i've read to not use NFS for DBs)

@weirlive commented on GitHub (Mar 21, 2022): well you would know based on your docker-compose file where your volume mount is pointing. using NFS for a database is usually a bad idea and will lead to corruption. (i'm open to someone correcting me as this is just what i've read to not use NFS for DBs)

deekerman commented

2026-02-28 02:03:42 -05:00

Author

Owner

@JGNi commented on GitHub (Mar 21, 2022):

you would know based on your docker-compose file where your volume mount is pointing

In unRAID it's all GUI. But I can open a CLI. Just don't know much to look for there....

@JGNi commented on GitHub (Mar 21, 2022): > you would know based on your docker-compose file where your volume mount is pointing In unRAID it's all GUI. But I can open a CLI. Just don't know much to look for there....

deekerman commented

2026-02-28 02:03:42 -05:00

Author

Owner

@JGNi commented on GitHub (Mar 21, 2022):

I deleted the user folder and integration. Installed again, and it worked.

@JGNi commented on GitHub (Mar 21, 2022): I deleted the user folder and integration. Installed again, and it worked.

deekerman referenced this issue

2026-02-28 02:15:37 -05:00

Subscribe to Status Page updates. #1265

deekerman referenced this issue

2026-02-28 02:17:36 -05:00