Results 1 to 5 of 5

Thread: Unknown S3 error with Swift S3 (Openstack)

  1. #1
    Join Date
    Jun 2013
    Posts
    3

    Default Unknown S3 error with Swift S3 (Openstack)

    Hi, it is my first post and just a few days with amanda.

    I'm trying to configure backups on Openstack's Swift using S3. I have the following error:

    Code:
    $ amlabel DailySet1 DailySet1-1 slot 1
    Reading label...
    Error reading volume label: While trying to read tapestart header: Unknown S3 error (None) (HTTP 403)
    Not writing label.
    amlabel.log has this:

    Code:
    Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: pid 23948 ruid 63998 euid 63998 version 3.3.3: start at Fri Jun 14 21:57:33 2013
    Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Arguments: DailySet1 DailySet1-1 slot 1
    Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: pid 23948 ruid 63998 euid 63998 version 3.3.3: rename at Fri Jun 14 21:57:33 2013
    Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Using state file: /etc/amanda/DailySet1/s3-statefile
    Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: S3 driver using bucket 'xxxxxxxxxxxxxxxxxxxxxxxx-backups', prefix 'DailySet1/slot-01'
    Fri Jun 14 21:57:33 2013: thd-0x13b5400: amlabel: Create 1 threads
    Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: GET https://xxxxxxxxxxxxxxx.com:443/xxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1%2Fslot-01special-tapestart failed with 403/None
    Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: Device s3:xxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1/slot-01 error = 'While trying to read tapestart header: Unknown S3 error (None) (HTTP 403)'
    Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: Device s3:xxxxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1/slot-01 setting status flag(s): DEVICE_STATUS_DEVICE_ERROR, and DEVICE_STATUS_VOLUME_ERROR
    Fri Jun 14 21:57:35 2013: thd-0x13b5400: amlabel: pid 23948 finish time Fri Jun 14 21:57:35 2013
    My amanda.conf is:

    Code:
    org "DailySet1"
    infofile "/srv/amanda/state/curinfo"
    logdir "/srv/amanda/state/log"
    indexdir "/srv/amanda/state/index"
    dumpuser "amandabackup"
    mailto "operations@xxxxxxxxxx.com"
    
    define tapetype S3 {
        comment "S3 Bucket"
        length 100 gigabytes # Bucket size
    }
    
    device_property "S3_ACCESS_KEY" "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"    # Your S3 Access Key
    device_property "S3_SECRET_KEY" "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"    # Your S3 Secret Key
    
    device_property "S3_SSL" "ON"                                        # Curl needs to have S3 Certification Authority (Verisign today)
                                                                          # in its CA list. If connection fails, try setting this no NO
    device-property "SSL_CA_INFO" "/etc/amanda/xxxxxxxxx.ca-bundle"
    device-property "S3_HOST" "xxxxxxxxxxxxxxxxxxxxx:443"
    
    tpchanger "chg-multi:s3:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx-backups/DailySet1/slot-{01,02,03,04,05,06,07,08,09,10}" # Number of tapes in your "tapecycle"
    changerfile  "s3-statefile"
    tapetype S3
    
    define dumptype simple-gnutar-remote {
        auth "ssh"
        ssh_keys "/etc/amanda/MyConfig/ssh-key"
        compress none
        program "GNUTAR"
    }
    
    holdingdisk hd1 {
        directory "/srv/amanda/holding"
        use 200 gbytes
        chunksize 1 mbyte
    }

    Using s3cmd and the same access/secret i have full permissions on the S3 storage, so i cannot figure out why i'm getting a 403 error.

    Thank you.
    Last edited by baskin; June 14th, 2013 at 02:10 PM.

  2. #2
    Join Date
    Aug 2008
    Posts
    184

    Default

    Amanda community edition has not been integrated with OpenStack Swift.

    OpenStack Swift is supported by Amanda Enterprise Edition. If you would like to consider the supported version, you can contact Zmanda sales at [email]zsales@zmanda.com[/email]

  3. #3
    Join Date
    Jun 2013
    Posts
    3

    Default

    On 3.3.2 release notes there is:
    Works with swift and google storage.
    I'm using 3.3.3. So community edition works or not with Swift? I'm confused...

  4. #4
    Join Date
    Aug 2008
    Posts
    184

    Default

    It appears an older version of swift api may have been tested at some point with the community edition. It has not been updated/tested recently.

  5. #5
    Join Date
    Jun 2013
    Posts
    3

    Default

    Ok. Thanks for the clarification. I hope that the community edition will support S3 (and Swift S3) soon.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •