CWP7: 0.9.8.1230

CWP7: 0.9.8.1230

What is the changelog?

CWP7: 0.9.8.1230.... Following this update, newbackup is taking a backup (/home/tmp_bak) but is not compressing it and placing it in the relevant folder.

Log entry

2026-06-15 10:13:07 Cleaned local backup file: /test/full/manual/accounts//username.tar.gz
2026-06-15 10:13:07 SAFE_CLEANUP_DIR: removing entire temp dir /home/backup_temp/.backup_temp
2026-06-15 10:13:07 Delete Directory
2026-06-15 10:13:07 OPTION NO_OTHER 1
2026-06-15 10:13:07 SAFE_CLEANUP_DIR: BLOCKED - no marker file in /home/backup_temp/.backup_temp, refusing to delete.
15 June 2026 10:13:07 There is no backup schedule for today
15 June 2026 10:13:07 SAFE_CLEANUP_DIR: BLOCKED - no marker file in /home/backup_temp/.backup_temp, refusing to delete.
2026-06-15 10:13:07 There is no backup schedule for today
2026-06-15 10:13:07 SAFE_CLEANUP_DIR: BLOCKED - no marker file in /home/backup_temp/.backup_temp, refusing to delete.
2026-06-15 10:13:07 TYPE FTP --> 0
2026-06-15 10:13:10 Backup Finished

I have the same problem about a week now.Version 0.9.8.1231.

I urgently contacted José, and he replied that an update is planned within a few hours to fix this problem.

0.9.8.1244 and the problem persists.

The log clearly shows that when it begins the backup process, while reaching the end of the first one in order it will successfully move and delete the tar.gz but it will also delete the marker file inside /home/tmp_bak/.backup_temp (the default temp folder, yours may differ) which gives the following message:
"SAFE_CLEANUP_DIR: BLOCKED - no marker file in /home/tmp_bak/.backup_temp, refusing to delete."

It should be really simple to fix but i cannot see/edit the backup_cron because i believe it is encrypted.

Either way, please fix this problem. I have been watching the backup because it fills up my disk space and i have to babysit it while the backup takes place.

Thank you

A solution that worked for me is to start the backup manually and as soon as the /home/tmp_bak/.backup_temp/.cwp_backup_marker file is created run "chattr +i .cwp_backup_marker" so that the file cannot be deleted.

This way the backup process will try to delete the .backup_temp folder as well as the marker file without success and then continue with the next account in line.

*(if, for some reason, you wish to delete the file you're going to have to run "chatt -i .cwp_backup_marker" and then rm it)

** this process could probably work without needing to run the backup process manually and then wait until the marker file is created, you could also run "touch /home/tmp_bak/.backup_temp/.cwp_backup_marker" and manually create the marker file. I followed the manually backup process so that i could have more control while testing if this works.