PostgreSQL won't allow a backup operation until WAL segments are being successfully archived, which is why the backup-push operation fails for you. Looking at the output from the backup-list operation, it looks like your S3 credentials are incorrect. Make sure that you have the correct credentials stored in /etc/wal-e.d/env. Specifically, the error message you're receiving is for an unknown access key ID meaning at minimum you are using the wrong value for that. This will also cause your WAL archival command to fail, which is why you're getting the "MSG: blocking on sending WAL segments" message from PostgreSQL when trying a backup-push.
~Brian Oldfield On Thursday, April 17, 2014 8:06:12 AM UTC-7, Rui Monteiro wrote: > > Hi > > *I have a problem, i can't upload segments to the S3, the output is the > following :* > > postgres@:~$ envdir /etc/wal-e.d/env /usr/local/bin/wal-e backup-push > /var/lib/postgresql/9.1/main > wal_e.operator.backup INFO MSG: start upload postgres version metadata > DETAIL: Uploading to > s3://produtocentro/backups/basebackups_005/base_000000010000000000000017_00000032/extended_version.txt. > STRUCTURED: time=2014-04-17T15:02:20.371237-00 pid=7074 > wal_e.operator.backup WARNING MSG: blocking on sending WAL segments > DETAIL: The backup was not completed successfully, but we have to > wait anyway. See README: TODO about pg_cancel_backup > STRUCTURED: time=2014-04-17T15:02:21.079066-00 pid=7074 > NOTICE: pg_stop_backup cleanup done, waiting for required WAL segments to > be archived > WARNING: pg_stop_backup still waiting for all required WAL segments to be > archived (60 seconds elapsed) > HINT: Check that your archive_command is executing properly. > pg_stop_backup can be canceled safely, but the database backup will not be > usable without all the WAL segments. > > *And if listing the backups the output is the following :* > > > postgres@:~$ envdir /etc/wal-e.d/env /usr/local/bin/wal-e backup-list > name last_modified expanded_size_bytes wal_segment_backup_start > wal_segment_offset_backup_start wal_segment_backup_stop > wal_segment_offset_backup_stop > wal_e.main CRITICAL MSG: An unprocessed exception has avoided all error > handling > DETAIL: Traceback (most recent call last): > File "/usr/local/lib/python2.7/dist-packages/wal_e/cmd.py", line > 518, in main > backup_cxt.backup_list(query=args.QUERY, detail=args.detail) > File > "/usr/local/lib/python2.7/dist-packages/wal_e/operator/backup.py", line 64, > in backup_list > for bi in bl_iter: > File > "/usr/local/lib/python2.7/dist-packages/wal_e/worker/base.py", line 153, in > __iter__ > for key in self._backup_list(self.layout.basebackups()): > File > "/usr/lib/python2.7/dist-packages/boto/s3/bucketlistresultset.py", line 30, > in bucket_lister > delimiter=delimiter, headers=headers) > File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line > 375, in get_all_keys > '', headers, **params) > File "/usr/lib/python2.7/dist-packages/boto/s3/bucket.py", line > 342, in _get_all > response.status, response.reason, body) > S3ResponseError: S3ResponseError: 403 Forbidden > <?xml version="1.0" encoding="UTF-8"?> > <Error><Code>InvalidAccessKeyId</Code><Message>The AWS Access Key > Id you provided does not exist in our > records.</Message><RequestId>adsahdkjashdka</RequestId><HostId>asdadad</HostId><AWSAccessKeyId>rterutoeiutoeiutoieut</AWSAccessKeyId></Error> > > STRUCTURED: time=2014-04-17T15:04:38.314522-00 pid=7179 > postgres@:~$ > > Thank you > Rui Monteiro > > > -- > > Rui Monteiro > [email protected] <javascript:> > www.centroproduto.com > TM : +351910536693 > -- 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.
