louislam/uptime-kuma

Password Reset via CLI does not work on Embedded MariaDB

Open

Aperta il 28 feb 2025

Vedi su GitHub
 (11 commenti) (0 reazioni) (0 assegnatari)JavaScript (86.760 star) (7844 fork)batch import
A:deploymentbuggood first issue

Descrizione

📑 I have found these related issues/pull requests

Could not find anything related to this topic for 2.0.0-beta.1

🛡️ Security Policy

Description

When trying to run the command npm run reset-password It starts the tool but I am never prompted to provide a new password. Only happens with Embedded MariaDB. SQLite it runs as expected.

👟 Reproduction steps

  • Start Uptime Kuma Container
  • Run docker exec -it <container name> bash
  • Run npm run reset-password

👀 Expected behavior

Prompt to enter a new password and then confirm the password.

😓 Actual Behavior

The log output belows shows the repeated output.

🐻 Uptime-Kuma Version

2.0.0-beta.1

💻 Operating System and Arch

Ubuntu Desktop 24.04

🌐 Browser

Edge

🖥️ Deployment Environment

  • Runtime: Docker Engine Community 28.0.1
  • Database: Embedded MariaDB
  • Filesystem used to store the database on: Ext 3/ext4 filesystem in Hyper-V VM
  • number of monitors: 0

📝 Relevant log output

root@d1438a76604b:/app# npm run reset-password

> uptime-kuma@2.0.0-beta.1 reset-password
> node extra/reset-password.js

== Uptime Kuma Reset Password Tool ==
Connecting the database
2025-02-28T20:41:32+00:00 [SERVER] INFO: Data Dir: ./data/
2025-02-28T20:41:32+00:00 [DB] INFO: Database Type: embedded-mariadb
2025-02-28T20:41:32+00:00 [MARIADB] INFO: Starting Embedded MariaDB
2025-02-28T20:41:32+00:00 [MARIADB] INFO: 2025-02-28 20:41:32 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision  as process 335

2025-02-28T20:41:32+00:00 [MARIADB] INFO: 2025-02-28 20:41:32 0 [ERROR] mariadbd: Can't lock aria control file '/app/data/mariadb/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds

2025-02-28T20:41:33+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:34+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:35+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:36+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:37+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:38+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:39+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:40+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:41+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:42+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:43+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:44+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:45+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:46+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:47+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:48+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:49+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:50+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:51+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:52+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:53+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:54+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:55+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:56+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:57+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:58+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:41:59+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:42:00+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:42:01+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:42:02+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [ERROR] mariadbd: Got error 'Could not get an exclusive lock; file is probably in use by another process' when trying to use aria control file '/app/data/mariadb/aria_log_control'
2025-02-28 20:42:02 0 [ERROR] Plugin 'Aria' registration as a STORAGE ENGINE failed.

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] InnoDB: Compressed tables use zlib 1.2.13

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] InnoDB: Number of transaction pools: 1

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
2025-02-28 20:42:02 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 11
2025-02-28 20:42:02 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] InnoDB: Completed initialization of buffer pool

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [ERROR] InnoDB: Unable to lock ./ibdata1 error: 11
2025-02-28 20:42:02 0 [Note] InnoDB: Check that you do not already have another mariadbd process using the same InnoDB data or log files.
2025-02-28 20:42:02 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error
2025-02-28 20:42:02 0 [Note] InnoDB: Starting shutdown...

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed.

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] Plugin 'FEEDBACK' is disabled.
2025-02-28 20:42:02 0 [ERROR] Could not open mysql.plugin table: "Unknown storage engine 'Aria'". Some plugins may be not loaded
2025-02-28 20:42:02 0 [ERROR] Failed to initialize plugins.
2025-02-28 20:42:02 0 [ERROR] Aborting

2025-02-28T20:42:02+00:00 [MARIADB] INFO: Stopped Embedded MariaDB: 1
2025-02-28T20:42:02+00:00 [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user
2025-02-28T20:42:02+00:00 [MARIADB] INFO: Starting Embedded MariaDB
2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision  as process 338

2025-02-28T20:42:02+00:00 [MARIADB] INFO: 2025-02-28 20:42:02 0 [ERROR] mariadbd: Can't lock aria control file '/app/data/mariadb/aria_log_control' for exclusive use, error: 11. Will retry for 30 seconds

2025-02-28T20:42:03+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:42:04+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2025-02-28T20:42:05+00:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
^C
root@d1438a76604b:/app#

Guida contributor

Tech stack
javascriptnodejssqldocker
Dominio
backendclidatabase
Tipo issue
bug
DifficoltàQuanto dovrebbe essere impegnativa per un nuovo contributor.
3
Tempo stimatoTempo stimato per completare e verificare uno scope piccolo.
half day
Stato attivitàQuanto è probabile che la issue sia ancora attiva e reviewable.
fresh
ChiarezzaQuanto chiaramente la issue descrive problema, scope e risultato atteso.
clear
Prerequisiti
Basic understanding of DockerFamiliarity with Node.js CLI toolsKnowledge of Uptime Kuma architectureUnderstanding of file locking
Adatta ai principiantiQuanto la issue è adatta a contributor alla prima esperienza.
55
Direzione di ricerca
The issue is that the password reset script (extra/reset password.js) tries to start an embedded MariaDB instance while the main Uptime Kuma container is already running with the same database files, causing a file lock conflict. Investigate the script's database initialization and consider stopping the main process or modifying the script to connect to the existing database.