Support

Akeeba Backup for Joomla!

#8726 Dropbox post processing error

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 Sunday, 05 December 2010 22:46 CST

user11696
I am using Akeeba Backup Professional 3.1.5 (2010-11-23)

When doing a backup on a site in the admin area (and with the lazy plugin) I get this error (but not every time):

Backup Failed
The backup operation has been halted because an error was detected.
The last error message was:

Cannot execute request: Unknown SSL protocol error in connection to www.dropbox.com:443

The log says (I replaced the domain name for my customer's privacy):

[101203 10:24:20] Beginning post processing file /administrator/components/com_akeeba/backup/www.mydomain.com-20101203-111230.jpa
[101203 10:24:23] Failed to process file /administrator/components/com_akeeba/backup/www.mydomain.com-20101203-111230.jpa
[101203 10:24:23] Error received from the post-processing engine:
[101203 10:24:23]
[101203 10:24:23] No quotas were defined; old backup files will be kept intact
[101203 10:24:23] ----- Finished operation 1 ------
[101203 10:24:23] Failed Smart algorithm on AECoreDomainFinalization


Anyone have any ideas? Is this a dropbox issue or a bug in Akeeba.

steph.s
It looks like error related to dropbox, I am not sure; maybe something has changed in the drop box API. I will flag this for Nicholas.

user11696
One thing I have noticed is that if I set the file splice to the largest value (instead of something around 6mb), the error does not occur. Right after posting the question, I stopped creating chunks of the backup file and instead let it make 1 huge file (only about 12mb) the error did not occur. I have repeated this and it always works if I don't set the file size chunks to something small (like recommended).

steph.s
Thanks for the information, I think it should work with parts, but for some reason it is not. I already flagged this post for Nicholas, so as soon as he is on he will take a look ;)

nicholas
Akeeba Staff
Manager
This looks like a host specific problem. During the time of the error it seems that your host was unable to connect to Dropbox. No matter which part size you use, the post-processing code runs exactly the same.

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!

user18962
just a note to test something..... I had the same issue and it seems that as long as I am logged into the web interface at dropbox.com.... the backup fails.... if I log out, the backup completes. I did this several times and noticed a pattern. Maybe ensure that you are not logged into the dropbox site, run the backup and see what happens?

user11696
I had considered that was a potential problem, so I started using the Lazy plugin to do everything in the middle of the night (LOVE the lazy plugin!). Sometimes the archive uploads, sometimes it doesn't. I have tried with 2 different hosting environments/vendors (inMotion Hosting and GoDaddy, VPS and Dedicated environments) and get the same issue of sporadically uploading or not uploading. it seems to be about a 35-40% chance of an upload failure. I had thought it was due to the archive sizes, but that has proven irrelevant.

steph.s
Apparently, DropBox experiences periodic short outages in its web interface (which is used by Akeeba Backup). If you try to backup during that time, you get those errors.

nicholas
Akeeba Staff
Manager
It is also true that if you are logged in DropBox's web interface the upload will not work. Akeeba Backup tries to connect to DropBox's web interface to send the backup archives to it. Using the RESTful API is not an option because it would oblige you to use part sizes of 1-2Mb, as their API requires each request to be signed which means that the entirety of the backup part has to be loaded in memory, processed and then sent to DropBox. This is not convenient at all, so I just scraped the idea of using that method.

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!