"check" command fails with "Invalid options"

Support
#1

Hi,

I’m using the Web GUI 0.2.10 Beta on Linux.

My local backup jobs to disk are running fine and the subsequent copy to B2 Backblaze.

The only problem I have is that the check command no longer works and gives and “Invalid options” error. Do I have to many chunks for the check to work?

2019-05-07 19:00:09.897 INFO BACKUP_STATS Files: 121316 total, 622,963M bytes; 0 new, 0 bytes
2019-05-07 19:00:09.897 INFO BACKUP_STATS File chunks: 127337 total, 623,185M bytes; 0 new, 0 bytes, 0 bytes uploaded
2019-05-07 19:00:09.897 INFO BACKUP_STATS Metadata chunks: 8 total, 40,683K bytes; 0 new, 0 bytes, 0 bytes uploaded!
All chunks: 127345 total, 623,225M bytes; 0 new, 0 bytes, 0 bytes uploaded
2019-05-07 19:00:09.897 INFO BACKUP_STATS Total running time: 00:00:08

check-error-invalid-options
check-error-invalid-options.png1347×156 13.8 KB

Please help!

Cheers pdaemon

#2

Here is a link to a recent “check” logfile:
https://drive.google.com/file/d/13hjJR6h9H9vcyyckdVTXRmXQXBgkQs_z/view?usp=sharing

#3

~/.duplicacy-web/logs/duplicacy_web.log should have more info on why the check command failed.

#4

Hi gchen,

Here is something from the log file:

2019/05/07 12:00:01 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log check -storage Local-Disk-USB -a -tabular]
2019/05/07 12:00:01 Set current working directory to /mnt/Datastore/tmp/localhost/all
2019/05/07 12:00:01 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log backup -storage Local-Disk-USB -stats]
2019/05/07 12:00:01 Set current working directory to /mnt/Datastore/tmp/localhost/0
2019/05/07 12:00:01 Created log file /var/log/duplicacy/backup-20190507-120001.log
2019/05/07 12:00:01 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log backup -storage Local-Disk-USB -stats]
2019/05/07 12:00:01 Set current working directory to /mnt/Datastore/tmp/localhost/4
2019/05/07 12:00:10 Created log file /var/log/duplicacy/copy-20190507-120010.log
2019/05/07 12:00:10 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log copy -from Local-Disk-USB -to B2-Cloud -threads 12]
2019/05/07 12:00:10 Set current working directory to /mnt/Datastore/tmp/localhost/all

2019/05/07 12:21:12 Schedule backup-schedule next run time: 2019-0507 13:00
2019/05/07 13:00:01 Starting schedule backup-schedule at scheduled time 2019-0507 13:00
2019/05/07 13:00:01 Created log file /var/log/duplicacy/backup-20190507-130001.log
2019/05/07 13:00:01 Created log file /var/log/duplicacy/backup-20190507-130001.log
2019/05/07 13:00:01 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log backup -storage Local-Disk-USB -stats]
2019/05/07 13:00:01 Set current working directory to /mnt/Datastore/tmp/localhost/4
2019/05/07 13:00:01 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log backup -storage Local-Disk-USB -stats]
2019/05/07 13:00:01 Set current working directory to /mnt/Datastore/tmp/localhost/0
2019/05/07 13:00:38 Created log file /var/log/duplicacy/copy-20190507-130038.log
2019/05/07 13:00:38 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.1.2 [-log copy -from Local-Disk-USB -to B2-Cloud -threads 12]
2019/05/07 13:00:38 Set current working directory to /mnt/Datastore/tmp/localhost/all
**2019/05/07 13:02:23 The Duplicacy executable returned an error: exit status 2, exit code: 2**
**2019/05/07 13:02:25 Schedule check-schedule next run time: 2019-0508 00:00**


2019/05/07 13:21:31 Schedule backup-schedule next run time: 2019-0507 14:00
2019/05/07 14:00:01 Starting schedule backup-schedule at scheduled time 2019-0507 14:00
2019/05/07 14:00:01 Created log file /var/log/duplicacy/backup-20190507-140001.log
2019/05/07 14:00:01 Created log file /var/log/duplicacy/backup-20190507-140001.log

Cheers pdaemon

#5

I believe this is an out-of-memory error, and it has been fixed by Fix a memory issue that check -tabular uses too much memory with many… · gilbertchen/duplicacy@4b69c11 · GitHub and included in the 2.2.0 release. So if you simply restart the web GUI it will automatically download 2.2.0 and this issue should go away, assuming you didn’t set the cli_version key as explained in CLI 2.2.0 has been released (impact on the Web GUI).

1 Like
#6

Thanks gchen,

I’m running the check’s now with CLI 2.2.0 and I’ll let you know…

2019/05/08 06:06:14 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.2.0 [-log check -storage Local-Disk-USB -a -tabular]
2019/05/08 06:06:14 Set current working directory to /mnt/Datastore/tmp/localhost/all
2019/05/08 06:06:14 Running /root/.duplicacy-web/bin/duplicacy_linux_x64_2.2.0 [-log check -storage B2-Cloud -a -tabular]
2019/05/08 06:06:14 Set current working directory to /mnt/Datastore/tmp/localhost/all

Cheers pdaemon

#7

Hi gchen,

It looks like CLI 2.2.0 has fixed the problem. My “check” schedules are running as expected.

Thanks very much for your help!

Cheers pdaemon.

1 Like
#8

For anyone: Feel free to use the :heart: button on the posts that you found useful.

For the OP of any #support topic: you can mark the post that solved your issue by ticking the image box under the post. That of course may include your own post :slight_smile: