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 Cloudron Auto update failed

    Support
    updates
    3
    5
    237
    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.
    • A
      alexwhughes last edited by girish

      Hello,

      Overnight I noted that my cloudron install failed to update. Status in Web UI was "update exited with code 1 signal null"

      The logs says :

      Aug 19 09:34:23 box:shell update (stdout): Running as unit: cloudron-updater.service
      Aug 19 09:34:23 box:shell update (stdout): cloudron-updater is still active. will check in 5 seconds
      Aug 19 09:34:28 box:shell update (stdout): => cloudron-updater has failed
      Aug 19 09:34:28 box:shell update code: 1, signal: null
      Aug 19 09:34:28 box:tasks setCompleted - 1747: {"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:64:17)\n at ChildProcess.emit (events.js:198:13)\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}}
      Aug 19 09:34:28 box:tasks 1747: {"percent":100,"result":null,"error":{"stack":"BoxError: update exited with code 1 signal null\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:64:17)\n at ChildProcess.emit (events.js:198:13)\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}}
      

      I can't make heads nor tails of what to do with that log. Is there a step I am missing

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

        @alexwhughes are you using Ubuntu 16 or 18?

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

          @alexwhughes If you are on Ubuntu 18, the logs are at /home/yellowtent/platformdata/logs/updater/cloudron-updater-{timestamp}.log. On Ubuntu 16, there are logs in journalctl -u cloudron-updater. Do you see any errors there? If it's dpkg errors, just run sudo dpkg --configure -a and try the update again.

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

            Also, which version of Cloudron are you currently on?

            1 Reply Last reply Reply Quote 0
            • J
              johan @girish last edited by

              @girish This solved it for me. Thanks!

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