Knex: Timeout acquiring a connection

[rjeevaram]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

I've been facing the below error in Uptimekuma Monitor recently. Has anyone faced this issue and any solution?

Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

📝 Error Message(s) or Log

Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Running as K8s pods in debian 11 Node

🌐 Browser

Chrome 122.0.6261.94

🖥️ Deployment Environment

• Runtime:
• Database:
• Filesystem used to store the database on:
• number of monitors:

[CommanderStorm]

Please fill out the Deployment Environment to help us debug this.
In addition, what retention have you configured?

TL;DR:
In v1, reducing either retention/ping-rate/.. or moving to a faster storage solution is the only option to get around this problem.
In v2, we have likely resolved this problem. See #4500 for further details of what needs to happen before we can release this version.

[CommanderStorm]

I am going to close this as resolved by v2.0 as I don't see evidence to the contrary.

TL;DR:
In v1, reducing either retention/ping-rate/.. or moving to a faster storage solution is the only option to get around this problem.
In v2, we have likely resolved this problem. See #4500 for further details of what needs to happen before we can release this version.

[jiriteach]

Ended up having to bin the db. SQLite db was over 6gb. Unfortunate but after starting again - no problems.