Support

Akeeba Backup for Joomla!

#9232 Failed Smart algorithm on AECoreDomainPack

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, 28 December 2011 07:02 CST

user39116
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? yes
Have I searched the forum before posting? yes
Have I read the documentation before posting (which pages?)? yes
Joomla! version: 1.7.3
PHP version: (unknown)
MySQL version: (unknown)
Host: (optional, but it helps us help you) Hostpapa
Akeeba Backup version: 3.3.10

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.

Description of my issue:
Hi,
Since the last update ( 3.3.10) unable to do a manually or automatic ( with cron) backup.
I saw the log and there is a "Failed Smart algorithm on AECoreDomainPack "
and there is a problem with "plugins/editors-xtd/pagebreak/pagebreak.xml "
All plugins seem to work fine. I don't know what to do.
Could you suggest me something ?
thank you

nicholas
Akeeba Staff
Manager
Hm, let's take a look at your log file:
[111218 10:59:58] Packing files

[111218 10:59:58] Connecting to remote FTP

[111218 11:00:00] Uploading plugins/editors-xtd/pagebreak/pagebreak.xml has failed.

This tells me that instead of backing up to a backup archive file you are actually trying to copy all files to a remote FTP repository. Please go to the Configuration page and set the "Archive Engine" to JPA. I believe that your intention is to back up to a regular archive file, not transfer your site to a remote FTP server, right?

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!

user39116
Actually, I used the copy to a remote ftp repository. It worked fine until the las update. I have on the remote directory with jpa files. I have enough place on the remote directory.

I set the "Archive Engine" to JPA. It worked. see the log file. (Akeeba Backup Debug Log JPA).

I reset to "FTP transfert" and this night the automatic backup to ftp didn't work. ( see the log )

Here is my cron command :
wget --max-redirect=10000 "http://www.lyoncasting.com/index.php?option=com_akeeba& view=backup&key=password"

When I updated to last version ( from joomla backend ) All Akeeba settings were lost... I redone all.

I'm doing other tests...

Thank you

nicholas
Akeeba Staff
Manager
Normally, when you upgrade no settings should be lost. The only case where settings are lost is if you uninstall before upgrading, which is the exact opposite of our instructions in our documentation.

Now, in the front-end backup log file I can see this:
ERROR |111219 01:30:04|Invalid username/password for the remote FTP server
Simply put, you are using the wrong FTP connection information in profile #1 (the default backup profile).

The back-end log file seems to be from an earlier backup, not using FTP?

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!

user39116
ok, but I did'nt uninstall it before upgrade. I used the Joomla extension manager to upgrade.

I've already seen this error. However, in Akeeba Backup Configuration, all ftp tests works : I can choose the remote folder with the search button.

I'm retrying...

user39116
when I launch a cron backup,in the akeeba backup manager, I've got a new line like this :

Sauvegarde effectuée le lundi 19 décembre 2011 19:35 19/12/11 - Erreur Frontal Fichiers du site et base de données 1
(backup done the 2011/12/19 - error )

Here is the email send by my host after the cron job done :
--2011-12-19 20:35:01-- http://www.lyoncasting.com/index.php?option=com_akeeba&%20view=backup&key=password
Resolving www.lyoncasting.com... 76.74.128.40
Connecting to www.lyoncasting.com|76.74.128.40|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.php?option=com_akeeba& view=backup&key=password.1'
0K 3.05M=0s
2011-12-19 20:35:03 (3.05 MB/s) - `index.php?option=com_akeeba& view=backup&key=bo9tjrw3!.1' saved [64]

But, there is no new Akeeba frontal log...

nicholas
Akeeba Staff
Manager
Of course it won't work. Now that you pasted the complete URL I can see what you're doing wrong. The documentation tells you that there should be no line break and no space in the URL. The line break is added in the docs for typesetting reasons and that's why I have specifically written a warning box to let you know that you should not include the linebreak when copying the URL.

In plain English, this means that the following URL (which you are using) is wrong:

http://www.lyoncasting.com/index.php?option=com_akeeba&%20view=backup&key=password

While this URL is correct:

http://www.lyoncasting.com/index.php?option=com_akeeba&view=backup&key=password

See the difference? There's no space between com_akeeba& and view= (the %20 in the original URL means that you typed in a space). That's what stands between you and the CRON job :) If you remove it, it'll work.

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!

user39116
thanks, I've just try it via Chrome :

http://www.lyoncasting.com/index.php?option=com_akeeba&view=backup&key=password

and I get :
500 ERROR -- Invalid username/password for the remote FTP server

I don't understand. In the akeeba backend username/password are good because the ftp test is "ok" and I can select the remote folder via the button !?

David

nicholas
Akeeba Staff
Manager
Can you please take a backup from the back-end and the front-end and send me the two log files?

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!

user39116
found !
I have enabled FTPS (FTP with SSL). in back-end, there is no problem to connect to the remote directory, but it doesn't work in front-end.
I launched a new front end backup. The log is fine. I'm waiting tomorrow... ( It's a more than 2Go site )

Thank you

nicholas
Akeeba Staff
Manager
Do you have more than one backup profiles? In this case, are you sure that you are using the same profile in both the back-end and the front-end backup? This is what I wanted to confirm and that's why I asked for the two log files.

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!

user39116
A question : with 3.3.10 there is no more jpa archive in a remote directory, only a "simple" copy/past of files and DB ?

nicholas
Akeeba Staff
Manager
You are using the wrong options for what you want to achieve. Set the "Archiver Engine" to JPA. Remember to set the "Part Size for Split Archives" to a sensible value, e.g. 20Mb (your mileage may vary). Then set the "Data Processing Engine" to "Upload to Remote FTP" and set up the FTP connection. This will allow you to upload a JPA file to the remote FTP instead of all files one by one (which is exactly what the DirectFTP archiver engine is doing, as promised in its description and its documentation).

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!

user39116
I have only one profil.
I understand : I had not the pro version but the core version.
It seems that I upgraded the pro to the core. (strange ?)
I downloaded and installed the pro version : I refound all my options and settings ! And the backup works properly !

Please accept my apologies and thank you very much for your attention !

David

nicholas
Akeeba Staff
Manager
Ah, that makes sense! I have one question though: did you do the upgrade to 3.3.10 manually or did you use Live Update? I want to make sure that Live Update didn't somehow malfunction.

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!

user39116
I believe that I done a Live update. It's why I didn't verfy if it was the core or the pro version.

But I kown that the first version that I installed was the core to test it. Next, I bought the pro version and installed it ( without to desintall the core version.)

for the pro, I began with the 3.3.5 (?) ( 6 november 2011) and all the updates ( except the 3.3.10 ) were safe.

but I am not very sure. Is there log to see my downloads and / or my installs ?

nicholas
Akeeba Staff
Manager
No, there is no way to see a log of the previously installed versions because such a log is not kept by Joomla!. However, I think I know what's going on.

When you upgrade from Core to Pro you actually have to install the Professional release twice due to an issue with the Joomla! extensions installer. The first time you run the update, it doesn't copy all files. The second time it does. From that point it is able to perform updates from one Professional release to the next without a problem.

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!