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. FreeScout
  3. Importing existing backup in new app instance fails

Importing existing backup in new app instance fails

Scheduled Pinned Locked Moved Solved FreeScout
21 Posts 4 Posters 2.4k Views 4 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.
  • imc67I imc67

    @nebulon very good you moved this to a new thread.

    On another Cloudron I just migrated (only migrate with no single module) a Freescout instance (this one is rather new, only 4 weeks and only few emails) and that went perfect.

    The Cloudron/Freescout app that has the issues is already from the very first version and updates went fine.
    The app is 1.98GB in size according to Cloudron System Info, however, when I calculate size on SCP login, the /appsdata/[ID]/data/ folder is 2.11GB and the mysqldump is 189.8MB.

    If you use the webterminal into the app, can you see /app/code/storage being a symlink to /app/data/storage ?

    In the current app it is symlink (bright blue is symlink I guess) together with Modules.

    I don't keep up the migrated Freescout up for longer than a few minutes because that one is fully functional and fetches email and response with autoanswers. Is there an easy way to stop cron to prevent mixing of data between 2 of the same instances?

    nebulonN Offline
    nebulonN Offline
    nebulon
    Staff
    wrote on last edited by
    #12

    @imc67 right you would have to stop the app to avoid interfering with the mailboxes.

    just out of curiosity, did you restart the failing app after import? I don't quite get why storage/framework/cache/ would not be writeable, if the symlinks are there.

    You can also try to run sudo chown -R www-data:www-data /app/data since that would set the permissions for the files in the symlinked files. Although that would be done on an app restart anyways.

    imc67I 2 Replies Last reply
    0
    • nebulonN nebulon

      @imc67 right you would have to stop the app to avoid interfering with the mailboxes.

      just out of curiosity, did you restart the failing app after import? I don't quite get why storage/framework/cache/ would not be writeable, if the symlinks are there.

      You can also try to run sudo chown -R www-data:www-data /app/data since that would set the permissions for the files in the symlinked files. Although that would be done on an app restart anyways.

      imc67I Offline
      imc67I Offline
      imc67
      translator
      wrote on last edited by
      #13

      @nebulon

      this time no such 755

      After the second try (see above) there was no such error anymore, so I don’t think we should look into that direction. But also don’t know in what direction to think either πŸ€” πŸ˜‚

      1 Reply Last reply
      0
      • nebulonN nebulon

        @imc67 right you would have to stop the app to avoid interfering with the mailboxes.

        just out of curiosity, did you restart the failing app after import? I don't quite get why storage/framework/cache/ would not be writeable, if the symlinks are there.

        You can also try to run sudo chown -R www-data:www-data /app/data since that would set the permissions for the files in the symlinked files. Although that would be done on an app restart anyways.

        imc67I Offline
        imc67I Offline
        imc67
        translator
        wrote on last edited by
        #14

        @nebulon hope you have time somewhere coming days to debug this issue together?

        Summary:

        1. Tried to follow you steps 5 times to migrate a Freescout instance (1.98GB + 189.8MB mysqldump, since the first version on Cloudron)
        2. Only the 1st time not only failed the "CSS/scripts" but also somehow the symlink.
        3. All the other 4 times only failed with a GUI without (looks like) CSS and some buttons (scripts?) are not working (login is possible with LDAP) see screenshot
        4. A migration of Freescout on another Cloudron went fine (only 4 weeks old instance with hardly any mails).
        5. Just as a debug scenario I just cloned the current app and that also didn't work, same result with GUI/CSS/script.

        Schermafbeelding 2021-02-16 om 09.12.16.png

        imc67I 1 Reply Last reply
        1
        • imc67I imc67

          @nebulon hope you have time somewhere coming days to debug this issue together?

          Summary:

          1. Tried to follow you steps 5 times to migrate a Freescout instance (1.98GB + 189.8MB mysqldump, since the first version on Cloudron)
          2. Only the 1st time not only failed the "CSS/scripts" but also somehow the symlink.
          3. All the other 4 times only failed with a GUI without (looks like) CSS and some buttons (scripts?) are not working (login is possible with LDAP) see screenshot
          4. A migration of Freescout on another Cloudron went fine (only 4 weeks old instance with hardly any mails).
          5. Just as a debug scenario I just cloned the current app and that also didn't work, same result with GUI/CSS/script.

          Schermafbeelding 2021-02-16 om 09.12.16.png

          imc67I Offline
          imc67I Offline
          imc67
          translator
          wrote on last edited by
          #15

          @nebulon hopefully you can find time this week to debug together as we now have the premium LDAP plug-in but can’t use it πŸ˜”

          nebulonN 1 Reply Last reply
          0
          • imc67I imc67

            @nebulon hopefully you can find time this week to debug together as we now have the premium LDAP plug-in but can’t use it πŸ˜”

            nebulonN Offline
            nebulonN Offline
            nebulon
            Staff
            wrote on last edited by
            #16

            @imc67 actually I have tried again but was not able to reproduce your issue to be able to debug this. Maybe this is really somehow related to the backup size of your instance πŸ˜• Not sure how to debug this properly.

            MooCloud_MattM 1 Reply Last reply
            0
            • nebulonN nebulon

              @imc67 actually I have tried again but was not able to reproduce your issue to be able to debug this. Maybe this is really somehow related to the backup size of your instance πŸ˜• Not sure how to debug this properly.

              MooCloud_MattM Offline
              MooCloud_MattM Offline
              MooCloud_Matt
              wrote on last edited by MooCloud_Matt
              #17

              @nebulon
              we just migrate our main server to a new one, and we got the same issue.
              1048e82e-cb14-471e-93e9-1be3c25f8912-image.png

              i will message you the link to our instance so you can check that out.

              Matteo. R.
              Founder and Tech-Support Manager.
              MooCloud MSP
              Swiss Managed Service Provider

              girishG 1 Reply Last reply
              0
              • MooCloud_MattM MooCloud_Matt

                @nebulon
                we just migrate our main server to a new one, and we got the same issue.
                1048e82e-cb14-471e-93e9-1be3c25f8912-image.png

                i will message you the link to our instance so you can check that out.

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

                @moocloud_matt thanks for the access! I was able to figure out this mystery...

                @nebulon We don't store symlinks in backups and it seems that there is a bunch of them in /app/data/public-modules. Not sure who creates them but a restore doesn't create those symlinks back. You couldn't reproduce it because you I am guessing you used tgz backup which keeps symlinks inside it but rsync backup will not store symlinks (there is no way to store symlinks in object storage without hacks). So, the package has to be fixed create those symlinks on startup as needed.

                1 Reply Last reply
                0
                • girishG Offline
                  girishG Offline
                  girish
                  Staff
                  wrote on last edited by
                  #19

                  I have fixed the code in 6.2 to preserve symlinks in rsync backups/restore

                  imc67I 1 Reply Last reply
                  1
                  • girishG girish

                    I have fixed the code in 6.2 to preserve symlinks in rsync backups/restore

                    imc67I Offline
                    imc67I Offline
                    imc67
                    translator
                    wrote on last edited by
                    #20

                    @girish said in Importing existing backup in new app instance fails:

                    I have fixed the code in 6.2 to preserve symlinks in rsync backups/restore

                    I can confirm that with 6.2.2 the backup and restore of FreeScout does work!

                    MooCloud_MattM 1 Reply Last reply
                    2
                    • imc67I imc67

                      @girish said in Importing existing backup in new app instance fails:

                      I have fixed the code in 6.2 to preserve symlinks in rsync backups/restore

                      I can confirm that with 6.2.2 the backup and restore of FreeScout does work!

                      MooCloud_MattM Offline
                      MooCloud_MattM Offline
                      MooCloud_Matt
                      wrote on last edited by
                      #21

                      @imc67
                      yep, @girish fixed in seconds, like a superhero! was an issue with the system link in rsync, and I discovered the output of the error was on the app log file, not on the container that's why we couldn't find anything on the log in Cloudron initially.

                      Matteo. R.
                      Founder and Tech-Support Manager.
                      MooCloud MSP
                      Swiss Managed Service Provider

                      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