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
  • 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 | Demo | Docs | Install
  1. Cloudron Forum
  2. Support
  3. Nextcloud App "not responding" after upgrading to Ubuntu 22.04

Nextcloud App "not responding" after upgrading to Ubuntu 22.04

Scheduled Pinned Locked Moved Solved Support
upgradeubuntu
18 Posts 6 Posters 3.2k Views 6 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.
  • A ApplegateR

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

    A Offline
    A Offline
    andreasb
    wrote on last edited by
    #7

    @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
    0
    • A andreasb

      @girish Cloudron 7.2.4

      girishG Offline
      girishG Offline
      girish
      Staff
      wrote on last edited by
      #8

      @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
      0
      • A andreasb

        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?

        girishG Offline
        girishG Offline
        girish
        Staff
        wrote on last edited by girish
        #9

        @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 humptydumptyH necrevistonnezrN 3 Replies Last reply
        1
        • girishG 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 Offline
          A Offline
          andreasb
          wrote on last edited by
          #10

          @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
          0
          • nebulonN nebulon marked this topic as a question on
          • nebulonN nebulon has marked this topic as solved on
          • girishG 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.

            humptydumptyH Offline
            humptydumptyH Offline
            humptydumpty
            wrote on last edited by
            #11

            @girish When does Cloudron support end for Ubuntu 20.04?

            girishG 1 Reply Last reply
            1
            • humptydumptyH humptydumpty

              @girish When does Cloudron support end for Ubuntu 20.04?

              girishG Offline
              girishG Offline
              girish
              Staff
              wrote on last edited by
              #12

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

              1 Reply Last reply
              2
              • girishG 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.

                necrevistonnezrN Offline
                necrevistonnezrN Offline
                necrevistonnezr
                wrote on last edited by
                #13

                @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
                
                girishG 1 Reply Last reply
                0
                • necrevistonnezrN necrevistonnezr

                  @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
                  
                  girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #14

                  @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.

                  necrevistonnezrN 1 Reply Last reply
                  0
                  • girishG girish

                    @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.

                    necrevistonnezrN Offline
                    necrevistonnezrN Offline
                    necrevistonnezr
                    wrote on last edited by
                    #15

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

                    girishG 1 Reply Last reply
                    0
                    • necrevistonnezrN necrevistonnezr

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

                      girishG Offline
                      girishG Offline
                      girish
                      Staff
                      wrote on last edited by
                      #16

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

                      necrevistonnezrN 1 Reply Last reply
                      0
                      • girishG girish

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

                        necrevistonnezrN Offline
                        necrevistonnezrN Offline
                        necrevistonnezr
                        wrote on last edited by necrevistonnezr
                        #17

                        @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!

                        girishG 1 Reply Last reply
                        0
                        • necrevistonnezrN 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!

                          girishG Offline
                          girishG Offline
                          girish
                          Staff
                          wrote on last edited by
                          #18

                          @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
                          0
                          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