What are your numbers in Uptime Kuma?
-
Since a few days one of our Uptime Kuma instances shows the following error:
Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?I found an issue upstream to this error -> https://github.com/louislam/uptime-kuma/issues/2346
The instance has 60+ instances to monitor and the current issues are: no way to delete instances, unresponsive dashboard. The solution is simple: restart the container.
The resources are 50% CPU, 2 GB RAM:
What are your numbers?
-
Since a few days one of our Uptime Kuma instances shows the following error:
Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?I found an issue upstream to this error -> https://github.com/louislam/uptime-kuma/issues/2346
The instance has 60+ instances to monitor and the current issues are: no way to delete instances, unresponsive dashboard. The solution is simple: restart the container.
The resources are 50% CPU, 2 GB RAM:
What are your numbers?
-
@luckow said in What are your numbers in Uptime Kuma?:
The solution is simple: restart the container
or another uptime kuma instance, maybe?
@joseph That's the plan for the future. Now I'm interested in getting the max number of monitored instances. 62 is way too many. 180 days retention policy for the metrics ditto. Sqlite DB is about 2 GB in size. Purging old data in the database does not work. Let's see.
