I'm currently working on adding gpg encryption to my existing wal-e
backups. I've got it 90% working, everything is using the GPG key via env
variable, and backup-push and backup-fetch seem to be working fine.
As part of my last bit of testing, I set up a new replica, and had it
restore via backup-fetch. However, the new replica is trying to set up
replication, and failing on wal-fetch.
It seems wal-e is trying to use the history files, but at this point they
are not gpg encrypted, and I'm not sure where to go from here.
Sample logs:
wal_e.main INFO MSG: starting WAL-E
DETAIL: The subcommand is "wal-fetch".
STRUCTURED: time=2016-07-26T22:16:27.375126-00 pid=16146
wal_e.operator.backup INFO MSG: begin wal restore
STRUCTURED: time=2016-07-26T22:16:27.409769-00 pid=16146
action=wal-fetch
key=s3://example/wal-e/master-db/wal_005/0000000A.history.lzo
prefix=wal-e/master-db/ seg=0000000A.history state=begin
gpg: decrypt_message failed: eof
wal_e.blobstore.s3.s3_util WARNING MSG: could no longer locate object while
performing wal restore
DETAIL: The absolute URI that could not be located is s3:
//example/wal-e/master-db/wal_005/0000000A.history.lzo.
HINT: This can be normal when Postgres is trying to detect what
timelines are available during restoration.
STRUCTURED: time=2016-07-26T22:16:27.577055-00 pid=16146
lzop: <stdin>: not a lzop file
wal_e.operator.backup INFO MSG: complete wal restore
STRUCTURED: time=2016-07-26T22:16:27.678940-00 pid=16146
action=wal-fetch
key=s3://example/wal-e/master-db/wal_005/0000000A.history.lzo
prefix=wal-e/master-db/ seg=0000000A.history state=complete
wal_e.main INFO MSG: starting WAL-E
DETAIL: The subcommand is "wal-fetch".
STRUCTURED: time=2016-07-26T22:16:27.862291-00 pid=16167
wal_e.operator.backup INFO MSG: begin wal restore
STRUCTURED: time=2016-07-26T22:16:27.895236-00 pid=16167
action=wal-fetch
key=s3://example/wal-e/master-db/wal_005/00000009.history.lzo
prefix=wal-e/master-db/ seg=00000009.history state=begin
gpg: packet(2) with unknown version 79
lzop: <stdin>: not a lzop file
wal_e.blobstore.s3.s3_util WARNING MSG: retrying WAL file fetch from
unexpected exception
DETAIL: The exception type is <class 'wal_e.exception.UserCritical'>
and its value is CRITICAL: MSG: pipeline process did not exit gracefully
DETAIL: "gpg -d -q --batch" had terminated with the exit status 2.
STRUCTURED: time=2016-07-26T22:16:28.166828-00 pid=16167 and its
traceback is File
"/usr/local/lib/python2.7/dist-packages/wal_e/retries.py", line 62, in shim
return f(*args, **kwargs)
File
"/usr/local/lib/python2.7/dist-packages/wal_e/blobstore/s3/s3_util.py",
line 137, in download
raise
File "/usr/local/lib/python2.7/dist-packages/wal_e/pipeline.py",
line 115, in __exit__
command.finish()
File "/usr/local/lib/python2.7/dist-packages/wal_e/pipeline.py",
line 204, in finish
.format(" ".join(self._command), retcode))
There have been 1 attempts to fetch wal file
s3://example/wal-e/master-db/wal_005/00000009.history.lzo
so far.
STRUCTURED: time=2016-07-26T22:16:28.167967-00 pid=16167
gpg: packet(2) with unknown version 79
lzop: <stdin>: not a lzop file
wal_e.blobstore.s3.s3_util WARNING MSG: retrying WAL file fetch from
unexpected exception
DETAIL: The exception type is <class 'wal_e.exception.UserCritical'>
and its value is CRITICAL: MSG: pipeline process did not exit gracefully
DETAIL: "gpg -d -q --batch" had terminated with the exit status 2.
STRUCTURED: time=2016-07-26T22:16:28.416916-00 pid=16167 and its
traceback is File
"/usr/local/lib/python2.7/dist-packages/wal_e/retries.py", line 62, in shim
return f(*args, **kwargs)
File
"/usr/local/lib/python2.7/dist-packages/wal_e/blobstore/s3/s3_util.py",
line 137, in download
raise
File "/usr/local/lib/python2.7/dist-packages/wal_e/pipeline.py",
line 115, in __exit__
command.finish()
File "/usr/local/lib/python2.7/dist-packages/wal_e/pipeline.py",
line 204, in finish
.format(" ".join(self._command), retcode))
There have been 2 attempts to fetch wal file
s3://example/wal-e/master-db/wal_005/00000009.history.lzo
so far.
STRUCTURED: time=2016-07-26T22:16:28.417242-00 pid=16167
--
You received this message because you are subscribed to the Google Groups
"wal-e" 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.
