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


    Cloudron Forum

    • Register
    • Login
    • Search
    • Categories
    • Recent
    • Tags
    • Popular

    Solved Fresh Cloudron tying to install n8n, error due to "Not found: Unable to find container postgresql".

    N8N
    postgresql
    2
    7
    232
    Loading More Posts
    • 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.
    • B
      biozork last edited by girish

      Hi all 👋,

      I'm brand new to selfhosting Cloudron, but I have had a bit of fun running n8n locally. n8n is really powerful compared to similar tools I've tried in the past.

      My aim was to setup cloudron with n8n on a local server, to run all sorts of automations. I installed cloudron, got dns and account setup without too much trouble.

      When I try to install n8n from a fresh cloudron install, i get this error:
      "Not found: Unable to find container postgresql"

      Thinking I could just uninstall and try again, I get same error "Not found: Unable to find container postgresql" when trying to uninstall.

      So now I'm stuck.

      Any suggestions what to do from here is much appreciated?
      Also if you have any clues to why I got the postgresql error.

      Feb 14 19:06:30 box:tasks setCompleted - 6: {"result":null,"error":{"stack":"BoxError: Unable to find container postgresql\n at Object.inspect (/home/yellowtent/box/src/docker.js:528:50)\n at processTicksAndRejections (internal/process/task_queues.js:95:5)\n at async getContainerDetails (/home/yellowtent/box/src/services.js:270:20)\n at async Object.teardownPostgreSql [as teardown] (/home/yellowtent/box/src/services.js:1436:20)\n at async Object.teardownAddons (/home/yellowtent/box/src/services.js:633:9)\n at async uninstall (/home/yellowtent/box/src/apptask.js:702:5)","name":"BoxError","reason":"Not found","details":{},"message":"Unable to find container postgresql"}}
      Feb 14 19:06:30 box:tasks update 6: {"percent":100,"result":null,"error":{"stack":"BoxError: Unable to find container postgresql\n at Object.inspect (/home/yellowtent/box/src/docker.js:528:50)\n at processTicksAndRejections (internal/process/task_queues.js:95:5)\n at async getContainerDetails (/home/yellowtent/box/src/services.js:270:20)\n at async Object.teardownPostgreSql [as teardown] (/home/yellowtent/box/src/services.js:1436:20)\n at async Object.teardownAddons (/home/yellowtent/box/src/services.js:633:9)\n at async uninstall (/home/yellowtent/box/src/apptask.js:702:5)","name":"BoxError","reason":"Not found","details":{},"message":"Unable to find container postgresql"}}
      Unable to find container postgresql
      at Object.inspect (/home/yellowtent/box/src/docker.js:528:50)
      at processTicksAndRejections (internal/process/task_queues.js:95:5)
      at async getContainerDetails (/home/yellowtent/box/src/services.js:270:20)
      at async Object.teardownPostgreSql [as teardown] (/home/yellowtent/box/src/services.js:1436:20)
      at async Object.teardownAddons (/home/yellowtent/box/src/services.js:633:9)
      at async uninstall (/home/yellowtent/box/src/apptask.js:702:5)
      

      Thanks in advance
      (from the newbie)
      biozork

      girish 1 Reply Last reply Reply Quote 0
      • girish
        girish Staff @biozork last edited by

        @biozork I think (for some reason) the postgresql service is down. Can you go to Services and check status of postgresql ? Maybe give it a bit more memory using the configure button and restart the service ?

        B 1 Reply Last reply Reply Quote 0
        • B
          biozork @girish last edited by

          @girish you are absolutely right.

          c6fa3c58-40bd-432d-b327-ecb8aadabacc-image.png

          A restart of the service did the trick.

          Thanks for a lightning fast response 🙏

          girish 1 Reply Last reply Reply Quote 0
          • girish
            girish Staff @biozork last edited by

            @biozork In the screenshot, the sftp is also down. I wonder what's up! Are any other services down ?

            B 1 Reply Last reply Reply Quote 0
            • B
              biozork @girish last edited by

              @girish sftp and mongodb was down.

              I restarted those and now they are up and running.
              f2a761b9-6453-4344-aa42-5256f08021c0-image.png

              Now I know I should keep an eye on those services and maybe assign more memory.

              1 Reply Last reply Reply Quote 1
              • girish
                girish Staff last edited by

                In theory, one should get a notification when a service runs out of memory (the red indicator on the nav bar), but I have seen atleast one other one bug report that it's not reliable. Let me know if you don't see it either.

                B 1 Reply Last reply Reply Quote 0
                • B
                  biozork @girish last edited by

                  @girish I saw no red indicators on the nav bar. I guess that would have helped me towards the source of the problem. But I will keep an eye if a service gets into trouble again.

                  1 Reply Last reply Reply Quote 0
                  • First post
                    Last post
                  Powered by NodeBB