Support

Akeeba Backup for Joomla!

#23332 Upload S3 failed after 4.4.0

Posted in ‘Akeeba Backup for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Akeeba Backup version
n/a

Latest post by nicholas on Wednesday, 30 September 2015 15:34 CDT

mdube
EXTREMELY IMPORTANT: Please attach a ZIP file containing your Akeeba Backup log file in order for us to help you with any backup or restoration issue. If the file is over 2Mb, please upload it on your server and post a link to it.


Warnings
Upload cannot be initialised. Amazon S3 returned an error message: 0 :: Akeeba\Engine\Postproc\Connector\S3v4\Connector::startMultipart(): [0] The request signature we calculated does not match the signature you provided. Check your key and signing method.
Failed to process file /var/www/clients/client1/web1/web/administrator/components/com_akeeba/backup/site-model.biz-me.com-20150930-105545.jpa
Post-processing interrupted -- no more files will be transferred

When I try to get an already uploaded backup I get this

Error
The backup archive could not be located

Description of my issue: Since I upgraded to 4.4.0 version I get those errors. If I try on a site that has not been upgraded (version 4.3.1) everything is working ok.

Thanks!

Michel

nicholas
Akeeba Staff
Manager
Please go to Configuration, find the Post-processing engine row and click on the Configure button next to it. Make sure the "Amazon S3 Region" is set correctly to the same region your bucket is located in. Verify that the "Signature method" is set to "v4 (preferred for Amazon S3)". Click on Save & Close even if you made no changes. Try taking a new backup.

If the backup fails go to Configuration, find the Post-processing engine row and click on the Configure button next to it. Try setting the "Signature method" to "v2 (legacy mode, third party providers)" and click on Save & Close. Try taking a new backup.

If the backup still fails go to Configuration, find the Post-processing engine row and click on the Configure button next to it. Find the "Disable multipart uploads" and check the box next to it. Click on Save & Close. Try taking a new backup.

Please let me know which one of these solutions worked for you. Normally the first one should be sufficient.

If none of these worked please remember to ZIP and attach your backup log file.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

mdube
Ok!

I've been able to upload to S3 by disabling multipart uploads with v2 and v4 signature method.

One strange thing is that all my logs that are located in administrator/components/com_akeeba/backup are empty - 0 byte.

And if I start ALICE, I get 2 warnings:

Additional database - Wrong access details
Warning
Could not detect the used profile, test skipped

Additional database - Joomla database inclusion
Warning
Could not detect the used profile, test skipped

Thanks for that fast support ;-)

Michel
+++++++++++++++++++++++++++++++=

nicholas
Akeeba Staff
Manager
ALICE will not work without a log file. A log file will not be generated unless you set the logging level to All errors And Debug in the configuration page.

I want to ask you some questions to help me figure out what is going on. Which region are your buckets in? Do you use uppercase letters or dots in their names? Do you have Use SSL enabled? How big are your backups? What's the part size for split archives?

Thank you in advance. It's impossible for me to do anything constructive when all I have is an error report about something I cannot reproduce on any server, live, test or development, I have available. Indeed the extra info to start triangulation the issue.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

mdube
Hi Nicholas,

I modified the configuration to get something in the logs. I joined a zip file containing 2 screen captures and one compressed logs file. You'll find everything you need I think.

This being said, I must tell you that after a first try, from the logs scanned by ALICE, I got this error message:

Post-processing engine and archive part size
Warning
A post-processing engine is found, but no part size is set; this could lead to timeout issues
Set a part size inside backup profile configuration.

So I just modify the Part size to ~100MB and gave another try to get that error message:

Upload cannot be initialised. Amazon S3 returned an error message: 0 :: Akeeba\Engine\Postproc\Connector\S3v4\Connector::startMultipart(): [0] The request signature we calculated does not match the signature you provided. Check your key and signing method.
Failed to process file /administrator/components/com_akeeba/backup/site-model.xxx.com-20150930-152329.jpa
Post-processing interrupted -- no more files will be transferred

Strange message that does not seem to be related to the problem.

Then I made many other tries and finally with a part size of 5 MB, it works.

I don't understand why it works with 2GB part size with version 4.3.1 on another site that is on the same server. This server is running on a full gigabit network, ssd drives, 8 cores and 24 Gigs of ram.

So for now I don't care to disable multipart uploads. My backups are not so big (500 MB to 1 Gig).

But if you can tell me what is going wrong with this, I would appreciate.

Thanks!

nicholas
Akeeba Staff
Manager
This version has been canceled. Thank you for your bug report. Please downgrade to Akeeba Backup 4.3.

Nicholas K. Dionysopoulos

Lead Developer and Director

πŸ‡¬πŸ‡·Greek: native πŸ‡¬πŸ‡§English: excellent πŸ‡«πŸ‡·French: basic β€’ πŸ• My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!