starred/uptime-kuma
1
0
Fork 0
mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00
Code Issues 754 Projects Packages Wiki Activity

Uptime Kuma 2.0 Upgrade - Percentage Indicator broken & Disk Usage not changing almost at all / No MariaDB Files Saved ? #4349

New issue
Closed
opened 2026-02-28 03:59:13 -05:00 by deekerman · 11 comments
deekerman commented 2026-02-28 03:59:13 -05:00
Owner
Copy link

Originally created by @luckylinux on GitHub (Oct 21, 2025).

📑 I have found these related issues/pull requests

Unable to find any Issues related to percentage, indicator or upgrade which seemed relevant.

🛡️ Security Policy

📝 Description

I changed the Image from Uptime Kuma 1.x Branch to Uptime Kuma 2.x, as indicated in the Upgrade Notes.

The Progress Indicator always stays at 0%, even though the Monitor Data is currently set at 43/87.

Disk Space for the data Bind-Mount seems to also be unaffected.

I would expect either the Disk Space to Double (if cleanup later) or at least some other new Files for MariaDB (embedded) to be created, but neither of these are happening.

It's been approx. 10 Hours.

👟 Reproduction steps

Just change the Docker Image from Uptime Kuma 1.x Branch to Uptime Kuma 2.x, as indicated in the Upgrade Notes.

In my Case, I change the Podman Quadlet uptime-kuma-server.container from:

[Unit]
Description=Uptime Kuma Server Container
Requires=uptime-kuma-caddy.service
After=uptime-kuma-caddy.service

[Service]
Restart=always

[Container]
ContainerName=uptime-kuma-server

Pod=uptime-kuma.pod
StartWithPod=true

Image=louislam/uptime-kuma:1-debian
Network=container:uptime-kuma-caddy
Pull=missing

Volume=/run/user/1002/podman/podman.sock:/var/run/docker.sock:ro,Z
Volume=/home/podman/containers/data/uptime-kuma/server:/app/data:Z

To uptime-kuma-server.container:

[Unit]
Description=Uptime Kuma Server Container
Requires=uptime-kuma-caddy.service
After=uptime-kuma-caddy.service

[Service]
Restart=always

[Container]
ContainerName=uptime-kuma-server

Pod=uptime-kuma.pod
StartWithPod=true

Image=louislam/uptime-kuma:2
Network=container:uptime-kuma-caddy
Pull=missing

Volume=/run/user/1002/podman/podman.sock:/var/run/docker.sock:ro,Z
Volume=/home/podman/containers/data/uptime-kuma/server:/app/data:Z

👀 Expected behavior

Percentage Indicator should increase.

Furthermore, not sure where uptime Kuma is saving the Data for the new embedded MariaDB (I assume it's still somewhere in the data Folder), but I would expect the Size on Disk to increase.

If I check my bind-mounts there does NOT seem to be any Change happening at all:

podman@podmanserver:~/containers/data/uptime-kuma$ du -sh ./*
20K	./caddy
6.7G	./server
6.7G	./server.backup.20251020

podman@podmanserver:~/containers/data/uptime-kuma$ ls -lh server
total 6.7G
-rw-r--r--. 1 podman podman   24 Oct 20 19:33 db-config.json
drwxr-xr-x. 2 podman podman 4.0K Dec 13  2024 docker-tls
-rw-r--r--. 1 podman podman 304K Oct 20 19:12 error.log
-rwxr-xr-x. 1 podman podman 6.7G Oct 21 05:59 kuma.db
-rwxr-xr-x. 1 podman podman  32K Oct 21 05:59 kuma.db-shm
-rwxr-xr-x. 1 podman podman 4.1M Oct 21 05:59 kuma.db-wal
drwxr-xr-x. 2 podman podman 4.0K Dec 13  2024 screenshots
drwxr-xr-x. 2 podman podman 4.0K Dec 13  2024 upload

podman@podmanserver:~/containers/data/uptime-kuma$ ls -lh server.backup.20251020
total 6.7G
drwxr-xr-x. 2 podman podman 4.0K Dec 13  2024 docker-tls
-rw-r--r--. 1 podman podman 304K Oct 20 19:12 error.log
-rwxr-xr-x. 1 podman podman 6.7G Oct 20 19:12 kuma.db
-rwxr-xr-x. 1 podman podman  32K Oct 20 19:12 kuma.db-shm
-rwxr-xr-x. 1 podman podman 4.1M Oct 20 19:12 kuma.db-wal
drwxr-xr-x. 2 podman podman 4.0K Dec 13  2024 screenshots
drwxr-xr-x. 2 podman podman 4.0K Dec 13  2024 upload

I would expect either the Disk Space to Double (if cleanup later) or at least some other new Files for MariaDB (embedded) to be created, but neither of these are happening.

I'm also extremely confused by the Statement at the end of the Migration Guide:

Can I migrate my existing SQLite database to MariaDB?

Cannot be done directly. You will need to export your data from SQLite and import it into MariaDB using 3rd party tools.

If the Migration of Data is not done automatically, then what is it taking 10+ Hours for the Migration to take place ?

😓 Actual Behavior

Oct 20 19:31:54 podmanserver systemd[839]: Starting uptime-kuma-server.service - Uptime Kuma Server Container...
░░ Subject: A start job for unit UNIT has begun execution
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░ 
░░ A start job for unit UNIT has begun execution.
░░ 
░░ The job identifier is 4591243.
Oct 20 19:31:54 podmanserver uptime-kuma-server[3675860]: Resolved "louislam/uptime-kuma" as an alias (/home/podman/.cache/containers/short-name-aliases.conf)
Oct 20 19:31:54 podmanserver uptime-kuma-server[3675860]: Trying to pull docker.MYDOMAIN.TLD/louislam/uptime-kuma:2...
Oct 20 19:31:54 podmanserver uptime-kuma-server[3675860]: Pulling image //docker.MYDOMAIN.TLD/louislam/uptime-kuma:2 inside systemd: setting pull timeout to 5m0s
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Getting image source signatures
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:c96d1635ad0991f730060719731a8a5d135c1039376a5c9df722d901915d2c01
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:c236995d12f2157ee427471a193f6d4a42377289b3095093d8c86187d77f768d
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:997b350cffa15286d430b21f1c133c4b455e74d22f03faf3cc70504d3cff87ff
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:ab9c5ae25e4db3eb06f491a7fe8df1c64545a2f2c1cdc078ae5daf3c76d916c2
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:5c32499ab806884c5725c705c2bf528662d034ed99de13d3205309e0d9ef0375
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:cc663995c53d1076d7066652c9e96f9dca65a2077ef4eb7957931e264640f769
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:26fe02595b648720aa5074d13869a9d61c881b9e05247bef2ab135b11ff290a8
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:ce43fa88f43ae8e137f1572692a85bd2832ce272dbeda209809db2ad31c20a47
Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:17b86553b1c83fba0d83ac914ffa9b738d6a57c0bbde259acd696fd775e8ceea
Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:fe60297d5e1c1afa01919d611b1effa624442eb602334319623739d961483593
Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:b7f9c2a776ef0ddab9f0eb86c661e33518edf9af47d1f99f883acadc6cee0127
Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:1cd1753349325cd64aa9e863f2455e512255145590edaa67d0b5a8c3fa92790d
Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:6fee2268553a1b25c91c7ab5fb4164efca55759dd5819081a9053bfaf246fd60
Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:21622836d4422ffc7f2c6facc8696ffae3123c68c04c4ff882ff0b0846de82c5
Oct 20 19:33:21 podmanserver uptime-kuma-server[3675860]: Copying config sha256:4297d36163e96ae253502178a221721b8c7be354b412be0e946e35006cfd8ac5
Oct 20 19:33:22 podmanserver uptime-kuma-server[3675860]: Writing manifest to image destination
Oct 20 19:33:24 podmanserver podman[3675860]: 2025-10-20 19:33:24.018617701 +0200 CEST m=+89.415641925 image pull 4297d36163e96ae253502178a221721b8c7be354b412be0e946e35006cfd8ac5 louislam/uptime-kuma:2
Oct 20 19:33:24 podmanserver podman[3675860]: 2025-10-20 19:33:24.560598902 +0200 CEST m=+89.957623112 container create 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 (image=docker.MYDOMAIN.TLD/louislam/uptime-kuma:2, name=uptime-kuma-server, pod_id=0e1d0ca59233e8d8afc409bc797f97c3f9ed4232515aea32739b8123076287ac, PODMAN_SYSTEMD_UNIT=uptime-kuma-server.service, org.opencontainers.image.source=https://github.com/louislam/uptime-kuma)
Oct 20 19:33:28 podmanserver podman[3675860]: 2025-10-20 19:33:28.080040791 +0200 CEST m=+93.477065013 container init 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 (image=docker.MYDOMAIN.TLD/louislam/uptime-kuma:2, name=uptime-kuma-server, pod_id=0e1d0ca59233e8d8afc409bc797f97c3f9ed4232515aea32739b8123076287ac, PODMAN_SYSTEMD_UNIT=uptime-kuma-server.service, org.opencontainers.image.source=https://github.com/louislam/uptime-kuma)
Oct 20 19:33:28 podmanserver podman[3675860]: 2025-10-20 19:33:28.087428471 +0200 CEST m=+93.484452695 container start 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 (image=docker.MYDOMAIN.TLD/louislam/uptime-kuma:2, name=uptime-kuma-server, pod_id=0e1d0ca59233e8d8afc409bc797f97c3f9ed4232515aea32739b8123076287ac, PODMAN_SYSTEMD_UNIT=uptime-kuma-server.service, org.opencontainers.image.source=https://github.com/louislam/uptime-kuma)
Oct 20 19:33:28 podmanserver systemd[839]: Started uptime-kuma-server.service - Uptime Kuma Server Container.
░░ Subject: A start job for unit UNIT has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel


░ 
░░ A start job for unit UNIT has finished successfully.
░░ 
░░ The job identifier is 4591243.
Oct 20 19:33:28 podmanserver uptime-kuma-server[3681684]: Welcome to Uptime Kuma
Oct 20 19:33:28 podmanserver uptime-kuma-server[3681684]: Your Node.js version: 20.19.5
Oct 20 19:33:28 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:28Z [SERVER] INFO: Env: production
Oct 20 19:33:28 podmanserver uptime-kuma-server[3675860]: 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638
Oct 20 19:33:30 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:30Z [SERVER] INFO: Uptime Kuma Version: 2.0.1
Oct 20 19:33:30 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:30Z [SERVER] INFO: Loading modules
Oct 20 19:33:31 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:31Z [SERVER] INFO: Creating express and socket.io instance
Oct 20 19:33:31 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:31Z [SERVER] INFO: Server Type: HTTP
Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SERVER] INFO: Data Dir: ./data/
Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json'
Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SETUP-DATABASE] INFO: kuma.db is found, generate db-config.json
Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [DB] INFO: Database Type: sqlite
Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SERVER] INFO: Connected to the database
Oct 20 19:33:37 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:37Z [MIGRATION] INFO: Migration server is running on http://localhost:3001
Oct 20 19:33:37 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:37Z [DB] INFO: Migrating Aggregate Table
Oct 20 19:33:37 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:37Z [DB] INFO: Getting list of unique monitors
Oct 20 19:33:56 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:56Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-22 [0.00%][1/87]
Oct 20 19:33:59 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:58Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-23 [0.00%][1/87]
Oct 20 19:34:01 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:01Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-24 [0.00%][1/87]
Oct 20 19:34:04 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:04Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-25 [0.00%][1/87]
Oct 20 19:34:07 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:07Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-26 [0.00%][1/87]
Oct 20 19:34:10 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:10Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-27 [0.00%][1/87]
Oct 20 19:34:12 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:12Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-28 [0.00%][1/87]
Oct 20 19:34:15 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:15Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-29 [0.00%][1/87]
Oct 20 19:34:17 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:17Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-30 [0.00%][1/87]
Oct 20 19:34:20 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:20Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-31 [0.00%][1/87]
Oct 20 19:34:22 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:22Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-01 [0.00%][1/87]
Oct 20 19:34:24 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:24Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-02 [0.00%][1/87]
Oct 20 19:34:27 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:27Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-03 [0.00%][1/87]
Oct 20 19:34:30 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:30Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-04 [0.00%][1/87]
Oct 20 19:34:43 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:43Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-05 [0.00%][1/87]
Oct 20 19:34:49 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:49Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-06 [0.00%][1/87]
Oct 20 19:34:58 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:58Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-07 [

...
...
...

Oct 21 05:49:29 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:29Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-02 [0.00%][38/87]
Oct 21 05:49:30 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:30Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-03 [0.00%][38/87]
Oct 21 05:49:32 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:32Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-04 [0.00%][38/87]
Oct 21 05:49:33 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:33Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-05 [0.00%][38/87]
Oct 21 05:49:34 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:34Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-06 [0.00%][38/87]
Oct 21 05:49:35 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:35Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-07 [0.00%][38/87]
Oct 21 05:49:36 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:36Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-08 [0.00%][38/87]
Oct 21 05:49:37 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:37Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-09 [0.00%][38/87]
Oct 21 05:49:38 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:38Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-10 [0.00%][38/87]
Oct 21 05:49:39 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:39Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-11 [0.00%][38/87]
Oct 21 05:49:40 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:40Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-12 [0.00%][38/87]
Oct 21 05:49:41 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:41Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-13 [0.00%][38/87]
Oct 21 05:49:42 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:42Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-14 [0.00%][38/87]
Oct 21 05:49:44 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:44Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-15 [0.00%][38/87]
Oct 21 05:49:45 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:45Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-16 [0.00%][38/87]
Oct 21 05:49:46 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:46Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-17 [0.00%][38/87]

🐻 Uptime-Kuma Version

2.0.1

💻 Operating System and Arch

Fedora 42 AMD64 on KVM [Proxmox VE] (Linux podmanserver 6.16.12-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Oct 12 16:31:16 UTC 2025 x86_64 GNU/Linux)

🌐 Browser

Librewolf 144.0-1 (64-Bit)

🖥️ Deployment Environment

  • Runtime Environment:
    • Podman: Version 5.6.2 (Git Commit 9dd5e1ed33830612bc200d7a13db00af6ab865a4)
    • Docker Compose: N/A (using Podman Quadlets)
    • Portainer (BE/CE): N/A (using Podman Quadlets written by Hand)
    • MariaDB: Version 15.1 (LTS: Yes/No - Unknown), embedded in louislam/uptime-kuma:2 Docker Image) - mariadb Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper
    • Node.js: Version 20.19.5 (LTS: Yes/No - Unknown)
    • Kubernetes (K3S/K8S): N/A (running as Podman Quadlet in Standalone Setup)
  • Database (currently upgrading from Uptime Kuma 1.x to Uptime Kuma 2.x):
    • SQLite: Embedded
    • MariaDB: Embedded
  • Database Storage:
    • Filesystem:
      • Linux: ext4 (inside Fedora VM) on top of ZFS ZVOL (Proxmox VE Host)
    • Storage Medium: SATA SSD
  • Uptime Kuma Setup:
    • Number of monitors: 87

📝 Relevant log output
Originally created by @luckylinux on GitHub (Oct 21, 2025). ### 📑 I have found these related issues/pull requests Unable to find any Issues related to `percentage`, `indicator` or `upgrade` which seemed relevant. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description I changed the Image from Uptime Kuma 1.x Branch to Uptime Kuma 2.x, as indicated in the [Upgrade Notes](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#migration-steps-docker-compose). The Progress Indicator always stays at 0%, even though the Monitor Data is currently set at `43/87`. Disk Space for the `data` Bind-Mount seems to also be unaffected. I would expect either the Disk Space to Double (if cleanup later) or at least some other new Files for MariaDB (embedded) to be created, but neither of these are happening. It's been approx. 10 Hours. ### 👟 Reproduction steps Just change the Docker Image from Uptime Kuma 1.x Branch to Uptime Kuma 2.x, as indicated in the [Upgrade Notes](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#migration-steps-docker-compose). In my Case, I change the Podman Quadlet `uptime-kuma-server.container` from: ``` [Unit] Description=Uptime Kuma Server Container Requires=uptime-kuma-caddy.service After=uptime-kuma-caddy.service [Service] Restart=always [Container] ContainerName=uptime-kuma-server Pod=uptime-kuma.pod StartWithPod=true Image=louislam/uptime-kuma:1-debian Network=container:uptime-kuma-caddy Pull=missing Volume=/run/user/1002/podman/podman.sock:/var/run/docker.sock:ro,Z Volume=/home/podman/containers/data/uptime-kuma/server:/app/data:Z ``` To `uptime-kuma-server.container`: ``` [Unit] Description=Uptime Kuma Server Container Requires=uptime-kuma-caddy.service After=uptime-kuma-caddy.service [Service] Restart=always [Container] ContainerName=uptime-kuma-server Pod=uptime-kuma.pod StartWithPod=true Image=louislam/uptime-kuma:2 Network=container:uptime-kuma-caddy Pull=missing Volume=/run/user/1002/podman/podman.sock:/var/run/docker.sock:ro,Z Volume=/home/podman/containers/data/uptime-kuma/server:/app/data:Z ``` ### 👀 Expected behavior Percentage Indicator should increase. Furthermore, not sure where uptime Kuma is saving the Data for the new embedded MariaDB (I assume it's still somewhere in the `data` Folder), but I would expect the Size on Disk to increase. If I check my bind-mounts there does NOT seem to be any Change happening at all: ``` podman@podmanserver:~/containers/data/uptime-kuma$ du -sh ./* 20K ./caddy 6.7G ./server 6.7G ./server.backup.20251020 podman@podmanserver:~/containers/data/uptime-kuma$ ls -lh server total 6.7G -rw-r--r--. 1 podman podman 24 Oct 20 19:33 db-config.json drwxr-xr-x. 2 podman podman 4.0K Dec 13 2024 docker-tls -rw-r--r--. 1 podman podman 304K Oct 20 19:12 error.log -rwxr-xr-x. 1 podman podman 6.7G Oct 21 05:59 kuma.db -rwxr-xr-x. 1 podman podman 32K Oct 21 05:59 kuma.db-shm -rwxr-xr-x. 1 podman podman 4.1M Oct 21 05:59 kuma.db-wal drwxr-xr-x. 2 podman podman 4.0K Dec 13 2024 screenshots drwxr-xr-x. 2 podman podman 4.0K Dec 13 2024 upload podman@podmanserver:~/containers/data/uptime-kuma$ ls -lh server.backup.20251020 total 6.7G drwxr-xr-x. 2 podman podman 4.0K Dec 13 2024 docker-tls -rw-r--r--. 1 podman podman 304K Oct 20 19:12 error.log -rwxr-xr-x. 1 podman podman 6.7G Oct 20 19:12 kuma.db -rwxr-xr-x. 1 podman podman 32K Oct 20 19:12 kuma.db-shm -rwxr-xr-x. 1 podman podman 4.1M Oct 20 19:12 kuma.db-wal drwxr-xr-x. 2 podman podman 4.0K Dec 13 2024 screenshots drwxr-xr-x. 2 podman podman 4.0K Dec 13 2024 upload ``` I would expect either the Disk Space to Double (if cleanup later) or at least some other new Files for MariaDB (embedded) to be created, but neither of these are happening. I'm also **extremely** confused by the Statement at the end of the [Migration Guide](https://github.com/louislam/uptime-kuma/wiki/Migration-From-v1-To-v2#can-i-migrate-my-existing-sqlite-database-to-mariadb): > Can I migrate my existing SQLite database to MariaDB? > > Cannot be done directly. You will need to export your data from SQLite and import it into MariaDB using 3rd party tools. If the Migration of Data is not done automatically, then what is it taking 10+ Hours for the Migration to take place ? ### 😓 Actual Behavior ``` Oct 20 19:31:54 podmanserver systemd[839]: Starting uptime-kuma-server.service - Uptime Kuma Server Container... ░░ Subject: A start job for unit UNIT has begun execution ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░░ ░░ A start job for unit UNIT has begun execution. ░░ ░░ The job identifier is 4591243. Oct 20 19:31:54 podmanserver uptime-kuma-server[3675860]: Resolved "louislam/uptime-kuma" as an alias (/home/podman/.cache/containers/short-name-aliases.conf) Oct 20 19:31:54 podmanserver uptime-kuma-server[3675860]: Trying to pull docker.MYDOMAIN.TLD/louislam/uptime-kuma:2... Oct 20 19:31:54 podmanserver uptime-kuma-server[3675860]: Pulling image //docker.MYDOMAIN.TLD/louislam/uptime-kuma:2 inside systemd: setting pull timeout to 5m0s Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Getting image source signatures Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:c96d1635ad0991f730060719731a8a5d135c1039376a5c9df722d901915d2c01 Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:c236995d12f2157ee427471a193f6d4a42377289b3095093d8c86187d77f768d Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:997b350cffa15286d430b21f1c133c4b455e74d22f03faf3cc70504d3cff87ff Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:ab9c5ae25e4db3eb06f491a7fe8df1c64545a2f2c1cdc078ae5daf3c76d916c2 Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:5c32499ab806884c5725c705c2bf528662d034ed99de13d3205309e0d9ef0375 Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:cc663995c53d1076d7066652c9e96f9dca65a2077ef4eb7957931e264640f769 Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:26fe02595b648720aa5074d13869a9d61c881b9e05247bef2ab135b11ff290a8 Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:ce43fa88f43ae8e137f1572692a85bd2832ce272dbeda209809db2ad31c20a47 Oct 20 19:31:55 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:17b86553b1c83fba0d83ac914ffa9b738d6a57c0bbde259acd696fd775e8ceea Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:fe60297d5e1c1afa01919d611b1effa624442eb602334319623739d961483593 Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:b7f9c2a776ef0ddab9f0eb86c661e33518edf9af47d1f99f883acadc6cee0127 Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:1cd1753349325cd64aa9e863f2455e512255145590edaa67d0b5a8c3fa92790d Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:6fee2268553a1b25c91c7ab5fb4164efca55759dd5819081a9053bfaf246fd60 Oct 20 19:31:56 podmanserver uptime-kuma-server[3675860]: Copying blob sha256:21622836d4422ffc7f2c6facc8696ffae3123c68c04c4ff882ff0b0846de82c5 Oct 20 19:33:21 podmanserver uptime-kuma-server[3675860]: Copying config sha256:4297d36163e96ae253502178a221721b8c7be354b412be0e946e35006cfd8ac5 Oct 20 19:33:22 podmanserver uptime-kuma-server[3675860]: Writing manifest to image destination Oct 20 19:33:24 podmanserver podman[3675860]: 2025-10-20 19:33:24.018617701 +0200 CEST m=+89.415641925 image pull 4297d36163e96ae253502178a221721b8c7be354b412be0e946e35006cfd8ac5 louislam/uptime-kuma:2 Oct 20 19:33:24 podmanserver podman[3675860]: 2025-10-20 19:33:24.560598902 +0200 CEST m=+89.957623112 container create 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 (image=docker.MYDOMAIN.TLD/louislam/uptime-kuma:2, name=uptime-kuma-server, pod_id=0e1d0ca59233e8d8afc409bc797f97c3f9ed4232515aea32739b8123076287ac, PODMAN_SYSTEMD_UNIT=uptime-kuma-server.service, org.opencontainers.image.source=https://github.com/louislam/uptime-kuma) Oct 20 19:33:28 podmanserver podman[3675860]: 2025-10-20 19:33:28.080040791 +0200 CEST m=+93.477065013 container init 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 (image=docker.MYDOMAIN.TLD/louislam/uptime-kuma:2, name=uptime-kuma-server, pod_id=0e1d0ca59233e8d8afc409bc797f97c3f9ed4232515aea32739b8123076287ac, PODMAN_SYSTEMD_UNIT=uptime-kuma-server.service, org.opencontainers.image.source=https://github.com/louislam/uptime-kuma) Oct 20 19:33:28 podmanserver podman[3675860]: 2025-10-20 19:33:28.087428471 +0200 CEST m=+93.484452695 container start 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 (image=docker.MYDOMAIN.TLD/louislam/uptime-kuma:2, name=uptime-kuma-server, pod_id=0e1d0ca59233e8d8afc409bc797f97c3f9ed4232515aea32739b8123076287ac, PODMAN_SYSTEMD_UNIT=uptime-kuma-server.service, org.opencontainers.image.source=https://github.com/louislam/uptime-kuma) Oct 20 19:33:28 podmanserver systemd[839]: Started uptime-kuma-server.service - Uptime Kuma Server Container. ░░ Subject: A start job for unit UNIT has finished successfully ░░ Defined-By: systemd ░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel ░ ░░ A start job for unit UNIT has finished successfully. ░░ ░░ The job identifier is 4591243. Oct 20 19:33:28 podmanserver uptime-kuma-server[3681684]: Welcome to Uptime Kuma Oct 20 19:33:28 podmanserver uptime-kuma-server[3681684]: Your Node.js version: 20.19.5 Oct 20 19:33:28 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:28Z [SERVER] INFO: Env: production Oct 20 19:33:28 podmanserver uptime-kuma-server[3675860]: 00c5d2c4b2a07e05af2dbb113ec3695da178c8d949a67b8bc6d3da54b91fc638 Oct 20 19:33:30 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:30Z [SERVER] INFO: Uptime Kuma Version: 2.0.1 Oct 20 19:33:30 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:30Z [SERVER] INFO: Loading modules Oct 20 19:33:31 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:31Z [SERVER] INFO: Creating express and socket.io instance Oct 20 19:33:31 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:31Z [SERVER] INFO: Server Type: HTTP Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SERVER] INFO: Data Dir: ./data/ Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json' Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SETUP-DATABASE] INFO: kuma.db is found, generate db-config.json Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [DB] INFO: Database Type: sqlite Oct 20 19:33:32 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:32Z [SERVER] INFO: Connected to the database Oct 20 19:33:37 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:37Z [MIGRATION] INFO: Migration server is running on http://localhost:3001 Oct 20 19:33:37 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:37Z [DB] INFO: Migrating Aggregate Table Oct 20 19:33:37 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:37Z [DB] INFO: Getting list of unique monitors Oct 20 19:33:56 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:56Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-22 [0.00%][1/87] Oct 20 19:33:59 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:33:58Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-23 [0.00%][1/87] Oct 20 19:34:01 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:01Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-24 [0.00%][1/87] Oct 20 19:34:04 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:04Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-25 [0.00%][1/87] Oct 20 19:34:07 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:07Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-26 [0.00%][1/87] Oct 20 19:34:10 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:10Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-27 [0.00%][1/87] Oct 20 19:34:12 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:12Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-28 [0.00%][1/87] Oct 20 19:34:15 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:15Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-29 [0.00%][1/87] Oct 20 19:34:17 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:17Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-30 [0.00%][1/87] Oct 20 19:34:20 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:20Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-01-31 [0.00%][1/87] Oct 20 19:34:22 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:22Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-01 [0.00%][1/87] Oct 20 19:34:24 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:24Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-02 [0.00%][1/87] Oct 20 19:34:27 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:27Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-03 [0.00%][1/87] Oct 20 19:34:30 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:30Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-04 [0.00%][1/87] Oct 20 19:34:43 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:43Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-05 [0.00%][1/87] Oct 20 19:34:49 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:49Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-06 [0.00%][1/87] Oct 20 19:34:58 podmanserver uptime-kuma-server[3681684]: 2025-10-20T17:34:58Z [DB] INFO: [DON'T STOP] Migrating monitor data 1 - 2024-02-07 [ ... ... ... Oct 21 05:49:29 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:29Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-02 [0.00%][38/87] Oct 21 05:49:30 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:30Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-03 [0.00%][38/87] Oct 21 05:49:32 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:32Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-04 [0.00%][38/87] Oct 21 05:49:33 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:33Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-05 [0.00%][38/87] Oct 21 05:49:34 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:34Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-06 [0.00%][38/87] Oct 21 05:49:35 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:35Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-07 [0.00%][38/87] Oct 21 05:49:36 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:36Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-08 [0.00%][38/87] Oct 21 05:49:37 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:37Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-09 [0.00%][38/87] Oct 21 05:49:38 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:38Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-10 [0.00%][38/87] Oct 21 05:49:39 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:39Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-11 [0.00%][38/87] Oct 21 05:49:40 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:40Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-12 [0.00%][38/87] Oct 21 05:49:41 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:41Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-13 [0.00%][38/87] Oct 21 05:49:42 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:42Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-14 [0.00%][38/87] Oct 21 05:49:44 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:44Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-15 [0.00%][38/87] Oct 21 05:49:45 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:45Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-16 [0.00%][38/87] Oct 21 05:49:46 podmanserver uptime-kuma-server[3681684]: 2025-10-21T03:49:46Z [DB] INFO: [DON'T STOP] Migrating monitor data 39 - 2025-08-17 [0.00%][38/87] ``` ### 🐻 Uptime-Kuma Version 2.0.1 ### 💻 Operating System and Arch Fedora 42 AMD64 on KVM [Proxmox VE] (Linux podmanserver 6.16.12-200.fc42.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Oct 12 16:31:16 UTC 2025 x86_64 GNU/Linux) ### 🌐 Browser Librewolf 144.0-1 (64-Bit) ### 🖥️ Deployment Environment - **Runtime Environment**: - Podman: Version `5.6.2` (Git Commit `9dd5e1ed33830612bc200d7a13db00af6ab865a4`) - Docker Compose: N/A (using Podman Quadlets) - Portainer (BE/CE): N/A (using Podman Quadlets written by Hand) - MariaDB: Version `15.1` (LTS: Yes/No - Unknown), embedded in `louislam/uptime-kuma:2` Docker Image) - `mariadb Ver 15.1 Distrib 10.11.14-MariaDB, for debian-linux-gnu (x86_64) using EditLine wrapper` - Node.js: Version `20.19.5` (LTS: Yes/No - Unknown) - Kubernetes (K3S/K8S): N/A (running as Podman Quadlet in Standalone Setup) - **Database** (currently upgrading from Uptime Kuma 1.x to Uptime Kuma 2.x): - SQLite: Embedded - MariaDB: Embedded - **Database Storage**: - **Filesystem**: - Linux: ext4 (inside Fedora VM) on top of ZFS ZVOL (Proxmox VE Host) - **Storage Medium**: SATA SSD - **Uptime Kuma Setup**: - Number of monitors: `87` ### 📝 Relevant log output ```bash session ```
deekerman 2026-02-28 03:59:13 -05:00
  • closed this issue
  • added the
    Stale
    help
         labels
deekerman commented 2026-02-28 03:59:18 -05:00
Author
Owner
Copy link

@CommanderStorm commented on GitHub (Oct 21, 2025):

We are migrating from storing every heartbeat to storing them in an Aggregated form.
We essentially need to read every row of your heartbeat and aggregate them.
This is somewhat expensive.

We will not migrate the dB backend for you.

@CommanderStorm commented on GitHub (Oct 21, 2025): We are migrating from storing every heartbeat to storing them in an Aggregated form. We essentially need to read every row of your heartbeat and aggregate them. This is somewhat expensive. We will not migrate the dB backend for you.
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@luckylinux commented on GitHub (Oct 21, 2025):

Do you mean that it's actually reading and re-writing an aggregated Form of the existing Data, but keeping it in the existing SQLite Database Form ?

@luckylinux commented on GitHub (Oct 21, 2025): Do you mean that it's actually reading and re-writing an aggregated Form of the existing Data, but keeping it in the existing SQLite Database Form ?
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@CommanderStorm commented on GitHub (Oct 21, 2025):

Yes. And that takes a while which is to be expected.

Could likely be optimised, but hey

@CommanderStorm commented on GitHub (Oct 21, 2025): Yes. And that takes a while which is to be expected. Could likely be optimised, but hey
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@luckylinux commented on GitHub (Oct 21, 2025):

So after 10 Hours sitting still at 0% (even though half the Monitors were processed), that's normal to you ?

Unfortunately I had to restart from Scratch 😞. I tried to disable Automatic Reboots after Fedora Updates (since sometimes DNF Triggers it), but then I restarted one Service which actually restarted the entire System.

So there we go again 🤣 ... 2 Hours in now and sitting at:

Oct 21 17:42:47 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:47Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-19 [0.00%][7/87]
Oct 21 17:42:48 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:48Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-20 [0.00%][7/87]
Oct 21 17:42:49 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:49Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-21 [0.00%][7/87]
Oct 21 17:42:50 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:50Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-22 [0.00%][7/87]
@luckylinux commented on GitHub (Oct 21, 2025): So after 10 Hours sitting still at 0% (even though half the Monitors were processed), that's normal to you ? Unfortunately I had to restart from Scratch 😞. I tried to disable Automatic Reboots after Fedora Updates (since sometimes DNF Triggers it), but then I restarted one Service which actually restarted the entire System. So there we go again 🤣 ... 2 Hours in now and sitting at: ``` Oct 21 17:42:47 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:47Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-19 [0.00%][7/87] Oct 21 17:42:48 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:48Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-20 [0.00%][7/87] Oct 21 17:42:49 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:49Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-21 [0.00%][7/87] Oct 21 17:42:50 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:50Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-22 [0.00%][7/87] ```
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@klafbang commented on GitHub (Oct 21, 2025):

Just did an upgrade as well, and my percentages were wonky as well (got to 100% at around monitor 55 out of 65). It still finishes just fine.

My upgrade took around an hour for 65 monitors and 100 days of history – running from source without Docker (just under half being daily heartbeats with way fewer data points, say 4000 monitor-days of data), so 10+ hours for 87 monitors going back almost 2 years (~55000 monitor-days, or ~14 times mine) doesn't seem unreasonable. Mine also ran faster per day (1-3 days/second vs 1-3 seconds/day for yours - possibly you have more data points per day).

@klafbang commented on GitHub (Oct 21, 2025): Just did an upgrade as well, and my percentages were wonky as well (got to 100% at around monitor 55 out of 65). It still finishes just fine. My upgrade took around an hour for 65 monitors and 100 days of history – running from source without Docker (just under half being daily heartbeats with way fewer data points, say 4000 monitor-days of data), so 10+ hours for 87 monitors going back almost 2 years (~55000 monitor-days, or ~14 times mine) doesn't seem unreasonable. Mine also ran faster per day (1-3 days/second vs 1-3 seconds/day for yours - possibly you have more data points per day).
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@louislam commented on GitHub (Oct 21, 2025):

So after 10 Hours sitting still at 0% (even though half the Monitors were processed), that's normal to you ?

Unfortunately I had to restart from Scratch 😞. I tried to disable Automatic Reboots after Fedora Updates (since sometimes DNF Triggers it), but then I restarted one Service which actually restarted the entire System.

So there we go again 🤣 ... 2 Hours in now and sitting at:

Oct 21 17:42:47 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:47Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-19 [0.00%][7/87]
Oct 21 17:42:48 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:48Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-20 [0.00%][7/87]
Oct 21 17:42:49 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:49Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-21 [0.00%][7/87]
Oct 21 17:42:50 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:50Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-22 [0.00%][7/87]

In case you dont need the history for all monitors, you can start Uptime Kuma 1.23.x using your backup, delete heartbeat data for some monitors, and upgrade to v2 again.

@louislam commented on GitHub (Oct 21, 2025): > So after 10 Hours sitting still at 0% (even though half the Monitors were processed), that's normal to you ? > > Unfortunately I had to restart from Scratch 😞. I tried to disable Automatic Reboots after Fedora Updates (since sometimes DNF Triggers it), but then I restarted one Service which actually restarted the entire System. > > So there we go again 🤣 ... 2 Hours in now and sitting at: > > ``` > Oct 21 17:42:47 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:47Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-19 [0.00%][7/87] > Oct 21 17:42:48 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:48Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-20 [0.00%][7/87] > Oct 21 17:42:49 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:49Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-21 [0.00%][7/87] > Oct 21 17:42:50 podmanserver uptime-kuma-server[4853]: 2025-10-21T15:42:50Z [DB] INFO: [DON'T STOP] Migrating monitor data 8 - 2025-01-22 [0.00%][7/87] > ``` In case you dont need the history for all monitors, you can start Uptime Kuma 1.23.x using your backup, delete heartbeat data for some monitors, and upgrade to v2 again.
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@github-actions[bot] commented on GitHub (Dec 20, 2025):

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.

@github-actions[bot] commented on GitHub (Dec 20, 2025): We are clearing up our old `help`-issues and your issue has been open for 60 days with no activity. If no comment is made and the stale label is not removed, this issue will be closed in 7 days.
deekerman commented 2026-02-28 03:59:19 -05:00
Author
Owner
Copy link

@Harry-Chen commented on GitHub (Dec 22, 2025):

The 0.00% is actually a rounding issue in progress calculation:

github.com/louislam/uptime-kuma@eb0b6cdb09/server/database.js (L828-L876)

The logic can be simplified as:

let part = 100 / monitors.length;
let progressPercent = 0;
for (monitor of monitors) {
  doSomething();
  progressPercent += Math.round(part / dates.length * 100) / 100;
  console.log(progressPercent);
}

The problem is, part / dates.length * 100 can be really small if you have a long monitors / dates. So Math.round just returns 0.

@Harry-Chen commented on GitHub (Dec 22, 2025): The `0.00%` is actually a rounding issue in progress calculation: https://github.com/louislam/uptime-kuma/blob/eb0b6cdb09024c0941e07c8c10b094a0be439ae4/server/database.js#L828-L876 The logic can be simplified as: ```javascript let part = 100 / monitors.length; let progressPercent = 0; for (monitor of monitors) { doSomething(); progressPercent += Math.round(part / dates.length * 100) / 100; console.log(progressPercent); } ``` The problem is, `part / dates.length * 100` can be really small if you have a long `monitors` / `dates`. So `Math.round` just returns 0.
deekerman commented 2026-02-28 03:59:20 -05:00
Author
Owner
Copy link

@CommanderStorm commented on GitHub (Dec 22, 2025):

yea, showing the absolute values in the log is likely good for long monitors / dates. Would you like to do such a PR?

@CommanderStorm commented on GitHub (Dec 22, 2025): yea, showing the absolute values in the log is likely good for long `monitors` / `dates`. Would you like to do such a PR?
deekerman commented 2026-02-28 03:59:20 -05:00
Author
Owner
Copy link

@Harry-Chen commented on GitHub (Dec 22, 2025):

@CommanderStorm Please see #6516.

@Harry-Chen commented on GitHub (Dec 22, 2025): @CommanderStorm Please see #6516.
deekerman commented 2026-02-28 03:59:20 -05:00
Author
Owner
Copy link

@CommanderStorm commented on GitHub (Dec 22, 2025):

thanks

@CommanderStorm commented on GitHub (Dec 22, 2025): thanks
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
master
npm-update
3.0.X
dev-better-auth
copilot/remove-password-complexity-requirements
2.2.X
copilot/sub-pr-6355
1.23.X
api-via-socketio-client
2.1.3
2.1.2
2.1.1
2.1.0
2.1.0-beta.3
2.1.0-beta.2
2.1.0-beta.1
2.1.0-beta.0
2.0.2
2.0.1
1.23.17
2.0.0
2.0.0-beta.4
2.0.0-beta.3
2.0.0-beta.2
2.0.0-beta.2-temp
2.0.0-beta.1
1.23.16
2.0.0-beta.0
1.23.15
1.23.14
1.23.13
1.23.12
1.23.11
1.23.10
1.23.9
1.23.8
1.23.7
1.23.6
1.23.5
1.23.5-beta.0
1.23.4
1.23.3
1.23.2
1.23.1
1.23.0
1.23.0-beta.1
1.23.0-beta.0
1.22.1
1.22.0
1.22.0-beta.0
1.21.3
1.21.2
1.21.2-beta.0
1.21.1
1.21.0
1.21.0-beta.1
1.21.0-beta.0
1.20.2
1.20.1
1.20.0
1.20.0-beta.0
1.19.6
1.19.5
1.19.4
1.19.3
1.19.2
1.19.1
1.19.0
1.19.0-beta.2
1.19.0-beta.1
1.19.0-beta.0
1.18.5
1.18.4
1.18.3
1.18.2
1.18.1
1.18.0
1.18.0-beta.0
1.17.1
1.17.0
1.17.0-beta.1
1.17.0-beta.0
1.16.1
1.16.0
1.16.0-beta.0
1.15.1
1.15.0
1.15.0-beta.1
1.14.1
1.15.0-beta.0
1.14.0
1.14.0-beta.2
1.13.2
1.14.0-beta.1
1.14.0-beta.0
1.13.1
1.13.0
1.13.0-beta.2
1.13.0-beta.1
1.13.0-beta.0
1.12.1
1.12.0
1.11.4
1.11.3
1.11.2
1.11.1
1.11.0
1.10.2
1.10.1
1.10.0
1.9.2
1.9.1
1.9.0
1.8.0
1.7.3
1.7.2
1.7.1
1.7.0
1.6.3
1.6.2
1.6.1
1.6.0
1.5.3
1.5.2
1.5.1
1.5.0
1.3.2
1.3.1
1.3.0
1.2.0
1.1.0
1.0.10
1.0.9
1.0.8
1.0.7
1.0.6
1.0.5
1.0.4
1.0.3
1.0.2
1.0.1
1.0.0
Labels
Clear labels   
A:accessibility

   
A:api

   
A:cert-expiry

   
A:core

   
A:dashboard

   
A:deployment

   
A:documentation

   
A:domain expiry

   
A:incidents

   
A:maintenance

   
A:metrics

   
A:monitor

   
A:notifications

   
A:reports

   
A:settings

   
A:status-page

   
A:ui/ux

   
A:user-management

   
Stale

   
ai-slop

   
blocked

   
blocked-upstream

   
bug

   
cannot-reproduce

   
dependencies

   
discussion

   
duplicate

   
feature-request

   
feature-request

   
good first issue

   
hacktoberfest

   
help

   
help wanted

   
house keeping

   
invalid

   
invalid-format

   
invalid-format

   
question

   
releaseblocker 🚨

   
security

   
spam

   
type:enhance-existing

   
type:new

   
wontfix
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4349
No description provided.