I kinda looked there already and didn't see any notable error messages.
When I do a manual backup-push, I have to hit a ctrl-C to interrupt it, so
syslog seems to only contain non-error messages:
Aug 12 22:44:00 ip-10-123-148-194 wal_e.operator.backup INFO MSG: start
upload postgres version metadata#012 DETAIL: Uploading to
s3://production_postgresql/basebackups_005/base_000000010000000000000020_00000040/extended_version.txt.#012
STRUCTURED: time=2014-08-12T22:44:00.429147-00 pid=4964
Aug 12 22:44:00 ip-10-123-148-194 wal_e.operator.backup INFO MSG:
postgres version metadata upload complete#012 STRUCTURED:
time=2014-08-12T22:44:00.553103-00 pid=4964
Aug 12 22:44:00 ip-10-123-148-194 wal_e.worker.upload INFO MSG:
beginning volume compression#012 DETAIL: Building volume
0.#012 STRUCTURED: time=2014-08-12T22:44:00.844788-00 pid=4964
Aug 12 22:44:02 ip-10-123-148-194 wal_e.worker.upload INFO MSG: begin
uploading a base backup volume#012 DETAIL: Uploading to
"s3://production_postgresql/basebackups_005/base_000000010000000000000020_00000040/tar_partitions/part_00000000.tar.lzo".#012
STRUCTURED: time=2014-08-12T22:44:02.007589-00 pid=4964
Aug 12 22:44:02 ip-10-123-148-194 wal_e.worker.upload INFO MSG: finish
uploading a base backup volume#012 DETAIL: Uploading to
"s3://production_postgresql/basebackups_005/base_000000010000000000000020_00000040/tar_partitions/part_00000000.tar.lzo"
complete at 15728.8KiB/s. #012 STRUCTURED:
time=2014-08-12T22:44:02.459143-00 pid=4964
The log in /var/log/postgresql is likewise uninformative. The error from
archive_command is repeated instances of this:
2014-08-12 23:11:00.520 UTC,,,30174,,53ea0337.75de,2679,,2014-08-12
12:06:15 UTC,,0,LOG,00000,"archive command failed with exit code 111","The
failed archive command was: envdir /etc/wal-e.d/env wal-e wal-push
pg_xlog/000000010000000000000009.00000028.backup",,,,,,,,""
2014-08-12 23:11:00.520 UTC,,,30174,,53ea0337.75de,2680,,2014-08-12
12:06:15 UTC,,0,WARNING,01000,"archiving transaction log file
""000000010000000000000009.00000028.backup"" failed too many times, will
try again later",,,,,,,,,""
The above file being complained about is found in an archive_status folder
in pg_xlog.
On Tuesday, August 12, 2014 6:00:28 PM UTC-4, Daniel Farina wrote:
>
> On Tue, Aug 12, 2014 at 1:48 PM, Paul Tiseo <[email protected]
> <javascript:>> wrote:
> > On Ubuntu 14, I have a strange feeling that something is a little off,
> after
> > following the instructions on the Github site and the Opbeat blog.
> >
> > postgres does not seem to want to run the archive command properly.
> >
> > If I manually run envdir /etc/wal-e.d/env wal-e wal-push
> > /var/lib/postgresql/9.3/main/pg_xlog/00000001000000000000001A, it seems
> to
> > work.
> >
> > If I manually run envdir /etc/wal-e.d/env wal-e wal-push
> > pg_xlog/00000001000000000000001A while in/var/lib/postgresql/9.3/main,
> it
> > seems to work.
> >
> > But, my archive_command, 'envdir /etc/wal-e.d/env wal-e wal-push %p',
> seems
> > to error out.
>
> Do you have any logs from that?
>
> Try syslog or the pg_log directory.
>
> > I'm assuming that whatever is jamming wal-push in the archive_command is
> hitting an ending step of backup-push?
>
> Yup.
>
--
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.
