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. Support
  3. Nextcloud not responding and will not update

Nextcloud not responding and will not update

Scheduled Pinned Locked Moved Solved Support
postgresqlupdate
5 Posts 2 Posters 961 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.
    • P Offline
      P Offline
      privsec
      wrote on last edited by girish
      #1

      I am getting the following when I try to restart, update, or backup my nextcloud instance

      Jul 12 06:18:53 box:settings initCache: pre-load settings   
      Jul 12 06:18:53 box:taskworker Starting task 1999. Logs are at /home/yellowtent/platformdata/logs/APP_ID/apptask.log
      Jul 12 06:18:53 box:tasks 1999: {"percent":2,"error":null}
      Jul 12 06:18:53 box:apptask cloud.website_address.com startTask installationState: pending_update runState: running
      Jul 12 06:18:53 box:apptask cloud.website_address.com Updating to 4.9.1-1
      Jul 12 06:18:53 box:tasks 1999: {"percent":5,"message":"Verify manifest"}
      Jul 12 06:18:53 box:tasks 1999: {"percent":15,"message":"Backing up app"}
      Jul 12 06:18:53 box:backups backupApp - Backing up cloud.website_address.com with tag 2021-07-12-061853-750
      Jul 12 06:18:53 box:tasks 1999: {"percent":15,"message":"Backup - Snapshotting app cloud.website_address.com"}
      Jul 12 06:18:53 box:services cloud.website_address.com backupAddons
      Jul 12 06:18:53 box:services cloud.website_address.com backupAddons: Backing up ["postgresql","sendmail","ldap","redis","localstorage","scheduler","turn"]
      Jul 12 06:18:53 box:services cloud.website_address.com Backing up postgresql
      Jul 12 06:18:53 box:apptask cloud.website_address.com update aborted because backup failed BoxError: Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump
      at /home/yellowtent/box/src/backups.js:1072:36
      at wrapper (/home/yellowtent/box/node_modules/async/dist/async.js:268:20)
      at iterateeCallback (/home/yellowtent/box/node_modules/async/dist/async.js:413:21)
      at /home/yellowtent/box/node_modules/async/dist/async.js:321:20
      at /home/yellowtent/box/src/services.js:1301:9
      at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
      at Request.<anonymous> (/home/yellowtent/box/src/services.js:1312:53)
      at Request.emit (events.js:315:20)
      at Request.onRequestResponse (/home/yellowtent/box/node_modules/request/request.js:1059:10)
      at ClientRequest.emit (events.js:315:20) {
      reason: 'External Error',
      details: {},
      backupError: true
      Jul 12 06:18:53 box:apptask cloud.website_address.com updating app with values: {"installationState":"installed","error":null,"health":null}
      Jul 12 06:18:53 box:taskworker Task took 0.103 seconds
      Jul 12 06:18:53 box:tasks setCompleted - 1999: {"result":null,"error":{"stack":"BoxError: Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump\n at /home/yellowtent/box/src/backups.js:1072:36\n at wrapper (/home/yellowtent/box/node_modules/async/dist/async.js:268:20)\n at iterateeCallback (/home/yellowtent/box/node_modules/async/dist/async.js:413:21)\n at /home/yellowtent/box/node_modules/async/dist/async.js:321:20\n at /home/yellowtent/box/src/services.js:1301:9\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at Request.<anonymous> (/home/yellowtent/box/src/services.js:1312:53)\n at Request.emit (events.js:315:20)\n at Request.onRequestResponse (/home/yellowtent/box/node_modules/request/request.js:1059:10)\n at ClientRequest.emit (events.js:315:20)","name":"BoxError","reason":"External Error","details":{},"message":"Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump","backupError":true}}
      Jul 12 06:18:53 box:tasks 1999: {"percent":100,"result":null,"error":{"stack":"BoxError: Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump\n at /home/yellowtent/box/src/backups.js:1072:36\n at wrapper (/home/yellowtent/box/node_modules/async/dist/async.js:268:20)\n at iterateeCallback (/home/yellowtent/box/node_modules/async/dist/async.js:413:21)\n at /home/yellowtent/box/node_modules/async/dist/async.js:321:20\n at /home/yellowtent/box/src/services.js:1301:9\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at Request.<anonymous> (/home/yellowtent/box/src/services.js:1312:53)\n at Request.emit (events.js:315:20)\n at Request.onRequestResponse (/home/yellowtent/box/node_modules/request/request.js:1059:10)\n at ClientRequest.emit (events.js:315:20)","name":"BoxError","reason":"External Error","details":{},"message":"Unexpected response code when piping https://IP_ADDRESS:3000/databases/DB_STRING/backup?access_token=SOME_LONG_STRING: 500 message: Internal Server Error filename: /home/yellowtent/appsdata/APP_ID/postgresqldump","backupError":true}}
      
      1 Reply Last reply
      0
      • P Offline
        P Offline
        privsec
        wrote on last edited by
        #2

        When I try to install a new nextcloud app, I get
        Addons Error: Error tearing down postgresql. Status code: 500 message: sorry, too many clients already

        girishG 1 Reply Last reply
        0
        • P privsec

          When I try to install a new nextcloud app, I get
          Addons Error: Error tearing down postgresql. Status code: 500 message: sorry, too many clients already

          girishG Offline
          girishG Offline
          girish
          Staff
          wrote on last edited by
          #3

          @privsec that bug is fixed in Cloudron 6.3. Before you update, what you can do is: go to Services -> Postgresql -> Restart. Then please retry the update of nextcloud. After nextcloud update succeeds, please update to Cloudron 6.3 which should fix the problem for good.

          P 1 Reply Last reply
          2
          • girishG girish

            @privsec that bug is fixed in Cloudron 6.3. Before you update, what you can do is: go to Services -> Postgresql -> Restart. Then please retry the update of nextcloud. After nextcloud update succeeds, please update to Cloudron 6.3 which should fix the problem for good.

            P Offline
            P Offline
            privsec
            wrote on last edited by
            #4

            @girish said in Nextcloud not responding and will not update:

            @privsec that bug is fixed in Cloudron 6.3. Before you update, what you can do is: go to Services -> Postgresql -> Restart. Then please retry the update of nextcloud. After nextcloud update succeeds, please update to Cloudron 6.3 which should fix the problem for good.

            Trying that now

            P 1 Reply Last reply
            0
            • P privsec

              @girish said in Nextcloud not responding and will not update:

              @privsec that bug is fixed in Cloudron 6.3. Before you update, what you can do is: go to Services -> Postgresql -> Restart. Then please retry the update of nextcloud. After nextcloud update succeeds, please update to Cloudron 6.3 which should fix the problem for good.

              Trying that now

              P Offline
              P Offline
              privsec
              wrote on last edited by
              #5

              @privsec That worked, thanks!

              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