malobeo/infrastructure
3
1
Fork 1
Code Issues 49 Pull Requests 5 Actions 1 Projects 3 Releases Wiki Activity

Uptime Kuma Migration Fails #167

New Issue
Open
opened 2026-08-12 22:01:50 +02:00 by kalipso · 1 comment
kalipso commented 2026-08-12 22:01:50 +02:00
Owner
Copy Link
Copy Source

Reason uptime kuma is not available is that database migration fails.

Logs (Reverse order - newest on top):

Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:52:22Z [SERVER] ERROR: Failed to prepare your database: ROLLBACK - SQLITE_ERROR: cannot rollback - no transaction is active
Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:52:22Z [DB] ERROR: Database migration failed
Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: migration failed with error: ROLLBACK TO SAVEPOINT trx27 - SQLITE_ERROR: no such savepoint: trx27
Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: migration file "2026-01-10-0000-convert-float-precision.js" failed
Aug 12 21:50:25 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:25Z [SERVER] INFO: Connected to the database
Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [DB] INFO: Using single connection for SQLite
Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [DB] INFO: Database Type: sqlite
Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [SETUP-DATABASE] INFO: UPTIME_KUMA_DB_TYPE is provided by env, try to override db-config.json
Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [SERVER] INFO: Data Dir: /var/lib/uptime-kuma/
Aug 12 21:50:23 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:23Z [SERVER] INFO: Custom hostname: 127.0.0.1
Aug 12 21:50:23 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:23Z [SERVER] INFO: Server Type: HTTP
Aug 12 21:50:23 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:23Z [SERVER] INFO: Creating express and socket.io instance
Aug 12 21:50:15 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:15Z [SERVER] INFO: Loading modules
Aug 12 21:50:15 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:15Z [SERVER] INFO: Uptime Kuma Version: 2.4.0
Aug 12 21:50:14 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:14Z [SERVER] INFO: Env: production

I restored the database from several different snapshots - some days ago, a month ago, half a year ago. I was not able to migrate any of them successfully.

This means we need to setup uptime kuma again from a fresh instance.

Alternative approach: Maybe its also possible to export configuration through the web interface - this way we could boot a microvm from brefore the 26.05 update, export settings through webinterface and than import them on the new instance.

Reason uptime kuma is not available is that database migration fails. Logs (Reverse order - newest on top): ``` Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:52:22Z [SERVER] ERROR: Failed to prepare your database: ROLLBACK - SQLITE_ERROR: cannot rollback - no transaction is active Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:52:22Z [DB] ERROR: Database migration failed Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: migration failed with error: ROLLBACK TO SAVEPOINT trx27 - SQLITE_ERROR: no such savepoint: trx27 Aug 12 21:52:22 uptimekuma uptime-kuma-server[1242]: migration file "2026-01-10-0000-convert-float-precision.js" failed Aug 12 21:50:25 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:25Z [SERVER] INFO: Connected to the database Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [DB] INFO: Using single connection for SQLite Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [DB] INFO: Database Type: sqlite Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [SETUP-DATABASE] INFO: UPTIME_KUMA_DB_TYPE is provided by env, try to override db-config.json Aug 12 21:50:24 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:24Z [SERVER] INFO: Data Dir: /var/lib/uptime-kuma/ Aug 12 21:50:23 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:23Z [SERVER] INFO: Custom hostname: 127.0.0.1 Aug 12 21:50:23 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:23Z [SERVER] INFO: Server Type: HTTP Aug 12 21:50:23 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:23Z [SERVER] INFO: Creating express and socket.io instance Aug 12 21:50:15 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:15Z [SERVER] INFO: Loading modules Aug 12 21:50:15 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:15Z [SERVER] INFO: Uptime Kuma Version: 2.4.0 Aug 12 21:50:14 uptimekuma uptime-kuma-server[1242]: 2026-08-12T19:50:14Z [SERVER] INFO: Env: production ``` I restored the database from several different snapshots - some days ago, a month ago, half a year ago. I was not able to migrate any of them successfully. This means we need to setup uptime kuma again from a fresh instance. Alternative approach: Maybe its also possible to export configuration through the web interface - this way we could boot a microvm from brefore the `26.05` update, export settings through webinterface and than import them on the new instance.
ahtlon commented 2026-08-17 12:12:33 +02:00
Owner
Copy Link
Copy Source

There is an issue here, but there's no real solution except restarting from scratch

There is an issue [here](https://github.com/louislam/uptime-kuma/issues/6920), but there's no real solution except restarting from scratch
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Bug/Problem
Lokal
Migration
Module/Disks
Module/Initssh
Request
Security
Service
Updates
bump
nextcloud
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
Bender (Bender Bending Rodríguez) ahtlon kalipso quinn
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: malobeo/infrastructure#167