uptime-kuma: SQLITE_IOERR: disk I/O error on update to 1.23.7

⚠️ Please verify that this bug has NOT been raised before.

  • I checked and didn’t find similar issue

πŸ›‘οΈ Security Policy

Description

Hello

I’v upgrade uptime-kuma 1.23.3 to 1.23.4 and when my pod starting I have this errors logs.

I have the same issue in 1.23.4 -> https://github.com/louislam/uptime-kuma/issues/4039

πŸ‘Ÿ Reproduction steps

Upgrade 1.23.3 to 1.23.7 or 1.23.6

πŸ‘€ Expected behavior

Uptime-kuma starting

πŸ˜“ Actual Behavior

Uptime-kuma won’t start

🐻 Uptime-Kuma Version

1.23.7

πŸ’» Operating System and Arch

unknown

🌐 Browser

Google Chrome Version 119.0.6045.123 (Build officiel) (64 bits)

πŸ‹ Docker Version

unknown

🟩 NodeJS Version

18.18.2

πŸ“ Relevant log output

==> Performing startup jobs and maintenance tasks
==> Starting application with user 0 group 0
Welcome to Uptime Kuma
Your Node.js version: 18.18.2
2023-11-27T08:56:23Z [SERVER] INFO: Welcome to Uptime Kuma
2023-11-27T08:56:23Z [SERVER] INFO: Node Env: production
2023-11-27T08:56:23Z [SERVER] INFO: Inside Container: true
2023-11-27T08:56:23Z [SERVER] INFO: Importing Node libraries
2023-11-27T08:56:23Z [SERVER] INFO: Importing 3rd-party libraries
2023-11-27T08:56:26Z [SERVER] INFO: Creating express and socket.io instance
2023-11-27T08:56:26Z [SERVER] INFO: Server Type: HTTP
2023-11-27T08:56:26Z [SERVER] INFO: Importing this project modules
2023-11-27T08:56:26Z [NOTIFICATION] INFO: Prepare Notification Providers
2023-11-27T08:56:26Z [SERVER] INFO: Version: 1.23.7
2023-11-27T08:56:26Z [DB] INFO: Data Dir: ./data/
2023-11-27T08:56:26Z [SERVER] INFO: Connecting to the Database
2023-11-27T08:56:26Z [DB] INFO: SQLite config:
[ { journal_mode: 'wal' } ]
[ { cache_size: -12000 } ]
2023-11-27T08:56:26Z [DB] INFO: SQLite Version: 3.41.1
2023-11-27T08:56:26Z [SERVER] INFO: Connected
2023-11-27T08:56:26Z [DB] INFO: Your database version: 10
2023-11-27T08:56:26Z [DB] INFO: Latest database version: 10
2023-11-27T08:56:26Z [DB] INFO: Database patch not needed
2023-11-27T08:56:26Z [DB] INFO: Database Patch 2.0 Process
2023-11-27T08:56:26Z [DB] INFO: patch-fix-kafka-producer-booleans.sql is not patched
2023-11-27T08:56:26Z [DB] INFO: patch-fix-kafka-producer-booleans.sql is patching
2023-11-27T08:56:26Z [DB] INFO: Closing the database
2023-11-27T08:56:28Z [DB] INFO: SQLite closed
[Error: ALTER TABLE monitor
    DROP COLUMN kafka_producer_allow_auto_topic_creation_old - SQLITE_IOERR: disk I/O error] {
  errno: 10,
  code: 'SQLITE_IOERR'
}
2023-11-27T08:56:28Z [DB] ERROR: Start Uptime-Kuma failed due to issue patching the database
2023-11-27T08:56:28Z [DB] ERROR: Please submit the bug report if you still encounter the problem after restart: https://github.com/louislam/uptime-kuma/issues

About this issue

  • Original URL
  • State: closed
  • Created 7 months ago
  • Comments: 15 (4 by maintainers)

Most upvoted comments

@willthong I am not a kuma user, I came from Google while searching SQLITE_IOERR.

Sometimes you may just make a copy of the database file itself, I mean on the same disk. I learned that disk fragments could lead to SQLITE_IOERR, making a copy of the database file will re-allocate data to the same cluster, see here.