Support

Akeeba Backup for Joomla!

#13830 Errors with installation after akeeba installed

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 Monday, 15 October 2012 10:25 CDT

mustards
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes (various, including Akeeba Backup throws an AJAX Error, 500 Internal Server Error or the backup does not complete,Any other Akeeba Backup related question)
Joomla! version: 2.5.7
PHP version: 5.3.6
MySQL version: 5.1.30
Host: (optional, but it helps us help you) batcave.net
Akeeba Backup version: 3.6.5 Pro

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.

Backup log file contains:

DEBUG |121012 23:46:32|Kettenrad :: Attempting to load from database (backend)
DEBUG |121012 23:46:32| -- Stored Akeeba Factory (backend) not found - hard reset
DEBUG |121012 23:46:32|
DEBUG |121012 23:48:31|Kettenrad :: Attempting to load from database (backend)
DEBUG |121012 23:48:31| -- Stored Akeeba Factory (backend) not found - hard reset
DEBUG |121012 23:49:39|

Description of my issue:

I have been migrating my Joomla 1.5 sites to 2.5 using the spupgrade component. Once migrated I've been installing akeeba and other components to restore the site to it's operational status, under Joomla 2.5.x. This has worked fine a number of times. On this site (first site on batcave.net) I have had problems after installing akeeba.

Akeeba installation works fine and when I run the post-installation configuration (enable system restore points, akeeba backup update emails, run configuration wizard checked) this completes (Finished benchmarking) as expected.

However, once at this point, any operation (other than components/akeeba backup) thereafter takes a long time to complete, as if something is timing out.

Going to components/akeeba backup also takes a long time to complete, and when the akeeba control panel eventually appears the rest of the joomla menu disappears. An error is displayed:

Error loading module MySQL server has gone away SQL=SELECT m.id, m.title, m.module, m.position, m.content, m.showtitle, m.params, mm.menuid FROM lze9a_modules AS m LEFT JOIN lze9a_modules_menu AS mm ON mm.moduleid = m.id LEFT JOIN lze9a_extensions AS e ON e.element = m.module AND e.client_id = m.client_id WHERE m.published = 1 AND e.enabled = 1 AND (m.publish_up = '0000-00-00 00:00:00' OR m.publish_up = '2012-10-13 23:22:01') AND m.access IN (1,2,3) AND m.client_id = 1 AND (mm.menuid = 0 OR mm.menuid rm) once there has been a visit to components/akeeba backup the menu never reappears, even if you change the page to site/administrator or any other valid link in the administrator area. The akeeba backup status icon is shown though. On one occasion the joomla menu did still appear (after the delay) and the error above appeared when components/akeeba backup was selected.

In the situation where the Joomla menu disappears, and every operation takes a long time, deleting the akeeba files (administrator/components/com_akeeba etc, as listed in ticket #12782) restores the situation so that any operation takes the normal amount of time, and the joomla menu is shown.

I assume this issue is something to do with php settings specific to this host, but I was unable to find anything other than a recommendation to change memory limit to a minimum of 32MB (which I have done). I have a disk space limit of 1GB and have used 257MB.

I hope you can help.

Regards

Steve

nicholas
Akeeba Staff
Manager
I would recommend deleting all #__ak_* tables from your Joomla! 2.5 site. These are Akeeba Backup's tables, storing all settings and backup attempt information. This information is stale anyway, so just get rid of it. Then uninstall and reinstall Akeeba Backup.

Please do not enable the automatic update notifications in the post-installation configuration page. This feature enables a plugin which tries to fetch Akeeba Backup update information and send you an email when a new version is available. Your server seems to have a problem with that.

The same check is also performed once every at most 6 hours when you visit Akeeba Backup's Control Panel. The first time you go to Akeeba Backup's Control Panel it will take forever to load. If it completely fails to do so please check with your host that:
- they have enabled the curl extension or enabled allow_url_fopen in the php.ini
- they allow connections to cdn.akeebabackup.com via ports 443 and 80. If they ask for an IP address ask them to do a
host -a cdn.akeebabackup.com
from their server to find out the IP address. It's a CDN, therefore the actual IP is different depending on where the world your server is.
These will allow Akeeba Backup's Live Update to communicate with its update server and load in a timely fashion.

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!

mustards
Thanks Nicholas

I have deleted the tables, uninstalled and reinstalled. I also confirmed that allow_url_fopen is on in the php.ini file (curl 7.15.5 is enabled). Now it takes a long time to load the Akeeba control panel, and the Joomla menu is not shown when it appears but everything else seems to work normally (ie loads at a normal pace).

I have raised a ticket with the host to ask about the ports and I will let you know the outcome.

Regards

Steve

mustards
Hi Nicholas

Just wanted to confirm that Batcave.net, the host, did confirm that ports were closed by default and they have now re-opened them. Everything is working fine now. Thanks for identifying the issue.

Do you think it would be possible in a subsequent release to identify if communications are not possible to warn the user and then not keep trying so that the delays and related issues don't occur?

Thanks again

Steve

nicholas
Akeeba Staff
Manager
Hi Steve,

Oh, I wish I could do that! Unfortunately, it's not really possible. We can go as far as detecting if cURL or allow_url_fopen is enabled on most hosts. We can't reliably detect the source of a communications error. It could be a server firewall, a problem with our CDN, a temporary routing issue in your server / our CDN / somewhere in between and so on. The point is that if we triggered an automatic kill-switch for the update feature whenever an update fetch error occurred we'd end up with thousands of sites not getting update notifications and without their owners being aware of that. This is much more dangerous than a handful of sites needing special support from their hosts.

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!