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 Nextcloud App "not responding" after upgrading to Ubuntu 22.04

    Support
    upgrade ubuntu
    6
    18
    663
    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
      andreasb last edited by girish

      Dear Cloudron Team

      upgrading the instance from Ubuntu 20.04 to 22.04 following the corresponding tutorial worked as described. Since then however, Nextcloud App shows "not responding", apparently because the corresponding Redis Service doesn't start either. I tried restarting NC + Redis independently, as well as rebooting the server, all without success. I as well increased memory limit to Redis and put the service in "recovery mode". This without visible effect. The redis log shows the following message repeatedly:

      Jun 22 21:02:25 cat: /sys/fs/cgroup/memory.max: No such file or directory
      

      Any ideas, anybody?

      A girish 3 Replies Last reply Reply Quote 0
      • A
        ApplegateR @andreasb last edited by

        @andreasb we told that we can't upgrade 22.04 just yet because it wasn't supported.

        Richard Applegate
        Anthem Coffee and Tea
        The Joint Chiropractic
        IT/Administrator Server/Network

        jdaviescoates A 2 Replies Last reply Reply Quote 1
        • girish
          girish Staff @andreasb last edited by

          @andreasb Which cloudron version are you on?

          (The issue has to do with cgroup v1 / v2 detection)

          A 1 Reply Last reply Reply Quote 0
          • jdaviescoates
            jdaviescoates @ApplegateR last edited by

            @ApplegateR indeed, https://www.cloudron.io/get.html still currently says:

            Create a fresh Ubuntu Focal 20.04 x64 server and run these commands

            But the linked to guide https://docs.cloudron.io/guides/upgrade-ubuntu-22/ does talk about upgrading. Although looks like it might be a work in progress as it also says e.g.

            If you are still on Ubuntu 20, you must first upgrade to Ubuntu 20

            Calling @staff to look into this and clarify 🙂

            I use Cloudron with Gandi & Hetzner

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

              @jdaviescoates Ubuntu 22 is mostly stable and working but really no rush to update. There is no active issue on Ubuntu 22, I am aware of.

              1 Reply Last reply Reply Quote 1
              • A
                andreasb @girish last edited by

                @girish Cloudron 7.2.4

                girish 1 Reply Last reply Reply Quote 0
                • A
                  andreasb @ApplegateR last edited by

                  @ApplegateR didn't read that anywhere. Let me know if you'd like some information from that machine. If not, I will go back to the snapshot in that case later today.

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

                    @andreasb thanks! I think the issue is that redis is not starting on ubuntu 22.04. This was already fixed . Can you please check docker images output and check for tag 3.3.0 of redis:

                    cloudron/redis                       3.3.0                       2187af39ff74   8 weeks ago    2.24GB
                    

                    Then, docker ps -a should have something like:

                    2d3003643201   cloudron/redis:3.3.0                                           "/app/code/start.sh"     27 minutes ago   Up 7 minutes                                                                              redis-31ce4921-9b37-41bb-903c-aff587955c00
                    

                    The 31ce... is the app id of nextcloud. And that redis is using 3.3.0..

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

                      @andreasb I managed to reproduce this.

                      To fix this:

                      # sed -e 's/"version": ".*",/"version":"50.0.0",/' -i /home/yellowtent/platformdata/INFRA_VERSION
                      # systemctl restart box
                      

                      The issue is that Ubuntu 22 uses cgroups v2 by default. Containers have to be re-recreated to recognize this change. Changing the infra version triggers a container re-create. Note that it will take a bit for the containers to get re-created. The UI will show "configuring" for all the apps and they will come up one by one.

                      I have fixed the guide accordingly.

                      A humptydumpty necrevistonnezr 3 Replies Last reply Reply Quote 1
                      • A
                        andreasb @girish last edited by

                        @girish thx for your support, rebuilding the containers did the job: after restarting, both Redis + NC are up and running again!

                        1 Reply Last reply Reply Quote 0
                        • Topic has been marked as a question  nebulon nebulon 
                        • Topic has been marked as solved  nebulon nebulon 
                        • humptydumpty
                          humptydumpty @girish last edited by

                          @girish When does Cloudron support end for Ubuntu 20.04?

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

                            @humptydumpty until canonical supports it. That will be for quite a while, see https://ubuntu.com/about/release-cycle

                            1 Reply Last reply Reply Quote 2
                            • necrevistonnezr
                              necrevistonnezr @girish last edited by

                              @girish said in Nextcloud App "not responding" after upgrading to Ubuntu 22.04:

                              @andreasb I managed to reproduce this.

                              To fix this:

                              # sed -e 's/"version": ".*",/"version":"50.0.0",/' -i /home/yellowtent/platformdata/INFRA_VERSION
                              # systemctl restart box
                              

                              The issue is that Ubuntu 22 uses cgroups v2 by default. Containers have to be re-recreated to recognize this change. Changing the infra version triggers a container re-create. Note that it will take a bit for the containers to get re-created. The UI will show "configuring" for all the apps and they will come up one by one.

                              I have fixed the guide accordingly.

                              Somehow, this doesn't persist. After a reboot, I see

                              {
                                  "version": "49.0.0",
                                  "baseImages": [
                                      {
                                          "repo": "cloudron/base",
                                          "tag": "cloudron/base:3.2.0@sha256:[REDACTED]"
                                      }
                                  ],
                              

                              in /home/yellowtent/platformdata/INFRA_VERSION

                              And the mail service does not start.
                              The error log shows:

                              Jun 26 18:25:59 cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory
                              
                              girish 1 Reply Last reply Reply Quote 0
                              • girish
                                girish Staff @necrevistonnezr last edited by

                                @necrevistonnezr It's not supposed to persist. It's just a "hack" to make the code recreate all the containers.

                                The mail container not starting is indeed a bug when solr/full text search is enabled. You can disable this temporarily.

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

                                  @girish How do I stop Solr in the terminal? I can't stop it in the dashboard - it just shows a spinning circle...

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

                                    @necrevistonnezr can you please try this one liner - https://git.cloudron.io/cloudron/box/-/commit/104bdaf76b1c66b6b7523e3bef0e61f8e18e86a4 and then systemctl restart box.

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

                                      @girish If that replacement should go into /home/yellowtent/platformdata/INFRA_VERSION - no, mail service still not working and showing the same error, even after a reboot.

                                      Jun 27 05:50:14 cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory
                                      Jun 27 05:50:23 cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory
                                      Jun 27 05:50:38 cat: /sys/fs/cgroup/memory/memory.limit_in_bytes: No such file or directory
                                      

                                      EDIT: I guess that replacement should go into /home/yellowtent/box/src/infra_version.js - but after a restart of box, still not running...

                                      EDIT 2: After 30 minutes or so, mail service is running again!

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

                                        @necrevistonnezr said in Nextcloud App "not responding" after upgrading to Ubuntu 22.04:

                                        EDIT: I guess that replacement should go into /home/yellowtent/box/src/infra_version.js - but after a restart of box, still not running...

                                        Yes, that's the correct place to fix it!

                                        I will add a warning to our docs that updating to ubuntu 22 when using FTS feature does not work out of the box / without patching until 7.3.

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