2.1.0 talking more CPU resources than 2.0 · louislam/uptime-kuma#6888

(19 comments) (1 reaction) (0 assignees)JavaScript (86,760 stars) (7,844 forks)batch import
bughelp wanted
Description

📑 I have found these related issues/pull requests

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.
📝 Description

Hi after updating to 2.1.0 my Uptime Kuma after few minutes went from 20% performance (CPU RAM) to 100% performance, before update i dont have any issue same settings i have before update.
👟 Reproduction steps

reboot :D
👀 Expected behavior

😓 Actual Behavior

🐻 Uptime-Kuma Version

2.1.0
💻 Operating System and Arch

Debian
🌐 Browser

🖥️ Deployment Environment

📝 Relevant log output

journalctl -u uptime-kuma -n 200 --no-pager
-- Journal begins at Thu 2026-01-29 15:29:32 CET, ends at Sun 2026-02-08 14:19:56 CET. --
Feb 08 14:02:23 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:02:43 UptimeKuma npm[169]: 2026-02-08T14:02:43+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://dzuris.dev/
Feb 08 14:02:43 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:02:43 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:02:43 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:02:45 UptimeKuma npm[169]: 2026-02-08T14:02:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:02:54 UptimeKuma npm[169]: 2026-02-08T14:02:54+01:00 [MONITOR] WARN: Monitor #35 'VPN.Dzuris.Dev': Failing: timeout of 48000ms exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
Feb 08 14:02:58 UptimeKuma npm[169]: 2026-02-08T14:02:58+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:03:03 UptimeKuma npm[169]: 2026-02-08T14:03:03+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:03:03 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:03:03 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:03:03 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:03:06 UptimeKuma npm[169]: 2026-02-08T14:03:06+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:03:15 UptimeKuma npm[169]: 2026-02-08T14:03:15+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:03:23 UptimeKuma npm[169]: 2026-02-08T14:03:23+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://dzuris.dev/
Feb 08 14:03:23 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:03:23 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:03:23 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:03:43 UptimeKuma npm[169]: 2026-02-08T14:03:43+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:03:43 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:03:43 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:03:43 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:03:45 UptimeKuma npm[169]: 2026-02-08T14:03:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:03:54 UptimeKuma npm[169]: 2026-02-08T14:03:54+01:00 [MONITOR] WARN: Monitor #35 'VPN.Dzuris.Dev': Failing: timeout of 48000ms exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
Feb 08 14:03:58 UptimeKuma npm[169]: 2026-02-08T14:03:58+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:04:03 UptimeKuma npm[169]: 2026-02-08T14:04:03+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://dzuris.dev/
Feb 08 14:04:03 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:04:03 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:04:03 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:04:06 UptimeKuma npm[169]: 2026-02-08T14:04:06+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:04:15 UptimeKuma npm[169]: 2026-02-08T14:04:15+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:04:23 UptimeKuma npm[169]: 2026-02-08T14:04:23+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://dzuris.dev/
Feb 08 14:04:23 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:04:23 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:04:23 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:04:43 UptimeKuma npm[169]: 2026-02-08T14:04:43+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:04:43 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:04:43 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:04:43 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:04:45 UptimeKuma npm[169]: 2026-02-08T14:04:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:04:54 UptimeKuma npm[169]: 2026-02-08T14:04:54+01:00 [MONITOR] WARN: Monitor #35 'VPN.Dzuris.Dev': Failing: timeout of 48000ms exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
Feb 08 14:04:58 UptimeKuma npm[169]: 2026-02-08T14:04:58+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:05:03 UptimeKuma npm[169]: 2026-02-08T14:05:03+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://dzuris.dev/
Feb 08 14:05:03 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:05:03 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:05:03 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:05:06 UptimeKuma npm[169]: 2026-02-08T14:05:06+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:05:15 UptimeKuma npm[169]: 2026-02-08T14:05:15+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:05:24 UptimeKuma npm[169]: 2026-02-08T14:05:24+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:05:24 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:05:24 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:05:24 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:05:45 UptimeKuma npm[169]: 2026-02-08T14:05:45+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:05:45 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:05:45 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:05:45 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:05:45 UptimeKuma npm[169]: 2026-02-08T14:05:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:05:54 UptimeKuma npm[169]: 2026-02-08T14:05:54+01:00 [MONITOR] WARN: Monitor #35 'VPN.Dzuris.Dev': Failing: timeout of 48000ms exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
Feb 08 14:05:58 UptimeKuma npm[169]: 2026-02-08T14:05:58+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:06:07 UptimeKuma npm[169]: 2026-02-08T14:06:07+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:06:07 UptimeKuma npm[169]: 2026-02-08T14:06:07+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:06:07 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:06:07 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:06:07 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:06:15 UptimeKuma npm[169]: 2026-02-08T14:06:15+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:06:28 UptimeKuma npm[169]: 2026-02-08T14:06:28+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:06:28 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:06:28 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:06:28 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:06:45 UptimeKuma npm[169]: 2026-02-08T14:06:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:06:50 UptimeKuma npm[169]: 2026-02-08T14:06:50+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://dzuris.dev/
Feb 08 14:06:50 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:06:50 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:06:50 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:06:55 UptimeKuma npm[169]: 2026-02-08T14:06:55+01:00 [MONITOR] WARN: Monitor #35 'VPN.Dzuris.Dev': Failing: timeout of 48000ms exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
Feb 08 14:06:58 UptimeKuma npm[169]: 2026-02-08T14:06:58+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:07:07 UptimeKuma npm[169]: 2026-02-08T14:07:07+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:07:19 UptimeKuma npm[169]: 2026-02-08T14:07:19+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:07:35 UptimeKuma npm[169]: 2026-02-08T14:07:35+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:07:35 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:07:35 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:07:35 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:08:35 UptimeKuma npm[169]: 2026-02-08T14:08:29+01:00 [MONITOR] WARN: Monitor #31 'Music Assistant': Pending: Connection failed | Max retries: 10 | Retry: 1 | Retry Interval: 20 seconds | Type: port
Feb 08 14:11:44 UptimeKuma npm[169]: 2026-02-08T14:11:36+01:00 [MONITOR] WARN: Monitor #6 'MQTT Broker': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: mqtt
Feb 08 14:14:01 UptimeKuma npm[169]: Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Feb 08 14:14:01 UptimeKuma npm[169]:     at Client_SQLite3.acquireConnection (/opt/uptime-kuma/node_modules/knex/lib/client.js:332:26)
Feb 08 14:14:01 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:65:5)
Feb 08 14:14:01 UptimeKuma npm[169]:     at listOnTimeout (node:internal/timers:549:9)
Feb 08 14:14:01 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:523:7)
Feb 08 14:14:01 UptimeKuma npm[169]:     at async Runner.ensureConnection (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:305:28)
Feb 08 14:14:01 UptimeKuma npm[169]:     at async Runner.run (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:30:19)
Feb 08 14:14:01 UptimeKuma npm[169]:     at async RedBeanNode.normalizeRaw (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:572:22)
Feb 08 14:14:01 UptimeKuma npm[169]:     at async RedBeanNode.getRow (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:558:22)
Feb 08 14:14:01 UptimeKuma npm[169]:     at async RedBeanNode.getCell (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:593:19)
Feb 08 14:14:01 UptimeKuma npm[169]:     at async Settings.get (/opt/uptime-kuma/server/settings.js:49:21) {
Feb 08 14:14:01 UptimeKuma npm[169]:   sql: 'SELECT `value` FROM setting WHERE `key` = ?  limit ?',
Feb 08 14:14:01 UptimeKuma npm[169]:   bindings: [ 'disableAuth', 1 ]
Feb 08 14:14:01 UptimeKuma npm[169]: }
Feb 08 14:14:01 UptimeKuma npm[169]:     at process.unexpectedErrorHandler (/opt/uptime-kuma/server/server.js:1982:13)
Feb 08 14:14:01 UptimeKuma npm[169]:     at process.emit (node:events:519:28)
Feb 08 14:14:01 UptimeKuma npm[169]:     at emitUnhandledRejection (node:internal/process/promises:252:13)
Feb 08 14:14:01 UptimeKuma npm[169]:     at throwUnhandledRejectionsMode (node:internal/process/promises:388:19)
Feb 08 14:14:01 UptimeKuma npm[169]:     at processPromiseRejections (node:internal/process/promises:475:17)
Feb 08 14:14:01 UptimeKuma npm[169]:     at processTicksAndRejections (node:internal/process/task_queues:106:32)
Feb 08 14:14:01 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:69:3)
Feb 08 14:14:01 UptimeKuma npm[169]:     at listOnTimeout (node:internal/timers:549:9)
Feb 08 14:14:01 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:523:7)
Feb 08 14:14:26 UptimeKuma npm[169]: If you keep encountering errors, please report to https://github.com/louislam/uptime-kuma/issues
Feb 08 14:15:12 UptimeKuma npm[169]: 2026-02-08T14:15:03+01:00 [MONITOR] WARN: Monitor #8 'Driveway Camera': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:15:59 UptimeKuma npm[169]: 2026-02-08T14:15:43+01:00 [MONITOR] WARN: Monitor #9 'Front Yard Camera': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: ping
Feb 08 14:17:01 UptimeKuma npm[169]: 2026-02-08T14:16:42+01:00 [MONITOR] WARN: Monitor #2 'Pi-Hole': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 3 | Retry: 1 | Retry Interval: 20 seconds | Type: dns
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #5 'Dzuriš Home': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 10 | Retry: 1 | Retry Interval: 20 seconds | Type: port
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #10 'Side Yard Camera': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #11 'Backyard Camera': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 60 seconds | Type: ping
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #14 'Switch 1': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #17 'Node-RED': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: port
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #25 'MySpeed': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: port
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #22 'Doorbell Camera': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:06 UptimeKuma npm[169]: Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Feb 08 14:17:06 UptimeKuma npm[169]:     at Client_SQLite3.acquireConnection (/opt/uptime-kuma/node_modules/knex/lib/client.js:332:26)
Feb 08 14:17:06 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:65:5)
Feb 08 14:17:06 UptimeKuma npm[169]:     at listOnTimeout (node:internal/timers:549:9)
Feb 08 14:17:06 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:523:7)
Feb 08 14:17:06 UptimeKuma npm[169]:     at async Runner.ensureConnection (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:305:28)
Feb 08 14:17:06 UptimeKuma npm[169]:     at async Runner.run (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:30:19)
Feb 08 14:17:06 UptimeKuma npm[169]:     at async RedBeanNode.storeCore (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:141:17)
Feb 08 14:17:06 UptimeKuma npm[169]:     at async RedBeanNode.store (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:110:20)
Feb 08 14:17:06 UptimeKuma npm[169]:     at async UptimeCalculator.update (/opt/uptime-kuma/server/uptime-calculator.js:315:9)
Feb 08 14:17:06 UptimeKuma npm[169]:     at async beat (/opt/uptime-kuma/server/model/monitor.js:1093:32) {
Feb 08 14:17:06 UptimeKuma npm[169]:   sql: undefined,
Feb 08 14:17:06 UptimeKuma npm[169]:   bindings: undefined
Feb 08 14:17:06 UptimeKuma npm[169]: }
Feb 08 14:17:06 UptimeKuma npm[169]:     at Timeout.safeBeat [as _onTimeout] (/opt/uptime-kuma/server/model/monitor.js:1134:25)
Feb 08 14:17:06 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:65:5)
Feb 08 14:17:06 UptimeKuma npm[169]:     at listOnTimeout (node:internal/timers:549:9)
Feb 08 14:17:06 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:523:7)
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] INFO: Try to restart the monitor
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #26 'go2rtc': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: port
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #35 'VPN.Dzuris.Dev': Failing: timeout of 48000ms exceeded | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #28 'Matterbridge': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: port
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #32 'AP 1': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:06 UptimeKuma npm[169]: 2026-02-08T14:17:06+01:00 [MONITOR] WARN: Monitor #33 'AP 2': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:07 UptimeKuma npm[169]: 2026-02-08T14:17:07+01:00 [MONITOR] WARN: Monitor #34 'Dzuriš Network': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:07 UptimeKuma npm[169]: 2026-02-08T14:17:07+01:00 [MONITOR] WARN: Monitor #36 'Proton VPN USA 🇺🇸': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:07 UptimeKuma npm[169]: 2026-02-08T14:17:07+01:00 [MONITOR] WARN: Monitor #38 'Dzuriš Network Guest VPN': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: ping
Feb 08 14:17:07 UptimeKuma npm[169]: Trace: KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
Feb 08 14:17:07 UptimeKuma npm[169]:     at Client_SQLite3.acquireConnection (/opt/uptime-kuma/node_modules/knex/lib/client.js:332:26)
Feb 08 14:17:07 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:65:5)
Feb 08 14:17:07 UptimeKuma npm[169]:     at listOnTimeout (node:internal/timers:549:9)
Feb 08 14:17:07 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:523:7)
Feb 08 14:17:07 UptimeKuma npm[169]:     at async Runner.ensureConnection (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:305:28)
Feb 08 14:17:07 UptimeKuma npm[169]:     at async Runner.run (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:30:19)
Feb 08 14:17:07 UptimeKuma npm[169]:     at async RedBeanNode.storeCore (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:141:17)
Feb 08 14:17:07 UptimeKuma npm[169]:     at async RedBeanNode.store (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:110:20)
Feb 08 14:17:07 UptimeKuma npm[169]:     at async UptimeCalculator.update (/opt/uptime-kuma/server/uptime-calculator.js:315:9)
Feb 08 14:17:07 UptimeKuma npm[169]:     at async beat (/opt/uptime-kuma/server/model/monitor.js:1093:32) {
Feb 08 14:17:07 UptimeKuma npm[169]:   sql: undefined,
Feb 08 14:17:07 UptimeKuma npm[169]:   bindings: undefined
Feb 08 14:17:07 UptimeKuma npm[169]: }
Feb 08 14:17:07 UptimeKuma npm[169]:     at Timeout.safeBeat [as _onTimeout] (/opt/uptime-kuma/server/model/monitor.js:1134:25)
Feb 08 14:17:07 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:65:5)
Feb 08 14:17:07 UptimeKuma npm[169]:     at listOnTimeout (node:internal/timers:549:9)
Feb 08 14:17:07 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:523:7)
Feb 08 14:17:07 UptimeKuma npm[169]: 2026-02-08T14:17:07+01:00 [MONITOR] ERROR: Please report to https://github.com/louislam/uptime-kuma/issues
Feb 08 14:17:07 UptimeKuma npm[169]: 2026-02-08T14:17:07+01:00 [MONITOR] INFO: Try to restart the monitor
Feb 08 14:17:07 UptimeKuma npm[169]: 2026-02-08T14:17:07+01:00 [MONITOR] WARN: Monitor #20 'Cloudflare DNS': Pending: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Max retries: 1 | Retry: 1 | Retry Interval: 20 seconds | Type: dns
Feb 08 14:17:42 UptimeKuma npm[169]: 2026-02-08T14:17:42+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:43 UptimeKuma npm[169]: 2026-02-08T14:17:43+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:44 UptimeKuma npm[169]: 2026-02-08T14:17:44+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:45 UptimeKuma npm[169]: 2026-02-08T14:17:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:45 UptimeKuma npm[169]: 2026-02-08T14:17:45+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:46 UptimeKuma npm[169]: 2026-02-08T14:17:46+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:46 UptimeKuma npm[169]: 2026-02-08T14:17:46+01:00 [MONITOR] WARN: Monitor #30 'Dzuriš.Dev': Failing: page.goto: net::ERR_SSL_PROTOCOL_ERROR at https://dzuris.dev/
Feb 08 14:17:46 UptimeKuma npm[169]: =========================== logs ===========================
Feb 08 14:17:46 UptimeKuma npm[169]: navigating to "https://dzuris.dev/", waiting until "networkidle"
Feb 08 14:17:46 UptimeKuma npm[169]: ============================================================ | Interval: 20 seconds | Type: real-browser | Down Count: 0 | Resend Interval: 0
Feb 08 14:17:47 UptimeKuma npm[169]: 2026-02-08T14:17:46+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:47 UptimeKuma npm[169]: 2026-02-08T14:17:47+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:48 UptimeKuma npm[169]: 2026-02-08T14:17:48+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:48 UptimeKuma npm[169]: 2026-02-08T14:17:48+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:49 UptimeKuma npm[169]: 2026-02-08T14:17:49+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:17:50 UptimeKuma npm[169]: 2026-02-08T14:17:49+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:18:10 UptimeKuma npm[169]: 2026-02-08T14:18:09+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:18:43 UptimeKuma npm[169]: 2026-02-08T14:18:43+01:00 [RATE-LIMIT] INFO: remaining requests: 60
Feb 08 14:19:00 UptimeKuma npm[169]: 2026-02-08T14:19:00+01:00 [MONITOR] WARN: Monitor #18 'Zigbee2MQTT': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:19:07 UptimeKuma npm[169]: 2026-02-08T14:19:07+01:00 [MONITOR] ERROR: Cannot send notification to Telegram
Feb 08 14:19:08 UptimeKuma npm[169]: 2026-02-08T14:19:07+01:00 [MONITOR] ERROR: Error: AggregateError (code=ETIMEDOUT) - caused by: connect ETIMEDOUT 149.154.166.110:443 (code=ETIMEDOUT); connect ENETUNREACH 2001:67c:4e8:f004::9:443 - Local (:::0) (code=ENETUNREACH)
Feb 08 14:19:08 UptimeKuma npm[169]:     at Telegram.throwGeneralAxiosError (/opt/uptime-kuma/server/notification-providers/notification-provider.js:165:15)
Feb 08 14:19:08 UptimeKuma npm[169]:     at Telegram.send (/opt/uptime-kuma/server/notification-providers/telegram.js:107:18)
Feb 08 14:19:08 UptimeKuma npm[169]:     at processTicksAndRejections (node:internal/process/task_queues:105:5)
Feb 08 14:19:08 UptimeKuma npm[169]:     at runNextTicks (node:internal/process/task_queues:69:3)
Feb 08 14:19:08 UptimeKuma npm[169]:     at process.processTimers (node:internal/timers:520:9)
Feb 08 14:19:08 UptimeKuma npm[169]:     at async Monitor.sendNotification (/opt/uptime-kuma/server/model/monitor.js:1543:21)
Feb 08 14:19:08 UptimeKuma npm[169]:     at async beat (/opt/uptime-kuma/server/model/monitor.js:1009:21)
Feb 08 14:19:08 UptimeKuma npm[169]:     at async Timeout.safeBeat [as _onTimeout] (/opt/uptime-kuma/server/model/monitor.js:1132:17)
Feb 08 14:19:09 UptimeKuma npm[169]: 2026-02-08T14:19:09+01:00 [MONITOR] WARN: Monitor #27 'Frigate': Failing: Connection failed | Interval: 60 seconds | Type: port | Down Count: 0 | Resend Interval: 0
Feb 08 14:19:16 UptimeKuma npm[169]: 2026-02-08T14:19:16+01:00 [MONITOR] WARN: Monitor #37 'Dzuriš Network VPN': Failing: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call? | Interval: 60 seconds | Type: ping | Down Count: 0 | Resend Interval: 0
Contributor guide

Tech stack: javascriptnodejs
Domain: backendperformance
Issue type: bug
Difficulty: 3
Estimated time: half day
Activity status: active
Clarity: mostly clear
Prerequisites: basic Node.js profilingunderstanding of Uptime Kuma monitor types
Newbie friendliness: 30
Research direction: Investigate CPU usage differences between v2.0 and v2.1.0. Focus on changes in monitor checking logic, especially 'real browser' monitors that use Puppeteer. Use Node.js profiling tools like clinic or prof to identify hotspots. Look at recent commits in the repository, particularly those related to monitor scheduling or browser automation.