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
  • Brite
  • 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. NocoDB
  3. Nocodb stop responding after about every 2 days

Nocodb stop responding after about every 2 days

Scheduled Pinned Locked Moved NocoDB
nocodb
2 Posts 2 Posters 31 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.
  • C Offline
    C Offline
    cfabrice
    wrote last edited by
    #1

    After 36-48 hours, my nocodb instance gets down.
    I usually reboot Cloudron (there is only another unused 8n8 app on it) and then I'm good for anew period.
    I don't know how to tackle this pbl.
    The server is a vps lite from Infomaniak with 4 cpu, 4 Gb of ram and 80 Gb of disk. I already migrated from a public cloud infomaniak slightly less powerfull (2 cpu) because of the same problem, thinking it was the lack of power. But it didn't change. Even got worse (more frequent) !
    There is not so much data in this nocodb. 6 databases very simple. Some of them are just one table. Most bases are used as backend for small nuxtjs website. Most api access are heavily cached until invalidated on the nuxt sites so I guess there is very little charge on the server.
    Looking at the logs, I see frequently error like this: "Nov 10 21:22:39 [Nest] 1 - 11/10/2025, 8:22:39 PM LOG [BaseModelSqlv2] Error: Formula error: Knex: Timeout acquiring a connection. The pool is probably full. Are you missing a .transacting(trx) call?" that I don't understand. It doesn't seem to prevent the app to be functioning.
    Looking at the graph I can see that the ram consumption is slowly rising, starting at 0,4 gb after a reboot and rising to 1 gb where it usually doesn't last long before the app become irresponsive. Even if my memory limit is set to 4gb or ram and 100 % of cpu.
    Cloudron itself is always working fine and responsive.
    I'd be very grateful if someone could guide me or even have a look ! Thank you.

    1 Reply Last reply
    2
    • nebulonN Away
      nebulonN Away
      nebulon
      Staff
      wrote last edited by
      #2

      Just a wild guess, but sounds like maybe something in nocodb is not freeing up database connections and eventually no more new connection can be established. Restarting the app would free up those handles.

      Have you searched upstream in the nocodb issue tracker already?

      1 Reply Last reply
      0
      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