Support

Akeeba Solo

#26280 Akeeba solo + Remote CLI - Error 101: could not connect to MySQL

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 CasperTofte on Tuesday, 11 October 2016 12:54 CDT

CasperTofte
Hello,
I am having trouble using Akeeba Solo PRO together with Akeeba Remote CLI.
It is possible to create a backup within the administrationpanel of Akeeba Solo, without any problems. However, when I try execute the backup-procedure using Remote CLI, I get the following error:
Error #101: Error 500: A backup error has occurred: Akeeba\Engine\Dump\Base :: Database Error: Could not connect to MySQL

I have tried to make a backup on two distinct hosts, with two different prestashop websites. The error is the same.
Analyzing using Alice provides
“Please try setting min execution time to 1, max execution time to 10 seconds (or if the PHP timeout is less than 10 seconds, use 75% of the PHP timeout), runtime bias 75%”
However, changing the execution time does not have any effect.

I know it might be a different scenario, but running the Remote CLI to perform a backup in Joomla (Akeeba backup for Joomla) on the same hosting environment, works just fine.

Host #1.
PHP Version 7.0.11
Database: 10.0.27-MariaDB

Host #2
PHP Version 7.0.6
Database: mysqlnd 5.0.12-dev – 20150407

Akeeba Solo PRO: 2.0.2
Remote CLI: 1.2

nicholas
Akeeba Staff
Manager
The problem I see in the first log (Meebox) you submitted is that there is no database defined for the main site database:
DEBUG   |161008 15:06:43|Akeeba\Engine\Core\Domain\Db :: Now backing up [SITEDB] ()

Please go to the Configuration page and click on the Configuration Wizard. Make sure the top section (URL and path) are correct, then click the big green button to have Solo automatically find out the database connection information from Prestashop's configuration.

The second log file (Unoeuro) shows an entirely different issue: only the first backup step run. The next backup step was never initiated. Can you please try the attached Remote CLI version instead and let me know if that works for you?

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!

CasperTofte
Hi',

The only thing missing in the Meebox example was the URL (albeit being optional). The path and the login details were correct.
After correcting this, error #101 was still present.

I updated the scripts to use the attached Remote CLI and both websites completed the backup without any problems hereafter.
Just out of curiosity - is this version of Remote CLI being made as a public update? and should I permanently update Remote CLI to this version for any backups run by Remote CLI?

nicholas
Akeeba Staff
Manager
Thank you for the feedback!

I hadn't released Remote CLI yet because nobody had reported any issues. I had spotted an issue in just one of my test sites, making me unsure if it was a bug fix or a fluke. Now that I know that there really is something here I will release the new version of Remote CLI today.

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!

CasperTofte
Glad I could help and thanks alot for the quick solution! :-)

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!