-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Comments
I don't know why you opened another issue while linking #4598. I am going to close this as resolved by
|
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. |
Yes, that is the performance problem noted in #4598 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.. |
Forgot to close as resolved |
is there a way to connect mysql when using docker compose? i can't find any references for this in the wiki. |
Please see #4500 for further context on the v2.0 release |
the question was less whether it comes in the 2.x but whether I can connect it now with mysql. |
No, using mysql is a change that requires |
📑 I have found these related issues/pull requests
#4598
🛡️ Security Policy
Description
I have been getting the error message very frequently for 2 days:
👟 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
Installation: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%94%A7-How-to-Install#-docker-compose
📝 Relevant log output
No response
The text was updated successfully, but these errors were encountered: