Receiving error when deleting monitor: Timeout acquiring a connection. The pool is probably full. @louislam #4109

Closed
opened 2026-02-28 03:51:28 -05:00 by deekerman · 1 comment
Owner

Originally created by @SomeoneVeryCool on GitHub (Apr 28, 2025).

I do not see a similar issue regarding this.

🛡️ Security Policy

📝 Description

Recently I had to delete a monitor from our uptime-kuma instance which made uptime blow up with every monitor reporting "[DOWN] Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?"

👟 Reproduction steps

Simply Deleting a monitor.

👀 Expected behavior

Monitor delete with no issues and everything runs as normal.

😓 Actual Behavior

Takes a while and cause multiple monitors to go down.

🐻 Uptime-Kuma Version

1.23.16

💻 Operating System and Arch

Ubuntu 24.04 LTS

🌐 Browser

Firefox 137.0.2

🖥️ Deployment Environment

  • Runtime Environment:
    • Node.js: Version 18.19.1 (LTS: No)
    • NPM: Version 9
  • Database:
    • SQLite: Embedded
  • Database Storage:
    • Filesystem:
      • Linux: ext4
    • Storage Medium: NVMe
  • Uptime Kuma Setup:
    • Number of monitors: 300+

📝 Relevant log output

"[DOWN] Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?"
Originally created by @SomeoneVeryCool on GitHub (Apr 28, 2025). ### 📑 I have found these related issues/pull requests I do not see a similar issue regarding this. ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description Recently I had to delete a monitor from our uptime-kuma instance which made uptime blow up with every monitor reporting "[DOWN] Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?" ### 👟 Reproduction steps Simply Deleting a monitor. ### 👀 Expected behavior Monitor delete with no issues and everything runs as normal. ### 😓 Actual Behavior Takes a while and cause multiple monitors to go down. ### 🐻 Uptime-Kuma Version 1.23.16 ### 💻 Operating System and Arch Ubuntu 24.04 LTS ### 🌐 Browser Firefox 137.0.2 ### 🖥️ Deployment Environment - **Runtime Environment**: - Node.js: Version `18.19.1` (LTS: No) - NPM: Version `9` - **Database**: - SQLite: Embedded - **Database Storage**: - **Filesystem**: - Linux: ext4 - **Storage Medium**: NVMe - **Uptime Kuma Setup**: - Number of monitors: `300+` ### 📝 Relevant log output ```bash session "[DOWN] Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?" ```
deekerman 2026-02-28 03:51:28 -05:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

@louislam commented on GitHub (Apr 28, 2025):

Duplicate of #2781

@louislam commented on GitHub (Apr 28, 2025): Duplicate of #2781
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#4109
No description provided.