Uptime Kuma 2.0.0 package

[imc67]

and what about this https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#rootless-vs-non-rootless?

Is it possible/safe to update and is the migration working?

[joseph]

@andreasdueren it's using the slim version .

@imc67 https://status.cloudron.io upgraded automatically . But it took ~20-30 mins for the migration to complete. After upgrade, it shows a message a in index page giving the status of the migration . Our app has ~1.5GB of data.

[imc67]

@joseph said in Uptime Kuma 2.0.0 package:

upgraded automatically . But it took ~20-30 mins for the migration to complete. After upgrade, it shows a message a in index page giving the status of the migration . Our app has ~1.5GB of data.

I gave it a try: 40 monitors with 7 days retention took 20 minutes, in the Logs Viewer you can see live the progress, all seems well after migration.

Thanks!!

[luckow]

My first try was a showstopper:

Oct 22 13:18:11 Your Node.js version: 18.20.8
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] ERROR: Failed to prepare your database: Aggregate table migration is already in progress
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Connected to the database
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Creating express and socket.io instance
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Data Dir: ./data/
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Loading modules
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Server Type: HTTP
Oct 22 13:18:12 2025-10-22T11:18:12Z [SERVER] INFO: Uptime Kuma Version: 2.0.1
Oct 22 13:18:12 2025-10-22T11:18:12Z [DB] ERROR: Database migration failed
Oct 22 13:18:12 2025-10-22T11:18:12Z [DB] WARN: Aggregate table migration is already in progress, or it was interrupted
Oct 22 13:18:12 2025-10-22T11:18:12Z [DB] INFO: Database Type: sqlite
Oct 22 13:18:13 \
Oct 22 13:18:38 ==> Overriding settings
Oct 22 13:18:38 ==> Removing sqlite backup files
Oct 22 13:18:38 ==> Starting Uptime Kuma
Oct 22 13:18:39 2025-10-22T13:18:39+02:00
Oct 22 13:18:39 2025-10-22T13:18:39+02:00
Oct 22 13:18:39 Welcome to Uptime Kuma

Now in an endless loop. I'll try it on a second clone.

[joseph]

@luckow maybe give the app more memory and then upgrade? Our status page is at 1GB RAM.

[luckow]

@joseph maybe. But first I have to fix this: Trace: [Error: select * from heartbeat where monitor_id = 75 ORDER BY time DESC limit 1 - SQLITE_CORRUPT: database disk image is malformed] This is a log entry BEFORE the 2.0 update.

[andreasdueren]

@joseph Yes, upgrade worked fine for me too. Took forever, probably almost an hour but I'm running it on a super low powered VPS. Does that mean no more embedded Chromium or did you package it in? Not using it, just curious.

[Lanhild]

I've opened an issue upstream, as starting the update triggered a false positive alert from Google Chrome on my subdomain:

• https://github.com/louislam/uptime-kuma/issues/6223

[luckow]

Woohoo. 2.0.1 update worked.
Q: Any plans to switch the app package to MariaDB instead of sqlite?

[Lanhild]

@luckow I don't believe we have a MariaDB addon.

[Lanhild]

Fixed with https://github.com/louislam/uptime-kuma/releases/tag/2.0.2.