starred/uptime-kuma

Fork 0

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

DB migration fails on 2026-01-10-0000-convert-float-precision.js #4704

New issue

Closed

opened 2026-02-28 04:12:21 -05:00 by deekerman · 7 comments

deekerman commented

2026-02-28 04:12:21 -05:00

Owner

Originally created by @ChekeredList71 on GitHub (Feb 12, 2026).

⚠️ Please verify that your question has not already been reported

I have searched the existing issues and found no similar reports.

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Describe your problem

After changing tags from louislam/uptime-kuma:latest -> louislam/uptime-kuma:2.1.0, Uptime Kuma no longer starts.

DB integrity is ok:

$ sqlite3 kuma.db "PRAGMA integrity_check;"
ok

📝 Error Message(s) or Log

Welcome to Uptime Kuma
Your Node.js version: 22.22.0
2026-02-13T01:46:13Z [SERVER] INFO: Env: production
2026-02-13T01:46:13Z [SERVER] INFO: Uptime Kuma Version: 2.1.0
2026-02-13T01:46:13Z [SERVER] INFO: Loading modules
2026-02-13T01:46:15Z [SERVER] INFO: Creating express and socket.io instance
2026-02-13T01:46:15Z [SERVER] INFO: Server Type: HTTP
2026-02-13T01:46:15Z [SERVER] INFO: Data Dir: ./data/
2026-02-13T01:46:15Z [DB] INFO: Database Type: sqlite
2026-02-13T01:46:15Z [SERVER] INFO: Connected to the database
migration file "2026-01-10-0000-convert-float-precision.js" failed
migration failed with error: ROLLBACK TO SAVEPOINT trx27 - SQLITE_ERROR: no such savepoint: trx27
2026-02-13T01:46:27Z [DB] ERROR: Database migration failed
2026-02-13T01:46:27Z [SERVER] ERROR: Failed to prepare your database: ROLLBACK - SQLITE_ERROR: cannot rollback - no transaction is active

🐻 Uptime-Kuma Version

2.1.0

💻 Operating System and Arch

Debian 13

🌐 Browser

non-applicable

🖥️ Deployment Environment

Runtime Environment:
- Kubernetes (K3S): Version v1.34.3+k3s1 (48ffa7b6)
- go version go1.24.11
- containerd: v2.1.5-k3s1
Database:
- SQLite: Embedded
Database Storage:
- Filesystem:
  - Longhorn (v1.10.1) volumes
- Storage Medium: 1 HDD and 1 SSD node
Uptime Kuma Setup:
- Number of monitors: 10 or so

Originally created by @ChekeredList71 on GitHub (Feb 12, 2026). ### ⚠️ Please verify that your question has not already been reported - [x] I have searched the [existing issues](https://github.com/louislam/uptime-kuma/issues?q=is%3Aissue%20sort%3Acreated-desc%20) and found no similar reports. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Describe your problem After changing tags from louislam/uptime-kuma:latest -> louislam/uptime-kuma:2.1.0, Uptime Kuma no longer starts. DB integrity is ok: ``` $ sqlite3 kuma.db "PRAGMA integrity_check;" ok ``` ### 📝 Error Message(s) or Log ```bash session Welcome to Uptime Kuma Your Node.js version: 22.22.0 2026-02-13T01:46:13Z [SERVER] INFO: Env: production 2026-02-13T01:46:13Z [SERVER] INFO: Uptime Kuma Version: 2.1.0 2026-02-13T01:46:13Z [SERVER] INFO: Loading modules 2026-02-13T01:46:15Z [SERVER] INFO: Creating express and socket.io instance 2026-02-13T01:46:15Z [SERVER] INFO: Server Type: HTTP 2026-02-13T01:46:15Z [SERVER] INFO: Data Dir: ./data/ 2026-02-13T01:46:15Z [DB] INFO: Database Type: sqlite 2026-02-13T01:46:15Z [SERVER] INFO: Connected to the database migration file "2026-01-10-0000-convert-float-precision.js" failed migration failed with error: ROLLBACK TO SAVEPOINT trx27 - SQLITE_ERROR: no such savepoint: trx27 2026-02-13T01:46:27Z [DB] ERROR: Database migration failed 2026-02-13T01:46:27Z [SERVER] ERROR: Failed to prepare your database: ROLLBACK - SQLITE_ERROR: cannot rollback - no transaction is active ``` ### 🐻 Uptime-Kuma Version 2.1.0 ### 💻 Operating System and Arch Debian 13 ### 🌐 Browser non-applicable ### 🖥️ Deployment Environment - **Runtime Environment**: - Kubernetes (K3S): Version `v1.34.3+k3s1 (48ffa7b6)` - go version go1.24.11 - containerd: v2.1.5-k3s1 - **Database**: - SQLite: Embedded - **Database Storage**: - **Filesystem**: - Longhorn (v1.10.1) volumes - **Storage Medium**: 1 HDD and 1 SSD node - **Uptime Kuma Setup**: - Number of monitors: `10` or so

deekerman

2026-02-28 04:12:21 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@mrvalterhugo commented on GitHub (Feb 14, 2026):

I got a similar error after updating:

2026-02-14T12:47:00Z [SERVER] ERROR: Failed to prepare your database: SELECT value FROM setting WHERE key = 'database_version' limit 1 - SQLITE_CORRUPT: database disk image is malformed

@mrvalterhugo commented on GitHub (Feb 14, 2026): I got a similar error after updating: 2026-02-14T12:47:00Z [SERVER] ERROR: Failed to prepare your database: SELECT `value` FROM setting WHERE `key` = 'database_version' limit 1 - SQLITE_CORRUPT: database disk image is malformed

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 14, 2026):

@mrvalterhugo no that is different. Please see our issue tracker for how other people have resolved this.
Solving disc corruption is not something we can do in all cases, but some.

@CommanderStorm commented on GitHub (Feb 14, 2026): @mrvalterhugo no that is different. Please see our issue tracker for how other people have resolved this. Solving disc corruption is not something we can do in all cases, but some.

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@ChekeredList71 commented on GitHub (Feb 14, 2026):

@mrvalterhugo

You likely have a corrupt DB. Consider running PRAGMA integrity_check(); on the kuma.db file.

If you have more questions, ping me on the separate issue you created (if you did create one).

@ChekeredList71 commented on GitHub (Feb 14, 2026): @mrvalterhugo You likely have a corrupt DB. Consider running `PRAGMA integrity_check();` on the `kuma.db` file. If you have more questions, ping me on the separate issue you created (if you did create one).

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@mrvalterhugo commented on GitHub (Feb 14, 2026):

Thanks, I restored from a backup and it worked.

@mrvalterhugo commented on GitHub (Feb 14, 2026): Thanks, I restored from a backup and it worked.

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@HLVM04 commented on GitHub (Feb 16, 2026):

I am experiencing this exact issue as well.

Feb 16 20:57:29 uptimekuma npm[6861]: 2026-02-16T20:57:29+01:00 [SERVER] INFO: Loading modules
Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Creating express and socket.io inst>
Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Server Type: HTTP
Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Data Dir: ./data/
Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [DB] INFO: Database Type: sqlite
Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Connected to the database
Feb 16 20:59:09 uptimekuma npm[6861]: migration file "2026-01-10-0000-convert-float-precision.js" failed
Feb 16 20:59:09 uptimekuma npm[6861]: migration failed with error: ROLLBACK TO SAVEPOINT trx27 - SQLITE_ERROR: no >
Feb 16 20:59:09 uptimekuma npm[6861]: 2026-02-16T20:59:09+01:00 [DB] ERROR: Database migration failed
Feb 16 20:59:09 uptimekuma npm[6861]: 2026-02-16T20:59:09+01:00 [SERVER] ERROR: Failed to prepare your database: R>

@HLVM04 commented on GitHub (Feb 16, 2026): I am experiencing this exact issue as well. ``` Feb 16 20:57:29 uptimekuma npm[6861]: 2026-02-16T20:57:29+01:00 [SERVER] INFO: Loading modules Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Creating express and socket.io inst> Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Server Type: HTTP Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Data Dir: ./data/ Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [DB] INFO: Database Type: sqlite Feb 16 20:57:31 uptimekuma npm[6861]: 2026-02-16T20:57:31+01:00 [SERVER] INFO: Connected to the database Feb 16 20:59:09 uptimekuma npm[6861]: migration file "2026-01-10-0000-convert-float-precision.js" failed Feb 16 20:59:09 uptimekuma npm[6861]: migration failed with error: ROLLBACK TO SAVEPOINT trx27 - SQLITE_ERROR: no > Feb 16 20:59:09 uptimekuma npm[6861]: 2026-02-16T20:59:09+01:00 [DB] ERROR: Database migration failed Feb 16 20:59:09 uptimekuma npm[6861]: 2026-02-16T20:59:09+01:00 [SERVER] ERROR: Failed to prepare your database: R> ```

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Feb 16, 2026):

No clue how to reproduce this, it is not reproduced by the migration tests in master..

@CommanderStorm commented on GitHub (Feb 16, 2026): No clue how to reproduce this, it is not reproduced by the migration tests in master..

deekerman commented

2026-02-28 04:12:26 -05:00

Author

Owner

@HLVM04 commented on GitHub (Feb 16, 2026):

I managed to migrate the database successfully by increasing my LXC disk space by a few Gb. In my case it seems to have been a simple no-disk-space issue.

@HLVM04 commented on GitHub (Feb 16, 2026): I managed to migrate the database successfully by increasing my LXC disk space by a few Gb. In my case it seems to have been a simple no-disk-space issue.