Support

Akeeba Backup for Joomla!

#13932 AEAbstractDump :: Database Error: Could not connect to MySQL

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 Tuesday, 23 October 2012 03:39 CDT

gmarsh
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
Joomla! version: (2,5,7)
PHP version: (5.3.17)
MySQL version: (5.5.27)
Host: (ICDSoft)
Akeeba Backup version: (3.6.5, 3.6.7, 3.6.8)

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: The CRON job stopped working on October 15th giving the database error. I thought it might be an issue with something changing in the hosting, but ICDSoft says nothing was changed. Manual backups to Amazon S3 still work as expected.

I upgraded from 3.6.5 to 3.6.7 and then to 3.6.8 to see if the error would go away. But no luck!

I use Akeeba on all my sites (all hosted on ICDSoft) and have had no troubles with any other site.

Thanks for your help!
Gary

nicholas
Akeeba Staff
Manager
Akeeba Backup 3.6.0 up to and including 3.6.5 had a bug connection with the MySQL database from the CLI CRON script. This was half-fixed in 3.6.6.RC1 and properly patched in 3.6.6 stable. I was able to reproduce that issue on test and live servers. I cannot reproduce this issue this any more on any sites and other clients who were affected have reported that the 3.6.6 release had fixed the issues they had.

This leads me to believe that something didn't get updated in your site. We'll have to go through the scenic route to make sure that the upgrade does work. Please remove the following folders:
- administrator/components/com_akeeba EXCEPT the administrator/components/com_akeeba/backup directory and the administrator/components/com_akeeba/akeeba/serverkey.php file. If you remove that directory and that file you will lose your existing backups and/or settings.
- components/com_akeeba
- administrator/modules/mod_akadmin
- media/com_akeeba
- plugins/system/plg_srp
- plugins/system/plg_akeebaupdatecheck
- plugins/system/plg_aklazy
- plugins/system/plg_oneclickaction
Now you can re-install Akeeba Backup Professional. This should fix this 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!

gmarsh
I took the entire scenic route . . . and nothing changed. Subsequently, I've . . .
~ Uninstalled 3.6.8 and reinstalled 3.6.5 - no change.
~ Uninstalled 3.6.5 and reinstalled 3.6.8 - no change.
~ Deleted and re-created the CRON script - no change.

I'm baffled because I updated another J2.5.7 site to Akeeba 3.6.8 - same hosting service - and it works fine. Any thots are welcome!
Gary

nicholas
Akeeba Staff
Manager
I think that this is a configuration issue with the server where this particular site is hosted on. Based on the error message is seems that it is impossible to establish the database connection. If your host can't help you with that the only alternative you have is using the old, front-end backup, method of automation instead of the akeeba-backup.php and akeeba-altbackup.php scripts.

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!