Support

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: cronjob error: cannot connect to mysql database. Same issue as #25236

After updating AkeebaBackup Pro for Joomla from 4.6.1 to 5.0.3 and later 5.0.4 I get this cronjob error:

You are using Joomla! 3.4.8 on PHP 5.6.21-1byte1 (cli)

Starting a new backup with the following parameters:
Profile ID 1
Description "Command-line backup"

Current memory usage: 1.56 Mb

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /home/users/facjkftp/mysite.nl
JPATH_ADMINISTRATOR : /home/users/facjkftp/mysite.nl/administrator



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

Could not connect to MySQL

Technical information:

Code: 2
File: /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Driver/Mysqli.php
Line: 288

Stack Trace:

#0 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Driver/Base.php(1049): Akeeba\Engine\Driver\Mysqli->query()
#1 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Driver/Base.php(742): Akeeba\Engine\Driver\Base->execute()
#2 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupPlatform/Joomla3x/Driver/Joomla.php(126): Akeeba\Engine\Driver\Base->loadAssocList()
#3 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Platform/Base.php(583): Akeeba\Engine\Driver\Joomla->__call('loadAssocList', Array)
#4 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Platform/Base.php(583): Akeeba\Engine\Driver\Joomla->loadAssocList()
#5 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Platform.php(272): Akeeba\Engine\Platform\Base->get_running_backups(NULL)
#6 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Factory.php(436): Akeeba\Engine\Platform->__call('get_running_bac...', Array)
#7 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/BackupEngine/Factory.php(436): Akeeba\Engine\Platform->get_running_backups(NULL)
#8 /home/users/facjkftp/mysite.nl/administrator/components/com_akeeba/Model/Backup.php(122): Akeeba\Engine\Factory::resetState(Array)
#9 /home/users/facjkftp/mysite.nl/cli/akeeba-backup.php(236): Akeeba\Backup\Admin\Model\Backup->startBackup(Array)
#10 /home/users/facjkftp/mysite.nl/cli/akeeba-backup.php(324): AkeebaBackupCLI->execute()
#11 {main}

An other Joomla site with the same configuration (in another cluster) but still on Akeeba 4.6.1 is running properly at the same hosting company, so the problem started after updating.

I did not touch my configuration.php at all.

Attached: 2 screendumps from Alice. And an Alice log file, which is more or less empty. Password for both zips is akeeba

Hold your horses. I just found out that 108 backup files were not uploaded to my ftp server. So my serverspace might be full. I moved the files from my hosting account. Within an hour or so a new cronjob will run and then I will know if this was the issue. I will let you know.

Ok, thank you. Moving the backups from the hosting server were not the solution I just found out.

is there a solution for this yet?

Stable version 5.1.0 works fine. Ticket can be closed.