Akeeba Backup for Joomla!

Monday, 12 March 2012 12:34 CDT

swingshoes

#11496: Command line indicated failed - but it didn't (continued)

This problem is still occurring. I have reinstalled the component, cleared the cache of Joomla, cleared the clache of the browser, used another browser.

It seems that the backup is working correctly from the log files etc, but it still shows the backup as failed.

The only possibility that I haven't explored is if it has to do with sending the file to Dropbox (and deleting the archive).

I'll keep following your direction on this,
Erik

Monday, 12 March 2012 12:56 CDT

swingshoes

I think I'm on to something...

I set the Data processing engine to "No post-processing"
however I still got a warning that Akeeba was unable to delete the backup (see attachment). That might indicate that the "Failure" warning might have something to do with the dropbox/delete archive engine.

Hope that helps,
Erik

Monday, 12 March 2012 12:56 CDT

swingshoes

I think I'm on to something...

I set the Data processing engine to "No post-processing"
however I still got a warning that Akeeba was unable to delete the backup (see attachment). That might indicate that the "Failure" warning might have something to do with the dropbox/delete archive engine.

Hope that helps,
Erik

Monday, 12 March 2012 13:19 CDT

nicholas

That last error message is the result of the backup record being displayed as Failed. I honestly have no idea as to what is going on. I can't replicate on any other server :s

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!

Monday, 12 March 2012 14:52 CDT

swingshoes

More info:
If I set my backup to send to DropBox but NOT delete the archive, then it works.

but if I set my backup to send to DropBox AND delete the archive, it shows as a failed backup.

That's the latest,
Erik

Monday, 12 March 2012 15:22 CDT

nicholas

That's strange. What are the permissions of the backup archive on your server?

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!

Monday, 12 March 2012 15:41 CDT

swingshoes

the file permission is 755

Monday, 12 March 2012 17:31 CDT

nicholas

Ugh, it doesn't make any sense :(

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!

Friday, 16 March 2012 01:39 CDT

swingshoes

Is is possible that this might be an issue because I have two different sites connected to the same dropbox?

It also seems to be something related to the last step of the backup (deleting the archive).

I'm still trying to figure this out even though I seem to have stable backups.

Thanks,
Erik

Friday, 16 March 2012 03:56 CDT

nicholas

Yes, it could be. Right now it's not clear if the Dropbox API allows the same application to be linked with the same user account from two different instances. Neither do they prescribe a way to fetch the existing authorisation token, i.e. have all of your copied of Akeeba Backup automatically authorised with Dropbox after you do that once, on just one site. Unfortunately, that's Dropbox' API and they have the final say on what is possible and what is not.

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!

Friday, 16 March 2012 12:08 CDT

swingshoes

ok - I'm not sure that that's the reason but I thought I'd mention it.

It worked just fine using the dropbox settings prior to the 2-part authorization process.

From my latest trails - it seems that it has to do with the post-processing engine: if the backup is set to "Delete archive after processing" then the backup will be marked as failed even though the archive was sent to dropbox, and also deleted.

I don't get it either, but just wanted to let you know.

Friday, 16 March 2012 12:35 CDT

nicholas

I'm not sure why that happens. The same setup and options, when I test it locally, results in a "Remote" backup, which is the expected result. If anyone else reports it, I will consider it a bug and try to fix it. For now, I mark this is a plausible issue I can't replicate.

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!

Friday, 16 March 2012 12:45 CDT

swingshoes

OK - I think I'm on to something.

Previously, I did not have to split the archives (usually 80mb). Everything worked fine.

Now, I adjusted to split the archive at 20mb (4 parts), and this seems to have worked. I know that this is your recommended setting, but it had worked unsplit with dropbox previously so I tried to keep everything consistent.

I'll keep you posted if this lasts a couple of cycles.

thanks for all your help at this point,
Erik

Friday, 16 March 2012 12:51 CDT

nicholas

OK, you are indeed onto something! If you use part size for split archives over 30Mb or so, it is possible that PHP reports a timeout, even though the file gets uploaded. This would, in turn, trigger the Failed status. Try your settings with 20Mb part size for a few times and let me know if that solved 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!

Friday, 16 March 2012 13:15 CDT

swingshoes

Yes - I've set it to 20mb and it seems to have worked. I'll let a few cycles go by to confirm.

Thanks you,
Erik

Saturday, 17 March 2012 12:52 CDT

swingshoes

So close, yet so far!

Same issue even with Backup archives split to 20MB.
The only thing that reliably works is if I don't automatically upload to dropbox.

Maybe in the next update, the issue will resolve itself.

E

Saturday, 17 March 2012 13:13 CDT

nicholas

I'm not sure what is causing it :( If I could replicate it on another server, I would consider it a bug. Why that only happens on your server, that beats me!

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