Cloudron Forum

Hi @nebulon,

Thank you for your last feedback.
I've finally found the issue.

While investigating further, I noticed that the rights on the backup folder were changed. (Probably during cleanup operations performed the week before the issue)
To resolve the issue, I changed the "prefix" in the backup settings so that a new backup folder has been created on the mountpoint with the good rights by the system.

It is now working as expected.

@jayonrails Maybe you can check the rights on the backup folder as well ?

Thank you again for your help.
Best Regards,

Hi,

I have the exact same issue than described.
Seems that happened after the last security update.

This is easily reproductible as it happens each time I manually initiate a backup.

{
  "taskId": "229",
  "errorMessage": "Error when checking for disk space: Error running df: df exited with code 1 signal null",
  "timedOut": false,
  "backupId": null
}

Here are box.log logs when issue happens :

2025-04-04T19:10:38.879Z box:shell tasks /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 230 /home/yellowtent/platformdata/logs/tasks/230.log 15 1024 -999
2025-04-04T19:10:38.921Z box:shell Running as unit: box-task-230.service

2025-04-04T19:10:40.216Z box:apphealthmonitor app health: 1 running / 0 stopped / 0 unresponsive
2025-04-04T19:10:40.356Z box:shell Finished with result: exit-code
Main processes terminated with: code=exited/status=50
Service runtime: 1.413s
CPU time consumed: 1.891s
Memory peak: 3.2M
Memory swap peak: 0B

2025-04-04T19:10:40.356Z box:shell Service box-task-230 failed to run

2025-04-04T19:10:40.365Z box:shell Service box-task-230 finished with exit code 1

2025-04-04T19:10:40.367Z box:shell tasks: /usr/bin/sudo -S -E /home/yellowtent/box/src/scripts/starttask.sh 230 /home/yellowtent/platformdata/logs/tasks/230.log 15 1024 -999 errored BoxError: tasks exited with code 1 signal null
    at ChildProcess.<anonymous> (/home/yellowtent/box/src/shell.js:137:19)
    at ChildProcess.emit (node:events:519:28)
    at ChildProcess._handle.onexit (node:internal/child_process:294:12) {
  reason: 'Shell Error',
  details: {},
  code: 1,
  signal: null
}

BR,