Support

Akeeba Backup for Joomla!

#9104 404 Component not Found

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 Friday, 14 October 2011 17:28 CDT

user7915
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.5.23
PHP version: 5.2.5
MySQL version: 5.0.81-community-log
Host: Siteground
Akeeba Backup version: 3.3.3

EXTREMELY IMPORTANT: Please attach your Akeeba Backup log file in order for us to help you with any backup or restoration issue.

Description of my issue: On a cloned version of our live site - I attempted to upgrade from Akeeba 3.3.3 to 3.3.4. The automatic upgrade process was not working, so I uploaded the new component files via ftp to our tmp folder and ran an update from there.

After this, the component was not installed properly - and worse, the native Extension Install function on Joomla does not work - it gives me a 404 component not found error when I hit the installer component.

Any chance I can get some guidance on how to reverse whatever happened to the install component so I can at least get back to normal here?

Thanks,
Jeff

dlb
Jeff,

Disable the plugin "System - System Restore Points". That will disable the restore points function, which may be what is interfering with your installer.

If you get the installer back, you can try the upgrade again. Don't uninstall Akeeba, that will cause you to lose all of your settings.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

user7915
That worked, thanks Dale. Now on to my next issue - I can't seem to install 3.3.4. I've attached the error message I'm getting when I try to reinstall.

dlb
Wow! I haven't seen one of those in a long time. The root of the problem is "MySQL server has gone away". That means that your MySQL server dropped the connection while the update was in progress. I don't know any tricks to get around this. It is late Friday night in Nicholas' neck of the woods. I'm afraid we're going to have to wait until tomorrow. I'm sorry I can't be more help.


Dale L. Brackin
Support Specialist


us.gifEnglish: native


Please keep in mind my timezone and cultural differences when reading my replies. Thank you!


????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

nicholas
Akeeba Staff
Manager
OMG! I haven't seen one of those errors for a very long time. Well, it's bad news, that's for sure. It actually means that your server may be way too slow. Let me explain what goes on. When you try to install a component, Joomla! has to move the uploaded file to the tmp directory, extract it, copy the files from the tmp directory to their final location and, finally, execute the SQL commands and the PHP installation script. All of this requires a lot of time - on some slow hosts that could be 20-40 seconds.

Pause here. Joomla! opens a database connection when it spawns (in our installation case, right before it's starting to move the uploaded file to the temporary directory). Then, this database connection is idle for those 20-40 seconds Joomla! takes to copy around files. Hold that thought and let's proceed.

Some hosts -apparently yours is one of them- will forcibly close a database connection if it's idle for a "long" time. On mosts hosts that's a huge amount of time, 30 seconds or more, and you never notice. Some low quality hosts set this to an unrealistically low amount of time, usually in the vicinity of 1 to 5 seconds. When the database connection is closed, any subsequent attempt to use the database will result to the spooky "MySQL server has gone away" errors.

Now that you have all the puzzle pieces, it's easy to realise what's going wrong. Joomla! takes a lot of time to copy the files because your host is slow and this causes your host to close the database connection which causes Joomla! to fail the installation with this error message. The two remedies are to decrease the time Joomla! takes to install the extension or increase the timeout limit for database connections. Since the host's speed is fixed, the first workaround can only be achieved by using the manual installation method but, obviously, this doesn't apply in your case. So we're left with the second option. You have to ask your host to increase the time before an idle database connection is closed to 30 seconds or more.

My advice: find a decent host. The root cause of this issue is that you have a s-l-o-w host. This is usually an indication of an overcrowded server. Having a slow server can have some unforeseen consequences to your site, like ranking low on search engines (fast sites rank better, at least with Google) and many visitor bounces. My personal experience shows that a site which loads 1 second faster can lead to a decrease in bounce rate and visitors who spend less than 10 seconds on your site by a staggering 8-10%. Well, ultimately it's your choice :)

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!