backup error: "undefined is not mounted"
-
Looking around in the box code:
grep -rin "is not mounted" src/storage/filesystem.js:86: if (result.mountpoint !== apiConfig.mountPoint) return callback(new BoxError(BoxError.FS_ERROR, `${apiConfig.mountPoint} is not mounted`)); src/storage/filesystem.js:88: if (result.mountpoint === '/') return callback(new BoxError(BoxError.FS_ERROR, `${apiConfig.backupFolder} is not mounted`)); src/storage/filesystem.js:317: if (!safe.child_process.execSync(`mountpoint -q -- ${apiConfig.mountPoint}`)) return callback(new BoxError(BoxError.BAD_FIELD, `${apiConfig.mountPoint} is not mounted`, { field: 'mountPoint' }));The
${apiConfig.mountPoint}/${apiConfig.backupFolder}=>apiConfigis from api endpoint{{baseUrl}}/settings/backup_configI assume.This api endpoint delivers:
{ "provider": "cifs", "format": "tgz", "memoryLimit": 838860800, "schedulePattern": "00 00 5 * * *", "retentionPolicy": { "keepWithinSecs": 604800 }, "prefix": "", "noHardlinks": false, "mountOptions": { "host": "-REDACTED-.your-storagebox.de", "remoteDir": "/backup/cloudron-backup", "username": "-REDACTED-", "password": "●●●●●●●●" }, "uploadPartSize": 10485760, "encryption": null, "mountStatus": { "state": "active", "message": "Mounted" } }There is no
backupFolderhere so either I am wrong with my guess about the api endpoint or something else.Hmmm more digging.
In
src/settings.jsdeleted line 425:backupConfig.mountPoint = '/mnt/cloudronbackup'; // hardcode the mountPoint for built-in mounts
This is a hint why I had to go with explicit /backup/cloudron-backupin https://forum.cloudron.io/topic/6529/shooting-a-cloudron-server-right-in-the-brain-i-deleted-appsdata-and-boxdata-by-accident because I am quite sure I never did this before.Like my work? Consider donating a drink. Cheers!
-
In
src/settings.jsdeleted line 425:backupConfig.mountPoint = '/mnt/cloudronbackup'; // hardcode the mountPoint for built-in mounts This is a hint why I had to go with explicit /backup/cloudron-backupin https://forum.cloudron.io/topic/6529/shooting-a-cloudron-server-right-in-the-brain-i-deleted-appsdata-and-boxdata-by-accident because I am quite sure I never did this before.@BrutalBirdie so you are essentially saying the
undefinedcomes from src/storage/filesystem.js:88 ?Do you know what we have to setup and how to reproduce this issue?
For the
/mnt/cloudronbackup, since there is only one backup backend supported, it made sense to hardcode this so it is less likely to clash with other directory names on the system. Did you hit any issue with this? -
In
src/settings.jsdeleted line 425:backupConfig.mountPoint = '/mnt/cloudronbackup'; // hardcode the mountPoint for built-in mounts This is a hint why I had to go with explicit /backup/cloudron-backupin https://forum.cloudron.io/topic/6529/shooting-a-cloudron-server-right-in-the-brain-i-deleted-appsdata-and-boxdata-by-accident because I am quite sure I never did this before.The error is definitely in these 3 patches.
wget https://git.cloudron.io/cloudron/box/-/commit/04b7c14fd71e65072f43ed008d9e8b598dd946ab.diff wget https://git.cloudron.io/cloudron/box/-/commit/8b9d821905b55c624084cb7665d8fbdb621a56e4.diff wget https://git.cloudron.io/cloudron/box/-/commit/a786fad3eed59e9ed141c7a3344466b61e280891.diffBecause when I set the backup to
no-opand then revert the changes:git apply -R a786fad3eed59e9ed141c7a3344466b61e280891.diff git apply -R 8b9d821905b55c624084cb7665d8fbdb621a56e4.diff git apply -R 04b7c14fd71e65072f43ed008d9e8b598dd946ab.diffAnd then setup my CIFS backup again, its working as intended.
Also regarding my previous post with explicit
/backup/cloudron-backupin the now reverted version I only have to do/backupagain -
Can you try updating to 7.1 and trying this? Not sure what the status of the "code" is with all these patches applied
Would be great to know if this is reproducible with 7.1 . What you can do is to take a VM snapshot and then update without taking a cloudron backup. -
Can you try updating to 7.1 and trying this? Not sure what the status of the "code" is with all these patches applied
Would be great to know if this is reproducible with 7.1 . What you can do is to take a VM snapshot and then update without taking a cloudron backup. -
@girish this is my next testing step.
@BrutalBirdie yes, please
I did make sure to test all the variety of backends in 7.1, but let me know. -
@BrutalBirdie yes, please
I did make sure to test all the variety of backends in 7.1, but let me know.Seems like after an upgrade to v7.1 there is no more issue.
So if you have to restore from
v7.0.4apply the 3 patches so you can restore Cloudron.
After the successful restore set the backup option toNo-Opaka. No Backup!
De-apply the patches in reverse order.git apply -R a786fad3eed59e9ed141c7a3344466b61e280891.diff git apply -R 8b9d821905b55c624084cb7665d8fbdb621a56e4.diff git apply -R 04b7c14fd71e65072f43ed008d9e8b598dd946ab.diffRestart the box.service
systemctl restart box.service
Then configure your backup again and make sure it works.Then do the upgrade. Do not disable the automatic backup before the upgrade.
-
Seems like after an upgrade to v7.1 there is no more issue.
So if you have to restore from
v7.0.4apply the 3 patches so you can restore Cloudron.
After the successful restore set the backup option toNo-Opaka. No Backup!
De-apply the patches in reverse order.git apply -R a786fad3eed59e9ed141c7a3344466b61e280891.diff git apply -R 8b9d821905b55c624084cb7665d8fbdb621a56e4.diff git apply -R 04b7c14fd71e65072f43ed008d9e8b598dd946ab.diffRestart the box.service
systemctl restart box.service
Then configure your backup again and make sure it works.Then do the upgrade. Do not disable the automatic backup before the upgrade.
@BrutalBirdie Can you confirm which version you are on, 7.1.0 or 7.1.1? I've hit this issue after restoring an instance that was on 7.1.0 already.
-
@BrutalBirdie Can you confirm which version you are on, 7.1.0 or 7.1.1? I've hit this issue after restoring an instance that was on 7.1.0 already.
I am on
v7.1.1- now
This issue is very specific!
If you run into this and feel not comfortable fixing it alone, do not hesitate to write a support ticket or here in the forum!The issue only appears after a specific error chain.
- You need to have a Cloudron
v7.0.4which needs to be fully restored - Then you get the first error https://forum.cloudron.io/topic/6494/restore-error-cannot-access-error-before-initialization
2.1. solved by applying the 3x patches - Restored Cloudron running now and throwing the
undefined is not mountederror when trying to backup
3.1. Still on versionv7.0.4you need to set backup option toNo-OpNo backup
3.2. De-apply the 3x patches in reverse order (like described above)
3.3. Restartbox.service-systemctl restart box.service
3.4. Configure your backup solution again and make sure it works as intended
3.5. Upgrade tov7.1.1and do not disable the pre-backup option
3.6. After the successful upgrade tov7.1.1everything works as expected again
- You need to have a Cloudron
-
I am on
v7.1.1- now
This issue is very specific!
If you run into this and feel not comfortable fixing it alone, do not hesitate to write a support ticket or here in the forum!The issue only appears after a specific error chain.
- You need to have a Cloudron
v7.0.4which needs to be fully restored - Then you get the first error https://forum.cloudron.io/topic/6494/restore-error-cannot-access-error-before-initialization
2.1. solved by applying the 3x patches - Restored Cloudron running now and throwing the
undefined is not mountederror when trying to backup
3.1. Still on versionv7.0.4you need to set backup option toNo-OpNo backup
3.2. De-apply the 3x patches in reverse order (like described above)
3.3. Restartbox.service-systemctl restart box.service
3.4. Configure your backup solution again and make sure it works as intended
3.5. Upgrade tov7.1.1and do not disable the pre-backup option
3.6. After the successful upgrade tov7.1.1everything works as expected again
@BrutalBirdie Actually for me the issue appeared after:
- Upgrading an instance to 7.1.0
- Doing a full backup (which worked fine)
- Restoring this instance on a new server (also worked fine) and shutting down the old server
- But then daily backups on the newly restored instance fail with the "undefined is not mounted" error.
I've been in touch with support about this. I've given them ssh access and wait to hear what they say but perhaps simply upgrading to 7.1.1 might solve it.
- You need to have a Cloudron
-
This was indeed a bug. Fixed in https://git.cloudron.io/cloudron/box/-/commit/2434e813836e7837162c1798794d04655227d9cf . Thanks a lot @avatar1024 . It will be part of 7.1.2
