Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.


Backup failed for Radicale app, a command failed somehow but it seems fine when I run it myself about 20 minutes after it failed.


  • Hi guys,

    Coincidentally, I made a bunch of optimizations to my Radicale data, so it's possible this is a root cause however I have seen two backups already run by the system since I made those changes without any issues, so I'm not convinced this is necessarily related and may be more of a genuine coincidence. Noting this just in case though it is related though.

    I was notified my backup failed by Cloudron box, and I went to run the same command it claims failed on my terminal via SSH maybe 20 minutes later, and it returned data to me without any issues. Is this not a valid test though? And if it is a valid test, any ideas why this might happen? Many app backups were made yesterday while I was making these changes to the app data, and after it was all done. System backups have proceeded since that time too without issues, this is the first one that failed for me in a long time now.

    The command I ran is this one as it appeared to be the one failed according to the logs:
    du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c

    One thing I noticed is the specific file that couldn't be found according to the logs is a Radicale tmp file, so maybe this is just a one-off type of thing? Been running Radicale for at least 8 months or so without backup-related issues for it until today.

    Relevant log snippet below (paths changed of course for privacy reasons - I can email you the full content if you'd like @girish or @nebulon):

    Jun 06 13:46:46 box:backups dav.example.com Unable to backup { BoxError: Command failed: du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c
    cannot access '/home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c/data/collections/collection-root/username/Calendar/.Radicale.cache/item/.Radicale.tmp-2fqutg7l': No such file or directory
    at /home/yellowtent/box/src/backups.js:889:29
    at f (/home/yellowtent/box/node_modules/once/once.js:25:25)
    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:67:9)
    at ChildProcess.emit (events.js:198:13)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
    name: 'BoxError',
    reason: 'External Error',
    details: {},
    message:
    'Command failed: du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c\ndu: cannot access \'/home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c/data/collections/collection-root/username/Calendar/.Radicale.cache/item/.Radicale.tmp-2fqutg7l\': No such file or directory\n' }
    Jun 06 13:46:46 box:tasks setCompleted - 3920: {"result":null,"error":{"stack":"BoxError: Command failed: du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c\ndu: cannot access '/home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c/data/collections/collection-root/username/Calendar/.Radicale.cache/item/.Radicale.tmp-2fqutg7l': No such file or directory\n\n at /home/yellowtent/box/src/backups.js:889:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:67:9)\n at ChildProcess.emit (events.js:198:13)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"External Error","details":{},"message":"Command failed: du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c\ndu: cannot access '/home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c/data/collections/collection-root/username/Calendar/.Radicale.cache/item/.Radicale.tmp-2fqutg7l': No such file or directory\n"}}
    Jun 06 13:46:46 box:tasks 3920: {"percent":100,"result":null,"error":{"stack":"BoxError: Command failed: du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c\ndu: cannot access '/home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c/data/collections/collection-root/username/Calendar/.Radicale.cache/item/.Radicale.tmp-2fqutg7l': No such file or directory\n\n at /home/yellowtent/box/src/backups.js:889:29\n at f (/home/yellowtent/box/node_modules/once/once.js:25:25)\n at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:67:9)\n at ChildProcess.emit (events.js:198:13)\n at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)","name":"BoxError","reason":"External Error","details":{},"message":"Command failed: du -Dsb /home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c\ndu: cannot access '/home/yellowtent/appsdata/66b02693-2d00-46e0-9b9d-f2c1b623642c/data/collections/collection-root/username/Calendar/.Radicale.cache/item/.Radicale.tmp-2fqutg7l': No such file or directory\n"}}
    

  • Quick update: I just manually ran another system-wide backup and it was successful, so it seems it may have just been a one-off and probably won't happen again anytime soon, was likely just coincidental I was making a bunch of changes to it yesterday considering other system backups proceeded without issue since the time I made those changes. But I'd love to get a second-set of eyes for insight into if this is something I should fix to prevent it in the future or just a one-off type of thing that can safely be ignored.