Importing existing backup in new app instance fails

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

[imc67]

@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

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

[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

[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_Matt]

@nebulon
we just migrate our main server to a new one, and we got the same issue.

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

[girish]

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

[girish]

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

[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_Matt]

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