search

louislam / uptime-kuma

A fancy self-hosted monitoring tool
https://uptime.kuma.pet
MIT License
58.39k stars 5.27k forks source link

v2 beta - embedded mariadb fails to initialise #5279

Open high3eam opened 3 days ago

high3eam commented 3 days ago

📑 I have found these related issues/pull requests

none

🛡️ Security Policy

Description

Tried to create a new docker based uptime kuma instance with embedded mariadb, but mariadb cannot initialise properly and goes into start and stop loop.

👟 Reproduction steps

Create a new uptime kuma instance with docker using this docker compose file:

services:
    uptime-kuma:
        image: louislam/uptime-kuma:beta
        container_name: uptime-kuma
        volumes:
          - ./uptime-kuma-data:/app/data
        ports:
          - 3001:3001
        restart: unless-stopped

👀 Expected behavior

Uptime Kuma would finalise the initialisation of the embedded mariadb

😓 Actual Behavior

start and stop loop of mariadb

🐻 Uptime-Kuma Version

2.0.0-beta.0

💻 Operating System and Arch

Debian 12.7 amd64

🌐 Browser

Edge v130

🖥️ Deployment Environment

📝 Relevant log output

Docker compose log output (click to expand) ``` uptime-kuma | Welcome to Uptime Kuma uptime-kuma | Your Node.js version: 20.18.0 uptime-kuma | 2024-10-29T20:56:12Z [SERVER] INFO: Env: production uptime-kuma | 2024-10-29T20:56:13Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0 uptime-kuma | 2024-10-29T20:56:13Z [SERVER] INFO: Loading modules uptime-kuma | 2024-10-29T20:56:14Z [SERVER] INFO: Creating express and socket.io instance uptime-kuma | 2024-10-29T20:56:14Z [SERVER] INFO: Server Type: HTTP uptime-kuma | 2024-10-29T20:56:14Z [SERVER] INFO: Data Dir: ./data/ uptime-kuma | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json' uptime-kuma | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: Starting Setup Database on 3001 uptime-kuma | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: Open http://localhost:3001 in your browser uptime-kuma | 2024-10-29T20:56:14Z [SETUP-DATABASE] INFO: Waiting for user action... uptime-kuma | Request /setup-database-info uptime-kuma | Request /setup-database-info uptime-kuma | Request /setup-database-info uptime-kuma | Request /setup-database-info uptime-kuma | Request /setup-database-info uptime-kuma | Request /setup-database-info uptime-kuma | 2024-10-29T20:56:26Z [SETUP-DATABASE] INFO: Database is configured, close the setup-database server and start the main server now. uptime-kuma | 2024-10-29T20:56:26Z [SETUP-DATABASE] INFO: The setup-database server is closed uptime-kuma | 2024-10-29T20:56:26Z [DB] INFO: Database Type: embedded-mariadb uptime-kuma | 2024-10-29T20:56:26Z [MARIADB] INFO: Embedded MariaDB: /app/data/mariadb is not found, create one now. uptime-kuma | 2024-10-29T20:56:28Z [MARIADB] INFO: Embedded MariaDB: mysql_install_db done:Installing MariaDB/MySQL system tables in '/app/data/mariadb' ... uptime-kuma | OK uptime-kuma | uptime-kuma | To start mariadbd at boot time you have to copy uptime-kuma | support-files/mariadb.service to the right place for your system uptime-kuma | uptime-kuma | uptime-kuma | Two all-privilege accounts were created. uptime-kuma | One is root@localhost, it has no password, but you need to uptime-kuma | be system 'root' user to connect. Use, for example, sudo mysql uptime-kuma | The second is node@localhost, it has no password either, but uptime-kuma | you need to be the system 'node' user to connect. uptime-kuma | After connecting you can set the password, if you would need to be uptime-kuma | able to connect as any of these users with a password and without sudo uptime-kuma | uptime-kuma | See the MariaDB Knowledgebase at https://mariadb.com/kb uptime-kuma | uptime-kuma | You can start the MariaDB daemon with: uptime-kuma | cd '/usr' ; /usr/bin/mariadb-safe --datadir='/app/data/mariadb' uptime-kuma | uptime-kuma | You can test the MariaDB daemon with mysql-test-run.pl uptime-kuma | cd '/usr/share/mysql/mysql-test' ; perl mariadb-test-run.pl uptime-kuma | uptime-kuma | Please report any problems at https://mariadb.org/jira uptime-kuma | uptime-kuma | The latest information about MariaDB is available at https://mariadb.org/. uptime-kuma | uptime-kuma | Consider joining MariaDB's strong and vibrant community: uptime-kuma | https://mariadb.org/get-involved/ uptime-kuma | uptime-kuma | uptime-kuma | 2024-10-29T20:56:28Z [MARIADB] INFO: Embedded MariaDB: /app/data/run/mariadb is not found, create one now. uptime-kuma | 2024-10-29T20:56:28Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-29T20:56:28Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-10-29T20:56:28Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma | 2024-10-29T20:56:28Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Waiting for Embedded MariaDB to start... uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-29T20:56:29Z [MARIADB] INFO: Waiting for Embedded MariaDB to start... uptime-kuma | 2024-10-29T20:56:30Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 ```
c3p0vsr2d2 commented 3 days ago

same error on previous 2 or 3 nightlies. Sorry, was too lazy to report it.

louislam commented 3 days ago

Is it rootless image? If yes:

⚠️ If file permission is not set correctly, Uptime Kuma will run into startup issues. You should set the data directory to node:node (1001:1001) user.

c3p0vsr2d2 commented 3 days ago

I am not using rootless, but there was also this recent change to remove USER node from the docker build file. Will retry with 1001:1001 set.

c3p0vsr2d2 commented 3 days ago

2.0.0-beta.0 (not the rootless image) has same issue with embedded mariadb initialization. data directory set to root permissions Logs show:

2024-10-29T20:56:43-07:00 [MARIADB] INFO: Stopped Embedded MariaDB: 1
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Starting Embedded MariaDB
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
2024-10-29T20:56:43-07:00 [MARIADB] INFO: Waiting for Embedded MariaDB to start...
...
louislam commented 3 days ago

@high3eam @c3p0vsr2d2 I just enabled MariaDB log to console. You could try the nightly2 image.

high3eam commented 3 days ago

@louislam I get this log output with nightly2 (non-rootless):

Nightly2 log ``` uptime-kuma | Welcome to Uptime Kuma uptime-kuma | Your Node.js version: 20.18.0 uptime-kuma | 2024-10-30T08:53:01Z [SERVER] INFO: Env: production uptime-kuma | 2024-10-30T08:53:02Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0-nightly-20241030074209 uptime-kuma | 2024-10-30T08:53:02Z [SERVER] INFO: Loading modules uptime-kuma | 2024-10-30T08:53:03Z [SERVER] INFO: Creating express and socket.io instance uptime-kuma | 2024-10-30T08:53:03Z [SERVER] INFO: Server Type: HTTP uptime-kuma | 2024-10-30T08:53:03Z [SERVER] INFO: Data Dir: ./data/ uptime-kuma | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json' uptime-kuma | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: Starting Setup Database on 3001 uptime-kuma | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: Open http://localhost:3001 in your browser uptime-kuma | 2024-10-30T08:53:03Z [SETUP-DATABASE] INFO: Waiting for user action... uptime-kuma | Request /setup-database-info uptime-kuma | 2024-10-30T08:53:14Z [SETUP-DATABASE] INFO: Database is configured, close the setup-database server and start the main server now. uptime-kuma | 2024-10-30T08:53:14Z [SETUP-DATABASE] INFO: The setup-database server is closed uptime-kuma | 2024-10-30T08:53:14Z [DB] INFO: Database Type: embedded-mariadb uptime-kuma | 2024-10-30T08:53:14Z [MARIADB] INFO: Embedded MariaDB: /app/data/mariadb is not found, create one now. uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: Embedded MariaDB: mysql_install_db done:Installing MariaDB/MySQL system tables in '/app/data/mariadb' ... uptime-kuma | OK uptime-kuma | uptime-kuma | To start mariadbd at boot time you have to copy uptime-kuma | support-files/mariadb.service to the right place for your system uptime-kuma | uptime-kuma | uptime-kuma | Two all-privilege accounts were created. uptime-kuma | One is root@localhost, it has no password, but you need to uptime-kuma | be system 'root' user to connect. Use, for example, sudo mysql uptime-kuma | The second is node@localhost, it has no password either, but uptime-kuma | you need to be the system 'node' user to connect. uptime-kuma | After connecting you can set the password, if you would need to be uptime-kuma | able to connect as any of these users with a password and without sudo uptime-kuma | uptime-kuma | See the MariaDB Knowledgebase at https://mariadb.com/kb uptime-kuma | uptime-kuma | You can start the MariaDB daemon with: uptime-kuma | cd '/usr' ; /usr/bin/mariadb-safe --datadir='/app/data/mariadb' uptime-kuma | uptime-kuma | You can test the MariaDB daemon with mysql-test-run.pl uptime-kuma | cd '/usr/share/mysql/mysql-test' ; perl mariadb-test-run.pl uptime-kuma | uptime-kuma | Please report any problems at https://mariadb.org/jira uptime-kuma | uptime-kuma | The latest information about MariaDB is available at https://mariadb.org/. uptime-kuma | uptime-kuma | Consider joining MariaDB's strong and vibrant community: uptime-kuma | https://mariadb.org/get-involved/ uptime-kuma | uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: Embedded MariaDB: /app/data/run/mariadb is not found, create one now. uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: mariadbd: Can't create file '/app/data/mariadb-error.log' (errno: 13 "Permission denied") uptime-kuma | 2024-10-30 8:53:15 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 86 uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: Number of transaction pools: 1 uptime-kuma | 2024-10-30 8:53:15 0 [Note] InnoDB: Using SSE4.2 crc32 instructions uptime-kuma | 2024-10-30 8:53:15 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95 uptime-kuma | 2024-10-30 8:53:15 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: Completed initialization of buffer pool uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: End of log at LSN=46996 uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: 128 rollback segments are active. uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: log sequence number 46996; transaction id 14 uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] Plugin 'FEEDBACK' is disabled. uptime-kuma | 2024-10-30 8:53:15 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] InnoDB: Buffer pool(s) load completed at 241030 8:53:15 uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [Note] Server socket created on IP: '127.0.0.1'. uptime-kuma | uptime-kuma | 2024-10-30T08:53:15Z [MARIADB] INFO: 2024-10-30 8:53:15 0 [ERROR] Can't start server : Bind on unix socket: Permission denied uptime-kuma | 2024-10-30 8:53:15 0 [ERROR] Do you already have another server running on socket: /app/data/run/mariadb/mysqld.sock ? uptime-kuma | 2024-10-30 8:53:15 0 [ERROR] Aborting uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: mariadbd: Can't create file '/app/data/mariadb-error.log' (errno: 13 "Permission denied") uptime-kuma | 2024-10-30 8:53:16 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 97 uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: Number of transaction pools: 1 uptime-kuma | 2024-10-30 8:53:16 0 [Note] InnoDB: Using SSE4.2 crc32 instructions uptime-kuma | 2024-10-30 8:53:16 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) uptime-kuma | 2024-10-30 8:53:16 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95 uptime-kuma | 2024-10-30 8:53:16 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: Completed initialization of buffer pool uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: End of log at LSN=46996 uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: 128 rollback segments are active. uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma | 2024-10-30 8:53:16 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: log sequence number 46996; transaction id 14 uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] Plugin 'FEEDBACK' is disabled. uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [Note] Server socket created on IP: '127.0.0.1'. uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: 2024-10-30 8:53:16 0 [ERROR] Can't start server : Bind on unix socket: Permission denied uptime-kuma | 2024-10-30 8:53:16 0 [ERROR] Do you already have another server running on socket: /app/data/run/mariadb/mysqld.sock ? uptime-kuma | 2024-10-30 8:53:16 0 [ERROR] Aborting uptime-kuma | uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-10-30T08:53:16Z [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user ```
louislam commented 3 days ago

[ERROR] Can't start server : Bind on unix socket: Permission denied

That is strange... Have to find a way to 100% reproduce this. I cannot reproduce it on my Linux machine.

N0Klu3 commented 2 days ago

I have this same issue, its a fresh install of Bookworm on RPi5, running Portainer. Compose: 

version: '3.3'
services:
  uptime-kuma:
    image: louislam/uptime-kuma:beta
    container_name: uptime-kuma
    volumes:
      - uptime-kuma:/app/data
    ports:
      - "3005:3001"
    restart: unless-stopped

volumes:
  uptime-kuma:

I get the exact same:

[MARIADB] INFO: Try to restart Embedded MariaDB as it is not stopped by user
[MARIADB] INFO: Starting Embedded MariaDB
[MARIADB] INFO: Waiting for Embedded MariaDB to start...

This was a fresh install of UK not a migration. My migration funnily did work just fine on another RPi5 system.

EDIT Ironically switching to beta-rootless gets it started and working fine with Embedded MariaDB Did the builds get switched by any chance? The notes say: Unable to use embedded MariaDB, you will need to use external MariaDB. But seems to work better than the 'beta' build?

This is using beta-rootless

2024-10-30T22:35:58Z [MARIADB] INFO: Embedded MariaDB: /app/data/run/mariadb is not found, create one now.
2024-10-30T22:35:58Z [MARIADB] INFO: Starting Embedded MariaDB
2024-10-30T22:35:58Z [MARIADB] INFO: Embedded MariaDB is ready for connections
2024-10-30T22:35:59Z [MARIADB] INFO: Embedded MariaDB started
2024-10-30T22:35:59Z [MARIADB] INFO: Creating basic tables for MariaDB
2024-10-30T22:36:00Z [MARIADB] INFO: Created basic tables for MariaDB
2024-10-30T22:36:00Z [SERVER] INFO: Connected to the database
2024-10-30T22:36:00Z [MIGRATION] INFO: Migration server is running on http://localhost:3001
2024-10-30T22:36:00Z [DB] INFO: Migrating Aggregate Table
2024-10-30T22:36:00Z [DB] INFO: Getting list of unique monitors
2024-10-30T22:36:00Z [DB] INFO: Clearing non-important heartbeats
2024-10-30T22:36:00Z [DB] INFO: No data to migrate

@louislam the above might help?

louislam commented 2 days ago

Bookworm on RPi5

@N0Klu3 Thanks for your hints! I just reproduce this issue on my Pi4 too.

N0Klu3 commented 2 days ago

Bookworm on RPi5

@N0Klu3 Thanks for your hints! I just reproduce this issue on my Pi4 too.

Can you confirm that beta-rootless should not have Embedded MariaDB working? As it seems to work just fine? Or maybe I just misunderstood the upgrade notes?

If it does work, why use non-root over root? Seems like if it works, running it as beta-rootless would be the better options no?

louislam commented 2 days ago

Bookworm on RPi5

@N0Klu3 Thanks for your hints! I just reproduce this issue on my Pi4 too.

Can you confirm that beta-rootless should not have Embedded MariaDB working? As it seems to work just fine? Or maybe I just misunderstood the upgrade notes?

If it does work, why use non-root over root? Seems like if it works, running it as beta-rootless would be the better options no?

Since I implemented this feature last year, the migration guide which I prepared recently was wrong. (I just updated) It should work on both the rootless and the root images.

Actually all issues are probably related to the file permissions. I try my best to handle it smoothly for everyone.

beta-rootless should have better security if you don't need Docker monitors via docker.sock.

N0Klu3 commented 2 days ago

Since I implemented this feature last year, the migration guide which I prepared recently was wrong. (I just updated) It should work on both the rootless and the root images.

Actually all issues probably the file permissions. I try my best to handle it smoothly for everyone.

beta-rootless should have better security if you don't need Docker monitors via docker.sock.

Perfect thank you! beta-rootless it is then :)

c3p0vsr2d2 commented 1 day ago

none of the latest root/rootless images work for me. tried both the latest nighly2 and beta tagged images. is there a v2 image that does not have this issue?

louislam commented 9 hours ago

It seems that I have fixed the issue in the nightly2, anyone would like to help to confirm that? Thanks. 

docker pull louislam/uptime-kuma:nightly2
docker pull louislam/uptime-kuma:nightly2-rootless
homelab-alpha commented 8 hours ago

It seems that I have fixed the issue in the nightly2, anyone would like to help to confirm that? Thanks.

docker pull louislam/uptime-kuma:nightly2
docker pull louislam/uptime-kuma:nightly2-rootless

I tested nightly2 and still have the problem with the built-in MariaDB.

👟 Reproduction steps:

Here is the docker-compose.yml file (click to expand)

```yml --- networks: uptime-kuma-beta_net: attachable: false internal: false external: false name: uptime-kuma-beta driver: bridge ipam: driver: default config: - subnet: 172.20.3.0/24 ip_range: 172.20.3.0/24 gateway: 172.20.3.1 driver_opts: com.docker.network.bridge.default_bridge: "false" com.docker.network.bridge.enable_icc: "true" com.docker.network.bridge.enable_ip_masquerade: "true" com.docker.network.bridge.host_binding_ipv4: "0.0.0.0" com.docker.network.bridge.name: "uptime-kuma" com.docker.network.driver.mtu: "1500" labels: com.uptime-kuma-beta.network.description: "is an isolated bridge network." services: uptime-kuma-beta_app: restart: unless-stopped logging: driver: "json-file" options: max-size: "1M" max-file: "2" stop_grace_period: 1m container_name: uptime-kuma-beta image: louislam/uptime-kuma:nightly2 pull_policy: if_not_present volumes: - /docker/uptime-kuma-beta/app:/app/data - /var/run/docker.sock:/var/run/docker.sock:ro - /usr/local/share/ca-certificates:/app/data/docker-tls environment: PUID: "1000" PGID: "1000" TZ: Europe/Amsterdam # NODE_EXTRA_CA_CERTS: /app/data/docker-tls/demo.cert # This is a demo certificate. domainname: status.local hostname: status networks: uptime-kuma-beta_net: ipv4_address: 172.20.3.3 ports: - "3001:3001/tcp" # HTTP - "3001:3001/udp" # HTTP security_opt: - no-new-privileges:true labels: com.docker.compose.project: "uptime-kuma-beta" com.uptime-kuma-beta.description: "is an self-hosted monitoring tool that allows you to monitor uptime, status, and notifications for various services and domains." healthcheck: disable: true ```

🐻 Uptime-Kuma Version Version: nightly2

💻 Operating System and Arch Ubuntu Server 24.04.1 LTS (GNU/Linux 6.8.0-48-generic x86_64)

🌐 Browser Brave version 1.71.121 (Chromium: 130.0.6723.91) (Official Build) (64-bit)

🖥️ Deployment Environment Runtime: Docker version 26.1.0, build 9714adc Runtime: docker-compose version 1.29.2, build unknown Runtime: Portainer Business Edition version 2.21.4 Database: MariaDB (embedded) Filesystem used for the database: Linux/ext4 on an SSD Number of monitors: 0

Relevant log output (click to expand)

```bash ┌──(homelab-alpha@test-server)-[/docker/uptime-kuma-beta] └─$sudo docker-compose up --remove-orphans Creating network "uptime-kuma-beta" with driver "bridge" Pulling uptime-kuma-beta_app (louislam/uptime-kuma:nightly2)... nightly2: Pulling from louislam/uptime-kuma a480a496ba95: Pull complete 07574ed847ca: Pull complete 2291004efc7a: Pull complete b991b65dcbd5: Pull complete 2816f5bc428c: Pull complete 759a9d6de00b: Pull complete c5c931bca37c: Pull complete 17a6f85699e8: Pull complete e21f8cdf23aa: Pull complete 57a18d7aff9b: Pull complete f3ce267d0ae9: Pull complete 9b65c38c4fbd: Pull complete 23079134dd94: Pull complete e6a053232f55: Pull complete e4105961c628: Pull complete Digest: sha256:88584b62bb2f543de161f31d0a323b508c09728731a8e483fd8c17212d8bdccd Status: Downloaded newer image for louislam/uptime-kuma:nightly2 Creating uptime-kuma-beta ... done Attaching to uptime-kuma-beta uptime-kuma-beta | Welcome to Uptime Kuma uptime-kuma-beta | Your Node.js version: 20.18.0 uptime-kuma-beta | 2024-11-02T12:06:50+01:00 [SERVER] INFO: Env: production uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0-nightly-20241102095533 uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SERVER] INFO: Loading modules uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SERVER] INFO: Creating express and socket.io instance uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SERVER] INFO: Server Type: HTTP uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SERVER] INFO: Data Dir: ./data/ uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json' uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SETUP-DATABASE] INFO: Starting Setup Database on 3001 uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SETUP-DATABASE] INFO: Open http://localhost:3001 in your browser uptime-kuma-beta | 2024-11-02T12:06:51+01:00 [SETUP-DATABASE] INFO: Waiting for user action... uptime-kuma-beta | Request /setup-database-info uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [SETUP-DATABASE] INFO: Database is configured, close the setup-database server and start the main server now. uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [SETUP-DATABASE] INFO: The setup-database server is closed uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [DB] INFO: Database Type: embedded-mariadb uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 18 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be created! uptime-kuma-beta | 2024-11-02 12:07:34 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Number of transaction pools: 1 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 2 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Completed initialization of buffer pool uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Setting file './ibdata1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: File './ibdata1' size is now 12.000MiB. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Doublewrite buffer not found: creating new uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: 128 rollback segments are active. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] InnoDB: log sequence number 0; transaction id 3 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] Plugin 'FEEDBACK' is disabled. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [Note] Server socket created on IP: '127.0.0.1'. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:34+01:00 [MARIADB] INFO: 2024-11-02 12:07:34 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist uptime-kuma-beta | 2024-11-02 12:07:34 0 [ERROR] Aborting uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 34 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Number of transaction pools: 1 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions uptime-kuma-beta | 2024-11-02 12:07:35 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 0 uptime-kuma-beta | 2024-11-02 12:07:35 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Completed initialization of buffer pool uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Buffered log writes (block size=512 bytes) uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: End of log at LSN=36397 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: 128 rollback segments are active. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma-beta | 2024-11-02 12:07:35 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: log sequence number 36397; transaction id 4 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool uptime-kuma-beta | 2024-11-02 12:07:35 0 [Note] Plugin 'FEEDBACK' is disabled. uptime-kuma-beta | 2024-11-02 12:07:35 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] InnoDB: Buffer pool(s) load completed at 241102 12:07:35 uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [Note] Server socket created on IP: '127.0.0.1'. uptime-kuma-beta | uptime-kuma-beta | 2024-11-02T12:07:35+01:00 [MARIADB] INFO: 2024-11-02 12:07:35 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist uptime-kuma-beta | 2024-11-02 12:07:35 0 [ERROR] Aborting uptime-kuma-beta | ^CGracefully stopping... (press Ctrl+C again to force) Stopping uptime-kuma-beta ... done ┌──(homelab-alpha@test-server)-[/docker/uptime-kuma-beta] └─$ sudo docker-compose down Removing uptime-kuma-beta ... done Removing network uptime-kuma-beta ```

high3eam commented 7 hours ago

The error changed but I also still have an issue with the embedded mariadb after repulling nightly2 on my Debian 12 amd64 host to try a fresh install:

Docker Compose Log ``` uptime-kuma | Welcome to Uptime Kuma uptime-kuma | Your Node.js version: 20.18.0 uptime-kuma | 2024-11-02T12:30:26Z [SERVER] INFO: Env: production uptime-kuma | 2024-11-02T12:30:27Z [SERVER] INFO: Uptime Kuma Version: 2.0.0-beta.0-nightly-20241102095533 uptime-kuma | 2024-11-02T12:30:27Z [SERVER] INFO: Loading modules uptime-kuma | 2024-11-02T12:30:27Z [SERVER] INFO: Creating express and socket.io instance uptime-kuma | 2024-11-02T12:30:27Z [SERVER] INFO: Server Type: HTTP uptime-kuma | 2024-11-02T12:30:27Z [SERVER] INFO: Data Dir: ./data/ uptime-kuma | 2024-11-02T12:30:27Z [SETUP-DATABASE] INFO: db-config.json is not found or invalid: ENOENT: no such file or directory, open 'data/db-config.json' uptime-kuma | 2024-11-02T12:30:28Z [SETUP-DATABASE] INFO: Starting Setup Database on 3001 uptime-kuma | 2024-11-02T12:30:28Z [SETUP-DATABASE] INFO: Open http://localhost:3001 in your browser uptime-kuma | 2024-11-02T12:30:28Z [SETUP-DATABASE] INFO: Waiting for user action... uptime-kuma | Request /setup-database-info uptime-kuma | 2024-11-02T12:30:41Z [SETUP-DATABASE] INFO: Database is configured, close the setup-database server and start the main server now. uptime-kuma | 2024-11-02T12:30:41Z [SETUP-DATABASE] INFO: The setup-database server is closed uptime-kuma | 2024-11-02T12:30:41Z [DB] INFO: Database Type: embedded-mariadb uptime-kuma | 2024-11-02T12:30:41Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-11-02T12:30:41Z [MARIADB] INFO: 2024-11-02 12:30:41 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 30 uptime-kuma | uptime-kuma | 2024-11-02T12:30:41Z [MARIADB] INFO: 2024-11-02 12:30:41 0 [Note] InnoDB: The first data file './ibdata1' did not exist. A new tablespace will be created! uptime-kuma | 2024-11-02 12:30:41 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 uptime-kuma | uptime-kuma | 2024-11-02T12:30:41Z [MARIADB] INFO: 2024-11-02 12:30:41 0 [Note] InnoDB: Number of transaction pools: 1 uptime-kuma | 2024-11-02 12:30:41 0 [Note] InnoDB: Using SSE4.2 crc32 instructions uptime-kuma | uptime-kuma | 2024-11-02T12:30:41Z [MARIADB] INFO: 2024-11-02 12:30:41 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) uptime-kuma | 2024-11-02 12:30:41 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95 uptime-kuma | 2024-11-02 12:30:41 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF uptime-kuma | uptime-kuma | 2024-11-02T12:30:41Z [MARIADB] INFO: 2024-11-02 12:30:41 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Completed initialization of buffer pool uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Setting file './ibdata1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma | 2024-11-02 12:30:42 0 [Note] InnoDB: File './ibdata1' size is now 12.000MiB. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Doublewrite buffer not found: creating new uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: 128 rollback segments are active. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma | 2024-11-02 12:30:42 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: log sequence number 0; transaction id 3 uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] Plugin 'FEEDBACK' is disabled. uptime-kuma | 2024-11-02 12:30:42 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded uptime-kuma | 2024-11-02 12:30:42 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] Server socket created on IP: '127.0.0.1'. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist uptime-kuma | 2024-11-02 12:30:42 0 [ERROR] Aborting uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] ERROR: Try to restart Embedded MariaDB as it is not stopped by user uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: Starting Embedded MariaDB uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] Starting MariaDB 10.11.6-MariaDB-0+deb12u1 source revision as process 49 uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Compressed tables use zlib 1.2.13 uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Number of transaction pools: 1 uptime-kuma | 2024-11-02 12:30:42 0 [Note] InnoDB: Using SSE4.2 crc32 instructions uptime-kuma | 2024-11-02 12:30:42 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts) uptime-kuma | 2024-11-02 12:30:42 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 95 uptime-kuma | 2024-11-02 12:30:42 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Completed initialization of buffer pool uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes) uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: End of log at LSN=36397 uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: 128 rollback segments are active. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ... uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: log sequence number 36397; transaction id 4 uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Loading buffer pool(s) from /app/data/mariadb/ib_buffer_pool uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] Plugin 'FEEDBACK' is disabled. uptime-kuma | 2024-11-02 12:30:42 0 [ERROR] Could not open mysql.plugin table: "Table 'mysql.plugin' doesn't exist". Some plugins may be not loaded uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] InnoDB: Buffer pool(s) load completed at 241102 12:30:42 uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [ERROR] Can't open and lock privilege tables: Table 'mysql.servers' doesn't exist uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [Note] Server socket created on IP: '127.0.0.1'. uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: 2024-11-02 12:30:42 0 [ERROR] Fatal error: Can't open and lock privilege tables: Table 'mysql.db' doesn't exist uptime-kuma | 2024-11-02 12:30:42 0 [ERROR] Aborting uptime-kuma | uptime-kuma | 2024-11-02T12:30:42Z [MARIADB] INFO: Stopped Embedded MariaDB: 1 ```
louislam commented 2 hours ago

@homelab-alpha @high3eam Thanks, I also could reproduce on my another linux.