Akeeba Solo

#25008 Akeeba Backup for Wordpress - unable to make a cron backup

Posted in ‘Akeeba Solo (standalone)’

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

PHP version

n/a

Akeeba Solo version

n/a

Latest post by hannesausmwald on Monday, 25 April 2016 12:21 CDT

Monday, 25 April 2016 03:07 CDT

hannesausmwald

Hi,

I have installed Akeeba Backup for Wordpress core version to test it before subscription (still a subscriber of the Joomla version).
Backend Backup works well, but I cannot get the cron based backup running (wp-content/plugins/akeebabackupwp-core/app/cli/backup.php).

The following error occured

Array
(
[0] => Akeeba Solo CLI 1.7.1 (2016-03-20)
[1] => Copyright (C) 2010-2016 Nicholas K. Dionysopoulos / Akeeba Ltd
[2] => -------------------------------------------------------------------------------
[3] => Akeeba Solo is Free Software, distributed under the terms of the GNU General
[4] => Public License version 3 or, at your option, any later version.
[5] => This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the
[6] => license. See http://www.gnu.org/licenses/gpl-3.0.html for details.
[7] => -------------------------------------------------------------------------------
[8] => You are using PHP 5.6.19-nmm1 (cli)
[9] =>
[10] => Starting a new backup with the following parameters:
[11] => Profile ID 1
[12] => Description "Command-line backup"
[13] =>
[14] => Current memory usage: 2.81 Mb
[15] =>
[16] => Unsetting time limit restrictions.
[17] =>
[18] => Site paths determined by this script:
[19] => APATH_BASE : /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app
[20] => PHP Fatal error: Uncaught exception 'RuntimeException' with message 'Could not connect to MySQL' in /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Driver/Mysqli.php:288
[21] => Stack trace:
[22] => #0 /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Driver/Base.php(1035): Akeeba\Engine\Driver\Mysqli->query()
[23] => #1 /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Driver/Base.php(728): Akeeba\Engine\Driver\Base->execute()
[24] => #2 /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Platform/Base.php(583): Akeeba\Engine\Driver\Base->loadAssocList()
[25] => #3 /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Platform.php(272): Akeeba\Engine\Platform\Base->get_running_backups(NULL)
[26] => #4 /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Factory.php(393): Akeeba\Engine\Platform->__call('get_running_bac...', Array)
[27] => #5 /www/htdocs/w00975af/wordpress/wp- in /www/htdocs/w00975af/wordpress/wp-content/plugins/akeebabackupwp-core/app/Solo/engine/Driver/Mysqli.php on line 288
)

Debug log is attached

Monday, 25 April 2016 05:55 CDT

nicholas

Please check your wp-config.php file. The lines beginning with "define" must NOT be followed by comments as this can confuse the configuration parser.

Moreover, the wp-config.php file must exist in your site's root and contain the database connection information. If you have put a require / include line to include the real file from another location it will not work. Likewise, the define lines must contain the real database connection information, not references to any variables.

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!

Monday, 25 April 2016 12:21 CDT

hannesausmwald

Dear Nicholas,

thank you, that does the trick! Command line Backup is running now. I deleted the comment after the "define" lines as you explained.

Greetings
Steffen

Support