dietpi-backup log is empty

Hi

just realized that on the latest release the backup log is empty. Previously at the end a dialog box was shown with the log now it only shows, see screenshot.
Release notes state that:
Transfer logs are now done to dietpi-backup.log inside of the backup directory. This way they remain persistent even if DietPi-RAMlog is enabled and can be reviewed at a later time.

BUT the log there shows the same as in the attached screenshot…

means the log file inside your backup locations is empty?

I get this:

 DietPi-Backup
─────────────────────────────────────────────────────
 Mode: Backup

[  OK  ] DietPi-Backup | mkdir -p /mnt/dd6b05a5-a3bb-429a-95a8-b2cf5189f7ff/dietpi-backup/data
[ SUB1 ] DietPi-Services > stop
[  OK  ] DietPi-Services | stop : cron
[  OK  ] DietPi-Services | stop : webmin
[  OK  ] DietPi-Services | stop : netdata
[  OK  ] DietPi-Services | stop : emby-server
[  OK  ] DietPi-Services | stop : plexmediaserver
[  OK  ] DietPi-Services | stop : tautulli
[ INFO ] DietPi-Backup | Checking for required APT packages: rsync
[  OK  ] DietPi-Backup | All required APT packages are already installed.
[  OK  ] DietPi-Backup | Free space check: path=/mnt/dd6b05a5-a3bb-429a-95a8-b2cf5189f7ff/dietpi-backup/data | available=204553 MiB | required=704 MiB
[ INFO ] DietPi-Backup | Backup to /mnt/dd6b05a5-a3bb-429a-95a8-b2cf5189f7ff/dietpi-backup in progress, please wait...
rsync: [client] failed to open log-file /mnt/dietpi-backup/dietpi-backup.log: No such file or directory (2)
Ignoring "log file" setting.
sending incremental file list
     38,746,731   0%   33.50MB/s    0:00:01 (xfr#24, ir-chk=1000/183563)
deleting var/lib/emby/metadata/library/50/5027391f7903542b712ba598dbf8e834/poster.jpg
deleting var/lib/emby/metadata/library/50/5027391f7903542b712ba598dbf8e834/
    283,886,443   1%    7.36MB/s    0:00:36 (xfr#101, to-chk=0/755703)

sent 314,425,867 bytes  received 346,701 bytes  8,393,935.15 bytes/sec
total size is 28,133,826,243  speedup is 89.38
[ SUB1 ] DietPi-Services > start
[  OK  ] DietPi-Services | start : tautulli
[  OK  ] DietPi-Services | start : plexmediaserver
[  OK  ] DietPi-Services | start : emby-server
[  OK  ] DietPi-Services | start : netdata
[  OK  ] DietPi-Services | start : webmin
[  OK  ] DietPi-Services | start : cron
[  OK  ] DietPi-Backup: Backup | Completed

The issue seems to be here:

[ INFO ] DietPi-Backup | Backup to /mnt/dd6b05a5-a3bb-429a-95a8-b2cf5189f7ff/dietpi-backup in progress, please wait...
rsync: [client] failed to open log-file /mnt/dietpi-backup/dietpi-backup.log: No such file or directory (2)
Ignoring "log file" setting.

Current backup and restore location: /mnt/dd6b05a5-a3bb-429a-95a8-b2cf5189f7ff/dietpi-backup

so this: rsync: [client] failed to open log-file /mnt/dietpi-backup/dietpi-backup.log: No such file or directory (2)
make sense as the backup is not there!

indeed, probably an issue on the script. I need to recheck with the developer. Thy for sharing the issue btw.

“Glad” to report. Let me know if there is a fix.

Thx!

question: is there a log file available inside backup location?

ls -la /mnt/dd6b05a5-a3bb-429a-95a8-b2cf5189f7ff/dietpi-backup

the error is not about creating the backup log. It’s more an issue of rsync not being able to backup the file.

Here is what’s inside:

P.S: This log file is created by the backup job.

P.P.S. I had the new automatic cron backups ON. Turned them off…

Don’t know if this caused it but this was the only thing I changed in the config after installed the new dietpi-update

no issue seems to be introduced with the last update. Will submit a GitHub issue

I have 5 Dietpi installations running:
2 pi4
2 vmware vm’2
1 x86 pc

Only the 2 vm’2 give no error because I se the default path: /mnt/dietpi-backup/data
The 2 pie’s and the pc habve external backup storage and show this issue.

Perhaps this helps.

GitHub issue created https://github.com/MichaIng/DietPi/issues/4967