Support

Akeeba Backup for Joomla!

#25581 error - could not connect to MySQL when running cron job

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 on Thursday, 11 August 2016 17:20 CDT

karendunne
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.

I was unable to locate a log file, presumably because the backup could not complete. The only information I have is via an email from the cron job. See below:

Description of my issue:
Backup via a cron job does not work. The following message is sent from the Cron Daemon after a scheduled cron job:

Akeeba Backup Alternate CRON Helper Script version 5.0.4 (2016-05-23)
Copyright (c) 2006-2016 Akeeba Ltd / Nicholas K. Dionysopoulos
-------------------------------------------------------------------------------
Akeeba Backup is Free Software, distributed under the terms of the GNU General
Public License version 3 or, at your option, any later version.
This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the
license. See http://www.gnu.org/licenses/gpl-3.0.html for details.
-------------------------------------------------------------------------------
Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /home/rtaarchitects/public_html
JPATH_ADMINISTRATOR : /home/rtaarchitects/public_html/administrator

********** ERROR! **********

Could not connect to MySQL.

Technical information:

Code: 0
File: /home/rtaarchitects/public_html/libraries/joomla/database/driver/mysqli.php
Line: 169

Stack Trace:

#0 /home/rtaarchitects/public_html/libraries/joomla/database/driver/mysqli.php(227): JDatabaseDriverMysqli->connect()
#1 /home/rtaarchitects/public_html/libraries/joomla/database/driver.php(1488): JDatabaseDriverMysqli->escape('component')
#2 /home/rtaarchitects/public_html/libraries/joomla/database/driver.php(407): JDatabaseDriver->quote('component', true)
#3 /home/rtaarchitects/public_html/libraries/fof30/Params/Params.php(54): JDatabaseDriver->__call('q', Array)
#4 /home/rtaarchitects/public_html/libraries/fof30/Params/Params.php(54): JDatabaseDriverMysqli->q('component')
#5 /home/rtaarchitects/public_html/libraries/fof30/Params/Params.php(41): FOF30\Params\Params->reload()
#6 /home/rtaarchitects/public_html/libraries/fof30/Container/Container.php(483): FOF30\Params\Params->__construct(Object(FOF30\Container\Container))
#7 /home/rtaarchitects/public_html/libraries/fof30/Pimple/Container.php(112): FOF30\Container\Container->FOF30\Container\{closure}(Object(FOF30\Container\Container))
#8 /home/rtaarchitects/public_html/libraries/fof30/Container/ContainerBase.php(27): FOF30\Pimple\Container->offsetGet('params')
#9 /home/rtaarchitects/public_html/administrator/components/com_akeeba/BackupPlatform/Joomla3x/Platform.php(706): FOF30\Container\ContainerBase->__get('params')
#10 /home/rtaarchitects/public_html/administrator/components/com_akeeba/BackupEngine/Platform.php(275): Akeeba\Engine\Platform\Joomla3x->get_platform_configuration_option('siteurl', '')
#11 /home/rtaarchitects/public_html/cli/akeeba-altbackup.php(140): Akeeba\Engine\Platform->__call('get_platform_co...', Array)
#12 /home/rtaarchitects/public_html/cli/akeeba-altbackup.php(140): Akeeba\Engine\Platform->get_platform_configuration_option('siteurl', '')
#13 /home/rtaarchitects/public_html/cli/akeeba-altbackup.php(503): AkeebaBackupCLI->execute()
#14 {main}

The cron job command is this:
/usr/local/bin/php /home/rtaarchitects/public_html/cli/akeeba-altbackup.php

Other information that may be helpful:
  • Cron jobs on the same host are working.

  • Running a backup manually from Joomla admin works properly.

  • I realize that this site is not on the latest version of Joomla. It has not be upgraded to 3.5.1 intentionally because of a bug that broke front-end editing, which is used all the time on the site (https://issues.joomla.org/tracker/joomla-cms/9615)

dlb
The 5.2.x series was not one of our best. I think that is a known issue with 5.0 but the versions are no longer available for me to check. If you can run 5.0, you should be able to upgrade to the current 5.1.2 where this bug has been fixed.


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)

karendunne
ok, thank you Dale. I will give that a try.

dlb
My apologies, I made an error in the comment above. It should say:
The 5.0.x series was not one of our best.
There is no 5.2 version yet.


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)

System Task
system
This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.

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!