You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running beta-slim and the latest version of the LSIO mariadb image, I receive a SQL error about LIMIT not being supported in a subquery of IN/ALL/ANY/SUM. This appears to be when it's trying to purge old statistics, I think.
π Reproduction steps
Launch compose stack with external mariadb (included below) and watch the logs.
π Expected behavior
Not throw this error, sucessfully clean up db as desired.
π Actual Behavior
Logging throws various errors included below.
π» Uptime-Kuma Version
2.0.0-beta.0
π» Operating System and Arch
TrueNAS Scale ElectricEel-24.10.0
π Browser
Chrome 131.0.6778.109 (Official Build) (arm64)
π₯οΈ Deployment Environment
Runtime: Docker 27.1.1
Database: MariaDB External 10.11.11-R0-LS163
Filesystem used to store the database on: ZFS RAIDZ2 (local)
Trace: Error:
DELETE FROM heartbeat
WHERE monitor_id = 30
AND important = 0
AND time<DATE_ADD(NOW(), INTERVAL -24 HOUR)
AND id NOT IN (
SELECT id
FROM heartbeat
WHERE monitor_id = 30
ORDER BY time DESC
LIMIT 100
)
- This version of MariaDB doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery' at Packet.asError (/app/node_modules/mysql2/lib/packets/packet.js:738:17) at Query.execute (/app/node_modules/mysql2/lib/commands/command.js:29:26) at Connection.handlePacket (/app/node_modules/mysql2/lib/connection.js:481:34) at PacketParser.onPacket (/app/node_modules/mysql2/lib/connection.js:97:12) at PacketParser.executeStart (/app/node_modules/mysql2/lib/packet_parser.js:75:16) at Socket.<anonymous> (/app/node_modules/mysql2/lib/connection.js:104:25) at Socket.emit (node:events:519:28) at addChunk (node:internal/streams/readable:559:12) at readableAddChunkPushByteMode (node:internal/streams/readable:510:3) at Readable.push (node:internal/streams/readable:390:5) { code: 'ER_NOT_SUPPORTED_YET', errno: 1235, sqlState: '42000', sqlMessage: "This version of MariaDB doesn't yet support 'LIMIT & IN/ALL/ANY/SOME subquery'", sql: '\n' + ' DELETE FROM heartbeat\n' + ' WHERE monitor_id = 30\n' + ' AND important = 0\n' + ' AND time < DATE_ADD(NOW(), INTERVAL -24 HOUR)\n' + ' AND id NOT IN (\n' + ' SELECT id\n' + ' FROM heartbeat\n' + ' WHERE monitor_id = 30\n' + ' ORDER BY time DESC\n' + ' LIMIT 100\n' + ' )\n' + ' '} at process.unexpectedErrorHandler (/app/server/server.js:1872:13) at process.emit (node:events:519:28) at emitUnhandledRejection (node:internal/process/promises:250:13) at throwUnhandledRejectionsMode (node:internal/process/promises:385:19) at processPromiseRejections (node:internal/process/promises:470:17) at process.processTicksAndRejections (node:internal/process/task_queues:96:32)If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
The text was updated successfully, but these errors were encountered:
π‘οΈ Security Policy
Description
When running beta-slim and the latest version of the LSIO mariadb image, I receive a SQL error about LIMIT not being supported in a subquery of IN/ALL/ANY/SUM. This appears to be when it's trying to purge old statistics, I think.
π Reproduction steps
Launch compose stack with external mariadb (included below) and watch the logs.
π Expected behavior
Not throw this error, sucessfully clean up db as desired.
π Actual Behavior
Logging throws various errors included below.
π» Uptime-Kuma Version
2.0.0-beta.0
π» Operating System and Arch
TrueNAS Scale ElectricEel-24.10.0
π Browser
Chrome 131.0.6778.109 (Official Build) (arm64)
π₯οΈ Deployment Environment
π Relevant log output
The text was updated successfully, but these errors were encountered: