What type of hardware are you using: Old laptop or computer
What YunoHost version are you running: 12.1.14
What app is this about: Uptime Kuma
Describe your issue
After update to 2.0.0~ynh3 the service failed to start
Share relevant logs or error messages
Aug 22 12:12:00 systemd[1]: uptime-kuma.service: Main process exited, code=exited, status=1/FAILURE
Aug 22 12:12:00 systemd[1]: uptime-kuma.service: Failed with result 'exit-code'.
Aug 22 12:12:00 systemd[1]: uptime-kuma.service: Consumed 2.010s CPU time.
Aug 22 12:12:00 systemd[1]: uptime-kuma.service: Scheduled restart job, restart counter is at 4.
Aug 22 12:12:00 systemd[1]: Stopped uptime-kuma.service - Uptime Kuma: monitoring tool.
Aug 22 12:12:00 systemd[1]: uptime-kuma.service: Consumed 2.010s CPU time.
Aug 22 12:12:00 systemd[1]: Started uptime-kuma.service - Uptime Kuma: monitoring tool.
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Main process exited, code=exited, status=1/FAILURE
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Failed with result 'exit-code'.
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Consumed 2.012s CPU time.
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Scheduled restart job, restart counter is at 5.
Aug 22 12:12:02 systemd[1]: Stopped uptime-kuma.service - Uptime Kuma: monitoring tool.
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Consumed 2.012s CPU time.
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Start request repeated too quickly.
Aug 22 12:12:02 systemd[1]: uptime-kuma.service: Failed with result 'exit-code'.
Aug 22 12:12:02 systemd[1]: Failed to start uptime-kuma.service - Uptime Kuma: monitoring tool.
Welcome to Uptime Kuma
Your Node.js version: 22.18.0
e[36m2025-08-22T12:12:01+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Env: production
e[36m2025-08-22T12:12:01+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Uptime Kuma Version: 2.0.0-beta.3
e[36m2025-08-22T12:12:01+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Loading modules
e[36m2025-08-22T12:12:02+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Creating express and socket.io instance
e[36m2025-08-22T12:12:02+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Server Type: HTTP
e[36m2025-08-22T12:12:02+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Data Dir: ./data/
e[36m2025-08-22T12:12:02+02:00e[0m [e[38;5;117mDBe[0m] e[36mINFO:e[0m Database Type: sqlite
e[36m2025-08-22T12:12:02+02:00e[0m [e[32mSERVERe[0m] e[36mINFO:e[0m Connected to the database
e[36m2025-08-22T12:12:02+02:00e[0m [e[38;5;117mDBe[0m] e[33mWARN:e[0m Aggregate table migration is already in progress, or it was interrupted
e[36m2025-08-22T12:12:02+02:00e[0m [e[38;5;117mDBe[0m] e[31mERROR:e[0m e[31mDatabase migration failede[0m
e[36m2025-08-22T12:12:02+02:00e[0m [e[32mSERVERe[0m] e[31mERROR:e[0m e[31mFailed to prepare your database: Aggregate table migration is already in progresse[0m
Verlauf