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

Error log in /opt/uptime-kuma/data #5508

Closed
2 tasks done
gmiss65 opened this issue Jan 8, 2025 · 1 comment
Closed
2 tasks done

Error log in /opt/uptime-kuma/data #5508

gmiss65 opened this issue Jan 8, 2025 · 1 comment
Labels

Comments

@gmiss65
Copy link

gmiss65 commented Jan 8, 2025

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

  • I checked and didn't find similar issue

🛡️ Security Policy

📝 Describe your problem

After some days of valid execution, the system didn't work and in the directory /opt/uptime-kuma/data I found an error.log file described below. It seems that from this point onward kuma service doesn't run correctly.
Do you have any kind of solution? Thank you very much.

📝 Error Message(s) or Log

[2025-01-08 15:18:27] KnexTimeoutError: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?
at Client_SQLite3.acquireConnection (/opt/uptime-kuma/node_modules/knex/lib/client.js:312:26)
at async Runner.ensureConnection (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:287:28)
at async Runner.run (/opt/uptime-kuma/node_modules/knex/lib/execution/runner.js:30:19)
at async RedBeanNode.storeCore (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:150:26)
at async RedBeanNode.store (/opt/uptime-kuma/node_modules/redbean-node/dist/redbean-node.js:110:20)
at async beat (/opt/uptime-kuma/server/model/monitor.js:1013:13)
at async Timeout.safeBeat [as _onTimeout] (/opt/uptime-kuma/server/model/monitor.js:1032:17) {
sql: undefined,
bindings: undefined
}

🐻 Uptime-Kuma Version

1.23.13

💻 Operating System and Arch

Gnu/Linux

🌐 Browser

Firefox 134.0

🖥️ Deployment Environment

  • Runtime: nodejs 20.12.2
  • Database: sqlite
  • Filesystem used to store the database on: /opt/uptime-kuma/data/kuma.db
  • number of monitors: 450
@gmiss65 gmiss65 added the help label Jan 8, 2025
@CommanderStorm
Copy link
Collaborator

Please see the following issue why this is happening and what we have done to combat this:

Your number of monitors * ping time * retention time is currently too high.

V2 does solve the issue, consider giving 2.0.0-beta.1 a try if the releaseblocker is okay with you: https://github.com/louislam/uptime-kuma/issues?q=is%3Aopen+is%3Aissue+label%3Areleaseblocker

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants