2.1.0b8 GUI shows Keychain access error even though the backup completes successfully

saspus     Feb 6 1:50AM 2018 GUI

Duplicacy configured as follows:

        "name": "sftpds01",
        "id": "alex-imac",
        "storage": "sftp://alex@DS01//Backups/duplicacy/",
        "encrypted": true,
        "no_backup": false,
        "no_restore": false,
        "no_save_password": false,
        "keys": {

There are no errors in the backup session log:

22:46:09.000    Command: duplicacy -background -log backup -stats -threads 8
22:46:09.398    Storage set to sftp://alex@DS01//Backups/duplicacy/
22:46:22.588    Last backup at revision 71 found
22:46:22.588    Indexing /Users/alex
22:46:22.588    Loaded 32 include/exclude pattern(s)
22:47:26.535    Use 8 uploading threads

<skipped lines starting with Packed ...>

22:47:36.419    Backup for /Users/alex at revision 72 completed
22:47:36.419    Files: 347222 total, 442,729M bytes; 39 new, 10,131K bytes
22:47:36.419    File chunks: 90437 total, 445,688M bytes; 2 new, 10,131K bytes, 5,060K bytes uploaded
22:47:36.419    Metadata chunks: 35 total, 202,652K bytes; 6 new, 51,268K bytes, 19,529K bytes uploaded
22:47:36.419    All chunks: 90472 total, 445,886M bytes; 8 new, 61,400K bytes, 24,589K bytes uploaded
22:47:36.419    Total running time: 00:01:26

Backup successfully completes, however after that the popup appears saying:

[22:47:36] /Users/alex Backup operation returned an error:
2018-02-05 22:46:09.426 duplicacy_osx_x64_2.1.0[21640:1342545] Keychain Get: Error Code: -25300
2018-02-05 22:46:09.427 duplicacy_osx_x64_2.1.0[21640:1342545] Keychain Get: Error Code: -25300

The keychain contains item "duplicacy" with account name "sftpds01_password" and ACL is set to allow access for duplicacy_osx_x64_2.1.0, "Confirm before allowing access" is ON and "Ask for Keychain password" is OFF

The application does not ask for the permission to access keychain (it only asked once) and instead reports errors, while still completing backup successfully.

gchen    Feb 6 10:52AM 2018

This is because the GUI version treats any stderr output from the CLI version as an error, which is right. In this case, the CLI version wanted to check the Keychain to see if an ssh password is provided; it printed out an error to stderr when it couldn't find it but continues to use key-based login.

I'll fix it in the next beta version which should be available later today.

Log in to comment
Copyright © Acrosync LLC 2016-2017