Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Knex: Timeout acquiring a connection #4924

Closed
1 task done
Tealk opened this issue Jul 10, 2024 · 8 comments
Closed
1 task done

Knex: Timeout acquiring a connection #4924

Tealk opened this issue Jul 10, 2024 · 8 comments
Labels
area:deployment related to how uptime kuma can be deployed help

Comments

@Tealk
Copy link

Tealk commented Jul 10, 2024

📑 I have found these related issues/pull requests

#4598

🛡️ Security Policy

Description

I have been getting the error message very frequently for 2 days:

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

grafik

👟 Reproduction steps

I can't say, I've been running Kuma for months now without changing anything.

👀 Expected behavior

😓 Actual Behavior

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Debian 12

🌐 Browser

Firefox

🖥️ Deployment Environment

  • Runtime: Docker 26.1.4
  • Database: sqlite
  • Filesystem used to store the database on: ext4 on SSD
  • number of monitors: 43

Installation: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install#-docker-compose

📝 Relevant log output

No response

@Tealk Tealk added the bug Something isn't working label Jul 10, 2024
@CommanderStorm CommanderStorm added help area:deployment related to how uptime kuma can be deployed and removed bug Something isn't working labels Jul 10, 2024
@CommanderStorm
Copy link
Collaborator

I don't know why you opened another issue while linking #4598.
The resolution of said issue has not changed.

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.

@Tealk
Copy link
Author

Tealk commented Jul 10, 2024

Because, as I said, it has been running on the VM for months without any changes and there were no problems and it suddenly started. The memory has not become slower.

@CommanderStorm
Copy link
Collaborator

CommanderStorm commented Jul 10, 2024

Yes, that is the performance problem noted in #4598
I don't see a difference.
Retention is 90 days => maybe consider reducing this.

Running a DB of EMMC-Memory (I think that is what you mean when you say memory) is severely limiting if you want to do something IO-Heavy..

@CommanderStorm
Copy link
Collaborator

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

Forgot to close as resolved

@Tealk
Copy link
Author

Tealk commented Jul 23, 2024

is there a way to connect mysql when using docker compose? i can't find any references for this in the wiki.
https://github.com/louislam/uptime-kuma/wiki/Environment-Variables

@CommanderStorm
Copy link
Collaborator

Please see #4500 for further context on the v2.0 release

@Tealk
Copy link
Author

Tealk commented Jul 23, 2024

the question was less whether it comes in the 2.x but whether I can connect it now with mysql.

@CommanderStorm
Copy link
Collaborator

No, using mysql is a change that requires v2.0. (See #4500 what tasks/bugs are left if you want to chip in ^^)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:deployment related to how uptime kuma can be deployed help
Projects
None yet
Development

No branches or pull requests

2 participants