Support

Akeeba Backup for Joomla!

#40698 backup fails: only writes the jpa file, "Chunk upload finalization failed"

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
4.4.4
PHP version
8.2.18
Akeeba Backup version
9.9.2

Latest post by nicholas on Sunday, 12 May 2024 13:38 CDT

gregeusa

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 10MiB, please upload it on your server and post a link to it.

 

error shown:

Failed to process file /var/www/vhosts/elmassian.com/httpdocs/administrator/components/com_akeebabackup/backup/site-www.elmassian.com-20240505-181950pdt-nkWWdAbGV2Xk0e2G.j01

Error received from the post-processing engine:

Chunk upload finalization failed

Error lookup_failed: No error description provided. Raw error: Array ( [.tag] => lookup_failed [lookup_failed] => Array ( [.tag] => incorrect_offset [correct_offset] => 1069547520 ) )

Post-processing interrupted -- no more files will be transferred

So I get the little jpa files, 186k, but the main backup file never appears, as you can see above.

 

 

 

nicholas
Akeeba Staff
Manager

Are you using Dropbox? There seems to be a problem either with Dropbox itself or a number of hosts in North America. What we see in the log files is claims of implausible upload speeds (20MiB chunks being uploaded at 0.5 seconds; that's impossible unless you're literally connected via a Gigabit local LAN connection to Dropbox' server which is the implausible part) and a final error on upload finalisation which matches what you see, saying that the offset is incorrect i.e. the data uploaded does not match the amount of data we have been sending.

If you have set up a transparent proxy on your server, e.g. Squid or Varnish, for outgoing HTTP(S) connections, i.e. connections made by your server to other remote servers, please make sure that you are NOT caching the responses of POST and PUT requests, and that you do include all URL (GET) parameters to the caching key. Anything else will break uploads to any remote storage provider.

If you have not set up a transparent proxy, please let us know. This would confirm that something is wrong with Dropbox in North America. We've only seen this problem coming from US and Canadian users, and we have been unable to reproduce this from Europe where we're based.

In the meantime, we'd recommend using a business-grade file hosting solution such as Amazon S3, Wasabi, BackBlaze B2 etc instead of consumere-grade storage providers (Box, Dropbox, OneDrive, Google Drive -- even their "pro" or "business" offerings are still the same consumer-grade technology they sell to individuals, just with a higher capacity limit). Business-grade file hosting doesn't have the reliability issues we've seen with consumer-grade storage providers the past 15 years.

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!