server.js:1699:13)

[lStan464l]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

It appears we are seeing this Spamming the Console. The below left unattended will eventually cause a Crash/Close which will require re-execution.

👟 Reproduction steps

Even after Updating. this behaviour is reproducible on our System.

👀 Expected behavior

None / Working.

😓 Actual Behavior

Crash after prolonged use. Within a working day

🐻 Uptime-Kuma Version

1.17.1 [Was doing this with 1.16]

💻 Operating System and Arch

Windows Server 2012

🌐 Browser

Google Chrome

🐋 Docker Version

No response

🟩 NodeJS Version

NodeJS 14

📝 Relevant log output

The Final Crash ends with "TypeError [ERR_INVALID_ARG_VALUE]: The property 'options.eval' must be false when 'filename' is not a string. Received true"

_Below is Spam in the Live Nodjs Window._
    
    
    at process.<anonymous> (C:\Program Files (x86)\uptime-kuma\server\server.js:1699:13)
    at process.emit (node:events:527:28)
    at emit (node:internal/process/promises:140:20)
    at processPromiseRejections (node:internal/process/promises:274:27)
    at processTicksAndRejections (node:internal/process/task_queues:97:32)
    at runNextTicks (node:internal/process/task_queues:65:3)
    at listOnTimeout (node:internal/timers:528:9)
    at processTimers (node:internal/timers:502:7)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
    at Client_SQLite3.acquireConnection (C:\Program Files (x86)\uptime-kuma\node_modules\knex\lib\client.js:305:26)
    at async Runner.ensureConnection (C:\Program Files (x86)\uptime-kuma\node_modules\knex\lib\execution\runner.js:259:28)
    at async Runner.run (C:\Program Files (x86)\uptime-kuma\node_modules\knex\lib\execution\runner.js:30:19)
    at async RedBeanNode.normalizeRaw (C:\Program Files (x86)\uptime-kuma\node_modules\redbean-node\dist\redbean-node.js:588:22)
    at async RedBeanNode.getRow (C:\Program Files (x86)\uptime-kuma\node_modules\redbean-node\dist\redbean-node.js:574:22)
    at async Function.calcUptime (C:\Program Files (x86)\uptime-kuma\server\model\monitor.js:729:22)
    at async Function.sendUptime (C:\Program Files (x86)\uptime-kuma\server\model\monitor.js:792:24)
    at async Function.sendStats (C:\Program Files (x86)\uptime-kuma\server\model\monitor.js:671:13) {
  sql: '\n' +
    '            SELECT\n' +
    '               -- SUM all duration, also trim off the beat out of time window\n' +
    '                SUM(\n' +
    '                    CASE\n' +
    '                        WHEN (JULIANDAY(`time`) - JULIANDAY(?)) * 86400 < duration\n' +
    '                        THEN (JULIANDAY(`time`) - JULIANDAY(?)) * 86400\n' +
    '                        ELSE duration\n' +
    '                    END\n' +
    '                ) AS total_duration,\n' +
    '\n' +
    '               -- SUM all uptime duration, also trim off the beat out of time window\n' +
    '                SUM(\n' +
    '                    CASE\n' +
    '                        WHEN (status = 1)\n' +
    '                        THEN\n' +
    '                            CASE\n' +
    '                                WHEN (JULIANDAY(`time`) - JULIANDAY(?)) * 86400 < duration\n' +
    '                                    THEN (JULIANDAY(`time`) - JULIANDAY(?)) * 86400\n' +
    '                                ELSE duration\n' +
    '                            END\n' +
    '                        END\n' +
    '                ) AS uptime_duration\n' +
    '            FROM heartbeat\n' +
    '            WHERE time > ?\n' +
    '            AND monitor_id = ?\n' +
    '        ',
  bindings: [
    '2022-07-04 10:37:56',
    '2022-07-04 10:37:56',
    '2022-07-04 10:37:56',
    '2022-07-04 10:37:56',
    '2022-07-04 10:37:56',
    12
  ]
}
    at process.<anonymous> (C:\Program Files (x86)\uptime-kuma\server\server.js:1699:13)
    at process.emit (node:events:527:28)
    at emit (node:internal/process/promises:140:20)
    at processPromiseRejections (node:internal/process/promises:274:27)
    at processTicksAndRejections (node:internal/process/task_queues:97:32)
If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues

[chakflying]

This is a database timeout error. Looks like it was trying to calculate the uptime, which is a read-heavy operation. Did you check that the disk usage is high, or storage is nearly full?

[lStan464l]

Hi Chakflying,

Appreciate the speedy response! loving Uptime Kuma! appreciate the hard work.

Yes, we have enough free space. not a massive amount of Disk Activity due to it being a very underused server.

[louislam]

Duplicate of #1397