Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Bookmarks
  • Search
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Brand Logo

Cloudron Forum

Apps | Demo | Docs | Install
  1. Cloudron Forum
  2. Uptime Kuma
  3. What are your numbers in Uptime Kuma?

What are your numbers in Uptime Kuma?

Scheduled Pinned Locked Moved Uptime Kuma
3 Posts 2 Posters 196 Views 2 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • luckowL Offline
    luckowL Offline
    luckow
    translator
    wrote on last edited by
    #1

    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?

    Pronouns: he/him | Primary language: German

    J 1 Reply Last reply
    2
    • luckowL luckow

      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?

      J Offline
      J Offline
      joseph
      Staff
      wrote on last edited by
      #2

      @luckow said in What are your numbers in Uptime Kuma?:

      The solution is simple: restart the container

      or another uptime kuma instance, maybe? 🙂

      luckowL 1 Reply Last reply
      0
      • J joseph

        @luckow said in What are your numbers in Uptime Kuma?:

        The solution is simple: restart the container

        or another uptime kuma instance, maybe? 🙂

        luckowL Offline
        luckowL Offline
        luckow
        translator
        wrote on last edited by
        #3

        @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.

        Pronouns: he/him | Primary language: German

        1 Reply Last reply
        2
        Reply
        • Reply as topic
        Log in to reply
        • Oldest to Newest
        • Newest to Oldest
        • Most Votes


        • Login

        • Don't have an account? Register

        • Login or register to search.
        • First post
          Last post
        0
        • Categories
        • Recent
        • Tags
        • Popular
        • Bookmarks
        • Search