louislam / uptime-kuma

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

'SQLITE_CORRUPT' #4909

Open diegoavitorino opened 3 months ago

diegoavitorino commented 3 months ago

πŸ“‘ I have found these related issues/pull requests

N/a

πŸ›‘οΈ Security Policy

Description

at Timeout.safeBeat [as _onTimeout] (/app/server/model/monitor.js:1034:25) 2024-07-05T10:19:15-03:00 [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues 2024-07-05T10:19:15-03:00 [MONITOR] INFO: Try to restart the monitor Trace: [Error: insert into heartbeat (down_count, duration, important, monitor_id, msg, ping, status, time) values (0, 21, false, 40, '200 - OK', 106, 1, '2024-07-05 13:19:14.170') - SQLITE_CORRUPT: database disk image is malformed] { errno: 11, code: 'SQLITE_CORRUPT'

πŸ‘Ÿ Reproduction steps

at Timeout.safeBeat [as _onTimeout] (/app/server/model/monitor.js:1034:25) 2024-07-05T10:19:15-03:00 [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues 2024-07-05T10:19:15-03:00 [MONITOR] INFO: Try to restart the monitor Trace: [Error: insert into heartbeat (down_count, duration, important, monitor_id, msg, ping, status, time) values (0, 21, false, 40, '200 - OK', 106, 1, '2024-07-05 13:19:14.170') - SQLITE_CORRUPT: database disk image is malformed] { errno: 11, code: 'SQLITE_CORRUPT'

πŸ‘€ Expected behavior

'SQLITE_CORRUPT'

πŸ˜“ Actual Behavior

Uptime error log

🐻 Uptime-Kuma Version

1.23.13

πŸ’» Operating System and Arch

Kubernetes

🌐 Browser

Google Chrome

πŸ–₯️ Deployment Environment

πŸ“ Relevant log output

No response

CommanderStorm commented 3 months ago

How did you deploy to kubernetes? What is the file system you use? (NFS is not compatible with SQLite3 due to bad locking)

There are a lot of issues that we already answered. Have you looked through the existing issues? For example https://github.com/louislam/uptime-kuma/issues/998 deployed with concurrent pods which is unsupported.

basrieter commented 1 month ago

We had the same issue while hosting it on Azure. The Azure persistent folder is a CIFS file share and that seem to cause corruption.