Have not found any post relating to this specific problem.
Problem: scheduled Duplicacy run commences, and then randomly stops. No obvious error messages are reported. Has happened before but I thought that Duplicacy had crashed and thought it was a fluke as it worked fine when triggered manually.
See below the setup. There is no failure or other error indicated.
The log for Backup_Windows contains the following; no indication as to what happened.
The general log file contains the following, starting with the Running of the backup at 00:05:
2023/05/15 00:05:01 Starting schedule Server backup_daily at scheduled time 2023-0515 00:05
2023/05/15 00:05:01 Created log file /logs/prune-20230515-000501.log
2023/05/15 00:05:01 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 [-log prune -storage Backup_Tower -all -threads 20 -keep 0:720 -keep 180:365 -keep 60:180 -keep 30:60 -keep 14:30 -keep 7:14 -keep 1:7]
2023/05/15 00:05:01 Set current working directory to /cache/localhost/all
2023/05/15 00:20:13 Failed to parse the stats file /root/.duplicacy-web/stats/schedules/Server backup_daily.stats: unexpected end of JSON input
2023/05/15 00:20:13 Created log file /logs/backup-20230515-002013.log
2023/05/15 00:20:13 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 [-log backup -storage Backup_Tower -threads 20 -stats]
2023/05/15 00:20:13 Set current working directory to /cache/localhost/0
2023/05/15 00:21:07 Failed to parse the stats file /root/.duplicacy-web/stats/schedules/Server backup_daily.stats: unexpected end of JSON input
2023/05/15 00:21:07 Created log file /logs/backup-20230515-002107.log
2023/05/15 00:21:07 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 [-log backup -storage Backup_Tower -threads 20 -stats]
2023/05/15 00:21:07 Set current working directory to /cache/localhost/2
2023/05/15 00:21:14 Failed to parse the stats file /root/.duplicacy-web/stats/schedules/Server backup_daily.stats: unexpected end of JSON input
2023/05/15 00:21:14 Created log file /logs/backup-20230515-002114.log
2023/05/15 00:21:14 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 [-log backup -storage Backup_Tower -threads 20 -stats]
2023/05/15 00:21:14 Set current working directory to /cache/localhost/21
At 00:34:03 it appears to start Backup_Windows, and at 03:05:30 it issued the following error:
2023/05/15 00:34:03 Failed to parse the stats file /root/.duplicacy-web/stats/schedules/Server backup_daily.stats: unexpected end of JSON input
2023/05/15 00:34:03 Created log file /logs/backup-20230515-003403.log
2023/05/15 00:34:03 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.7.2 [-log backup -storage Backup_Tower -threads 20 -stats]
2023/05/15 00:34:03 Set current working directory to /cache/localhost/3
2023/05/15 03:05:30 Failed to get the value from the keyring: keyring/dbus: Error connecting to dbus session, not registering SecretService provider: exec: "dbus-launch": executable file not found in $PATH
2023/05/15 03:05:30 Temporary directory set to /cache
2023/05/15 03:05:30 Schedule Server backup_daily next run time: 2023-0516 00:05
2023/05/15 03:05:30 Schedule VAULT backup_daily next run time: 2023-0515 22:30
2023/05/15 03:05:30 Duplicacy Web Edition 1.7.2 (1B2557)
2023/05/15 03:05:30 Duplicacy CLI 2.7.2
Is this perhaps a time out error? I know that the backup in question is quite large at times, however it does not seem to be dependent on size as it has done full multiple TB backups no problem on the schedule before.
Logs:
logs.zip (172.6 KB)
Edit:
Backup completed fine when triggered manually.