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 - Status | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Update from 8.3.2 to 9.0.x fails

Update from 8.3.2 to 9.0.x fails

Scheduled Pinned Locked Moved Solved Support
update
7 Posts 3 Posters 620 Views 3 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.
  • D Offline
    D Offline
    Divemasterza
    wrote on last edited by joseph
    #1

    When trying to update to version 9.0.x the update process exits with a error code

    Nov 14 00:04:58
    Nov 14 00:05:03 box:shell 2025-11-13T22:05:03 ==> update: cloudron-updater is still active. will check in 5 seconds
    Nov 14 00:05:03
    Nov 14 00:05:08 box:shell 2025-11-13T22:05:08 ==> update: cloudron-updater failed
    Nov 14 00:05:08
    Nov 14 00:05:08 box:shell updater: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-4248070419 /home/yellowtent/platformdata/logs/tasks/7769.log errored BoxError: updater exited with code 1 signal null
    Nov 14 00:05:08 at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:137:19)
    Nov 14 00:05:08 at ChildProcess.emit (node:events:519:28)
    Nov 14 00:05:08 at ChildProcess.emit (node:domain:488:12)
    Nov 14 00:05:08 at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
    Nov 14 00:05:08 reason: 'Shell Error',
    Nov 14 00:05:08 details: {},
    Nov 14 00:05:08 code: 1,
    Nov 14 00:05:08 signal: null
    Nov 14 00:05:08 }
    Nov 14 00:05:08 box:locks write: current locks: {"update_task":null}
    Nov 14 00:05:08 box:locks release: update
    Nov 14 00:05:08 box:taskworker Task took 5514.708 seconds
    Nov 14 00:05:08 box:tasks setCompleted - 7769: {"result":null,"error":null}
    Nov 14 00:05:08 box:tasks update 7769: {"percent":100,"result":null,"error":null}
    

    Any idea?

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

      Can you check if you see any errors in the mentioned log file for the update task?
      The file can be found at /home/yellowtent/platformdata/logs/tasks/7769.log

      1 Reply Last reply
      1
      • D Offline
        D Offline
        Divemasterza
        wrote on last edited by
        #3

        So the log reflect the same data (quite a large log)

        First part of the logo is the backup part - Successful

        2025-11-13T21:54:51.507Z box:backupupload upload completed. error: null
        2025-11-13T21:54:51.507Z box:backuptask runBackupUpload: result - {"result":""}
        2025-11-13T21:54:51.529Z box:backuptask uploadBoxSnapshot: took 2.253 seconds
        2025-11-13T21:54:51.532Z box:backuptask rotateBoxBackup: rotating to id 2025-11-13-203330-497/box_v8.3.2
        

        The comes the grabbing of the release and locks

        2025-11-13T21:54:51.879Z box:locks acquire: update
        2025-11-13T21:54:51.880Z box:tasks update 7769: {"percent":70,"message":"Installing update"}
        2025-11-13T21:54:51.880Z box:updater Updating box with https://releases.cloudron.io/box-bfe9ee457d-bfe9ee457d-9.0.8.tar.gz
        2025-11-13T21:54:51.880Z box:shell updater /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-4248070419 /home/yellowtent/platformdata/logs/tasks/7769.log
        2025-11-13T21:54:51.914Z box:shell 2025-11-13T21:54:51 ==> update: updating Cloudron with /tmp/box-4248070419
        2025-11-13T21:54:51.947Z box:shell Running as unit: cloudron-updater.service; invocation ID: 53a06dc92d404749a38995ac6f589301
        2025-11-13T21:54:51.956Z box:shell 2025-11-13T21:54:51 ==> update: cloudron-updater is still active. will check in 5 seconds
        2025-11-13T21:54:52 ==> installer: Updating from 8.3.2 to 9.0.8
        /usr/bin/docker
        

        then for roughly 10 minutes

        2025-11-13T21:55:01.984Z box:shell 2025-11-13T21:55:01 ==> update: cloudron-updater is still active. will check in 5 seconds
        

        With fail thereafter

        2025-11-13T22:05:03.577Z box:shell 2025-11-13T22:05:03 ==> update: cloudron-updater is still active. will check in 5 seconds
        
        2025-11-13T22:05:08.591Z box:shell 2025-11-13T22:05:08 ==> update: cloudron-updater failed
        
        2025-11-13T22:05:08.596Z box:shell updater: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-4248070419 /home/yellowtent/platformdata/logs/tasks/7769.log errored BoxError: updater exited with code 1 signal null
            at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:137:19)
            at ChildProcess.emit (node:events:519:28)
            at ChildProcess.emit (node:domain:488:12)
            at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
          reason: 'Shell Error',
          details: {},
          code: 1,
          signal: null
        }
        2025-11-13T22:05:08.604Z box:locks write: current locks: {"update_task":null}
        2025-11-13T22:05:08.605Z box:locks release: update
        2025-11-13T22:05:08.605Z box:taskworker Task took 5514.708 seconds
        2025-11-13T22:05:08.605Z box:tasks setCompleted - 7769: {"result":null,"error":null}
        2025-11-13T22:05:08.607Z box:tasks update 7769: {"percent":100,"result":null,"error":null}
        
        1 Reply Last reply
        0
        • girishG Do not disturb
          girishG Do not disturb
          girish
          Staff
          wrote on last edited by
          #4

          @Divemasterza can you also check /home/yellowtent/platformdata/logs/updater/ (there is a log file there) OR journalctl -u cloudron-updater ? (the log location depends on the ubuntu version)

          I think most likely it is getting stuck in dpkg installation of the latest docker. Can you see if apt-install -y --fix-missing is working ok? Or dpkg --force-confold --configure -a . Sometimes, they ask questions and get stuck despite asking them to move on.

          D 1 Reply Last reply
          0
          • girishG girish

            @Divemasterza can you also check /home/yellowtent/platformdata/logs/updater/ (there is a log file there) OR journalctl -u cloudron-updater ? (the log location depends on the ubuntu version)

            I think most likely it is getting stuck in dpkg installation of the latest docker. Can you see if apt-install -y --fix-missing is working ok? Or dpkg --force-confold --configure -a . Sometimes, they ask questions and get stuck despite asking them to move on.

            D Offline
            D Offline
            Divemasterza
            wrote on last edited by
            #5

            @girish said in Update from 8.3.2 to 9.0.x fails:

            @Divemasterza can you also check /home/yellowtent/platformdata/logs/updater/ (there is a log file there) OR journalctl -u cloudron-updater ? (the log location depends on the ubuntu version)

            No logs there

            @girish said in Update from 8.3.2 to 9.0.x fails:

            Can you see if apt-install -y --fix-missing is working ok?

            I am sure you meant apt-get install -f -y
            all good on that side

            @girish said in Update from 8.3.2 to 9.0.x fails:

            dpkg --force-confold --configure -a

            No output

            1 Reply Last reply
            0
            • girishG Do not disturb
              girishG Do not disturb
              girish
              Staff
              wrote on last edited by
              #6

              @Divemasterza thanks. Mmm, a bit lost here since there are no logs to work with. Can you send a mail to support@cloudron.io ? We can debug it, would be good to figure out what the issue is.

              1 Reply Last reply
              0
              • D Offline
                D Offline
                Divemasterza
                wrote on last edited by
                #7

                So turns out that potentially the issue is disk space.
                we ran the process again without changing anything - same result
                we clean up and enable at least 40 GB of space and relaunched the update process = successful update

                suggestions: better pre-update space check and verbose messaging about needed space for update

                1 Reply Last reply
                2
                • J joseph has marked this topic as solved on

                Hello! It looks like you're interested in this conversation, but you don't have an account yet.

                Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.

                With your input, this post could be even better 💗

                Register Login
                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