ok, thank you.
I did that, upgraded successfully to 1.15

/usr/src/s3ql-1.15# s3qladm --version
S3QL 1.15

Then ran the s3qladm upgrade <s3 bucket> with this output:

s3qladm upgrade s3://s3ql-test2
Enter backend login: 
Enter backend password: 
Enter file system encryption passphrase: 
Getting file system parameters..
Ignoring locally cached metadata (outdated).
File system already at most-recent revision

This bucket was created using s3ql v1.12 so I was a little confused by the 
"Fyle system already at most-recent revision' output.
Could this have anything to do with my failed attempt to upgrade it from 
1.2 to 2.9 already.
Outside of that question, I then attempted to upgrade again on my 2.9 host 
and got the following output:

s3qladm upgrade s3://s3ql-test2
Enter backend login: 
Enter backend passphrase: 
Enter file system encryption passphrase: 
Uncaught top-level exception:
Traceback (most recent call last):
  File "/usr/bin/s3qladm", line 9, in <module>
    load_entry_point('s3ql==2.9', 'console_scripts', 's3qladm')()
  File "/usr/lib/s3ql/s3ql/adm.py", line 94, in main
    backend = get_backend(options)
  File "/usr/lib/s3ql/s3ql/backends/__init__.py", line 42, in get_backend
    return get_backend_factory(options, plain)()
  File "/usr/lib/s3ql/s3ql/backends/__init__.py", line 189, in 
get_backend_factory
    data_pw = tmp_backend['s3ql_passphrase']
  File "/usr/lib/s3ql/s3ql/backends/common.py", line 267, in __getitem__
    return self.fetch(key)[0]
  File "/usr/lib/s3ql/s3ql/backends/common.py", line 335, in fetch
    return self.perform_read(do_read, key)
  File "/usr/lib/s3ql/s3ql/backends/common.py", line 58, in wrapped
    return method(*a, **kw)
  File "/usr/lib/s3ql/s3ql/backends/common.py", line 308, in perform_read
    with self.open_read(key) as fh:
  File "/usr/lib/s3ql/s3ql/backends/common.py", line 612, in open_read
    metadata = self._unwrap_meta(fh.metadata)
  File "/usr/lib/s3ql/s3ql/backends/common.py", line 571, in _unwrap_meta
    raise ObjectNotEncrypted()
s3ql.backends.common.ObjectNotEncrypted

any help you can supply with this is greatly appreciated.

Thanks




On Tuesday, July 29, 2014 5:30:46 PM UTC-7, Nikolaus Rath wrote:
>
> On 07/28/2014 11:28 AM, jaredk51 wrote: 
> [ Upgrading from 1.12 to 2.9 ] 
> > Curious if this is possible. 
>
> No, you have to do an intermediate step with S3QL 1.15. 
>
>
> Best, 
> -Nikolaus 
>
> -- 
> GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F 
> Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F 
>
>              »Time flies like an arrow, fruit flies like a Banana.« 
>

-- 
You received this message because you are subscribed to the Google Groups 
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to