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 Problem updating from Cloudron 6.1.2 to 6.2.4

    Support
    update
    2
    6
    351
    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.
    • M
      madrush last edited by girish

      This update keeps timing out on me, with error messages such as the following:

      {
        "taskId": "6395",
        "errorMessage": "update exited with code 1 signal null",
        "timedOut": false
      }
      
      2021-03-13T06:30:16.608Z box:updater Update failed with error { stack:
         'BoxError: update exited with code 1 signal null\n    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:66:17)\n    at ChildProcess.emit (events.js:198:13)\n    at ChildProcess.EventEmitter.emit (domain.js:448:20)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)',
        name: 'BoxError',
        reason: 'Spawn Error',
        details: {},
        message: 'update exited with code 1 signal null',
        code: 1,
        signal: null }
      
      girish 2 Replies Last reply Reply Quote 0
      • girish
        girish Staff @madrush last edited by

        @madrush Can you look into /home/yellowtent/platformdata/logs/tasks/6395.log ?

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

          @madrush Are you on ubuntu 16 by any chance? If so, I just debugged a server with a similar back trace. If you do journalctl -u cloudron-updater, do you see "no entries" ? It seems there is some systemd issue. In my case, a reboot of the server fixed it.

          1 Reply Last reply Reply Quote 0
          • M
            madrush @girish last edited by

            @girish: In the log, after all the backups are completed, I see the following entries in the log:

            2021-03-16T07:40:49.065Z box:tasks 6395: {"percent":75.31538461538463,"message":"box: Copied 10177 files with error: null"}
            2021-03-16T07:40:49.069Z box:backups Rotated box backup successfully as id 2021-03-16-070020-445/box_2021-03-16-073619-390_v6.1.2
            2021-03-16T07:40:49.069Z box:updater updating box https://prod-cloudron-releases.s3.amazonaws.com/box-3ee3786936-4dffce0b71-6.2.4.tar.gz
            2021-03-16T07:40:49.069Z box:tasks 6395: {"percent":70,"message":"Installing update"}
            2021-03-16T07:40:49.069Z box:shell update spawn: /usr/bin/sudo -S /home/yellowtent/box/src/scripts/update.sh /tmp/box-1465958658
            2021-03-16T07:40:49.081Z box:shell update (stdout): Updating Cloudron with /tmp/box-1465958658
            
            2021-03-16T07:40:49.082Z box:shell update (stdout): => reset service cloudron-updater status (of previous update)
            
            2021-03-16T07:40:49.085Z box:shell update (stdout): => Run installer.sh as cloudron-updater.
            
            2021-03-16T07:40:49.089Z box:shell update (stdout): => starting service (ubuntu 16.04) cloudron-updater. see logs using journalctl -u cloudron-updater
            
            2021-03-16T07:40:49.094Z box:shell update (stdout): Failed to start transient service unit: Unit cloudron-updater.service already exists.
            
            2021-03-16T07:40:49.094Z box:shell update (stdout): Failed to install cloudron. See log for details
            
            2021-03-16T07:40:49.094Z box:shell update code: 1, signal: null
            2021-03-16T07:40:49.097Z box:taskworker Task took 2447.75 seconds
            2021-03-16T07:40:49.097Z box:tasks setCompleted - 6395: {"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:66:17)\n    at ChildProcess.emit (events.js:198:13)\n    at ChildProcess.EventEmitter.emit (domain.js:448:20)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"Spawn Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
            2021-03-16T07:40:49.097Z box:tasks 6395: {"percent":100,"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:66:17)\n    at ChildProcess.emit (events.js:198:13)\n    at ChildProcess.EventEmitter.emit (domain.js:448:20)\n    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"Spawn Error","details":{},"message":"update exited with code 1 signal null","code":1,"signal":null}}
            

            Also, doing journalctl -u cloudron-updater does return -- No entries --.

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

              @madrush Right, I guess this is Ubuntu 16 as well. There seems to some bug in systemd which makes the updater task not run. To fix:

              • First, reboot the server.
              • sudo purge-old-kernels <- this seems to take a bit at times since it accumulates a lot of stable kernels. It also keeps asking to keep config (you can just choose the default).
              • sudo apt autoremove
              • sudo apt autoclean
              • Then, try to update
              M 1 Reply Last reply Reply Quote 2
              • M
                madrush @girish last edited by

                @girish That did the trick. Thanks!

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