The free forums are no longer in use. It remains available as read-only archive.
3:15 pm
February 19, 2011
After executing cron command via SSH, the local backup was successful. But, there's a problem in saving backup to Amazon S3 bucket.
Here is the error message:
<b>AMAZON S3: Starting communication with the Amazon S3 server...</b><br />
<br />
<b>Warning</b>: S3::listBuckets(): [77] error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
in <b>/home/path/to/wordpress/installation/wp-content/plugins/xcloner-backup-and-restore/classes/S3.php</b> on line <b>93</b><br />
<br />
<b>Warning</b>: S3::putBucket(Example, private, ): [77] error setting certificate verify locations:
CAfile: /etc/pki/tls/certs/ca-bundle.crt
CApath: none
in <b>/home/path/to/wordpress/installation/wp-content/plugins/xcloner-backup-and-restore/classes/S3.php</b> on line <b>229</b><br />
<b>AMAZON S3: Unable to create bucket Example (it may already exist and/or be owned by someone else)!</b><br />
-------------------------
I've replaced my S3 bucket name with "Example".
This bucket is owned by me & my Access key pairs were correct (I've checked it multiple times). Also, there's no need to create a new bucket each time the cron job is executed..
Please, help!
Hi Sachin! The issue you seem to have is related to a curl install miss-configuration on the server, please refer to this blog post, it should help http://chrisschuld.c.....locations/
Let me know if you still have issues! Ovidiu
8:38 pm
February 19, 2011
A solution would be to disable the ssl usage, so open the wp-content/plugins/xcloner-backup-and-restore/cloner.cron.php and replace this line(around 292 line):
$s3 = new S3($_CONFIG['cron_amazon_awsAccessKey'], $_CONFIG['cron_amazon_awsSecretKey']);
with
$s3 = new S3($_CONFIG['cron_amazon_awsAccessKey'], $_CONFIG['cron_amazon_awsSecretKey'], false);
Let me know if it worked! Ovidiu
10:31 pm
February 19, 2011
The first problem has been fixed with your method. But, there're others to prevent the backup being successful.
Here is the error message:
<b>AMAZON S3: Starting communication with the Amazon S3 server...</b><br />
<br />
<b>Warning</b>: S3::putBucket(MyBucket, private, ):
[BucketAlreadyExists] The requested bucket name is not available. The
bucket namespace is shared by all users of the system. Please select a
different name and try again. in
<b>/path/to/wordpress/installation/wp-content/plugins/xcloner-backup-and-restore/classes/S3.php</b>
on line <b>229</b><br />
<br />
<b>Warning</b>: S3::putObject(): [AccessDenied] Access
Denied in
<b>/path/to/wordpress/installation/wp-content/plugins/xcloner-backup-and-restore/classes/S3.php</b>
on line <b>361</b><br />
<b>AMAZON S3: Failed to copy file to
{MyBucket}/Destination/Directory/in/Amazon/S3/backup_2011-02-19_16-07_gamingcheater.com-sql-nodrop.tgz</b><br
/>
-----------------
I've replaced Bucket name with "MyBucket".
The Bucket
is owned by me. Its not shared at all. The bucket is accessed by few
(less than 10) applications. At the time of cron job execution, no other
app was accessing that bucket.
Is there something broken if it comes to backup in existing buckets?
Please, look around it..
The error you are showing up seems to be related to a permission issue to your amazon account, the script is unable to upload the backup to the specified bucket. The script usually tried to create a bucket if it does not exists, however from the error above it doesn't seem to be allowed to access that bucket name.
Try and use another name for your bucket, make sure it's something more unique and see if it helps.
Ovidiu
9:48 am
February 19, 2011
1. I am using other apps to upload using the same credentials. Means, my permission is Ok.
2. After using a unique bucket name, I'm facing the same problem. After cron job execution, I've created a bucket (using AWS console) having same name successfully. Means, the bucket name was unique.
Now, I can confidentally say "There's something broken in XCloner S3 script."
10:18 am
September 26, 2010
Could you post here a screenshot of your amazon s3 config details, except of course your private keys, to see if we can spot something there. We are using the amazon upload feature without issues from here, but again, we can't really test all enviroments.
We could help you better if we would have access to your cron script and try our amazon details to see if it's something related to XCloner, so if you like, feel free to open a support ticket and send us the XCloner admin details there.
As a suggestion, could you try a localhost install and see if you have any issues uploading with the same S3 details, it might help identifying where the issue is.
Ovidiu
8:14 am
February 24, 2011
Hello,
I have some errors:
AMAZON S3: Starting communication with the Amazon S3 server...
Warning: S3::putObject(): [28] Operation timed out after 10 seconds with 0 bytes received in ........./xcloner-backup-and-restore/classes/S3.php on line 361
AMAZON S3: Failed to copy file to {akonstrubackup}/backup/backup_2011-02-24_10-41_akonst.ru-sql-nodrop.tar
How I can fix it?
Thanks!
10:01 am
September 26, 2010
Hi Andrey! The error seems to be related to cURL, you need to check if:
1. are you able to ping within your server this address s3.amazonaws.com , if not, the server provider might be blocking dns resolve requests within the server
2. is there any firewall on the server that could affect the communication with the amazon server?
This url might be of good use http://www.geekhelpg.....d-error/ , it seems there is a plugin called Core Control which you can use to test aspects of the http transport protocols.
Hope it helps! Ovidiu
1 Guest(s)