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 5.2 update failed

    Support
    redis update
    4
    8
    377
    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.
    • T
      Trankery last edited by girish

      Hi!

      I logged into cloudron this morning, and all the sudden, it kept giving me Nginx 500 Errors.

      Later I updated to the latest release of this week.

      The errors continued.

      Then I've realized that redis is missing from the system?!

      https://gyazo.com/23842f36afd19ff4561b83952cbee032

      Anyone able to help me out? This is a production server and we urgently need this fixed.

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

        @Trankery Can you check the server logs? The file /home/yellowtent/platformdata/logs/box.log has the logs. Do you see any errors?

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

          So there was a crash because of redis:

          invalid argument "NaN" for "-m, --memory" flag: invalid size: 'NaN'
          See 'docker run --help'.
          
              at ChildProcess.exithandler (child_process.js:294:12)
              at ChildProcess.emit (events.js:198:13)
              at maybeClose (internal/child_process.js:982:16)
              at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
            killed: false,
            code: 125,
            signal: null,
            cmd:
          
          1 Reply Last reply Reply Quote 1
          • girish
            girish Staff last edited by

            There is a bug that if the redis memory limit is adjusted before the platform code starts up, it crashes. This is because of a typo in the code 😞

            In the rare chance someone else hits this, just apply the one line change to /home/yellowtent/box/src/addons.js - https://git.cloudron.io/cloudron/box/-/commit/4ede765e1f9a1a89d497255465721b0b930db642 and then systemctl restart box.

            T 1 Reply Last reply Reply Quote 1
            • T
              Trankery @girish last edited by

              @girish No Idea how this happened! Sorry!

              1 Reply Last reply Reply Quote 0
              • G
                gml last edited by

                My whole cloudron was not really working after the update. I did a reboot, nothing really changed, System looked like this: Screenshot_2020-05-30.png

                After the fix from @girish and restart of box everything worked again.

                Hope you push a hotfix pretty soon for all others. Still wish for a GUI option to choose if i want auto or manually install system updates, just for cases like this (this exists for the apps and has existed for the cloudron itself in the past). Auto updates always have this bitter aftertaste of waking up next day and it could work or not work.

                1 Reply Last reply Reply Quote 1
                • valkalon
                  valkalon last edited by

                  Same here thanks for the fix @girish it worked! I got to say I was scared, glad you reacted so fast 😉

                  T 1 Reply Last reply Reply Quote 1
                  • T
                    Trankery @valkalon last edited by

                    @valkalon Cloudron support is still the best 😉

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