Support

Akeeba Backup for Joomla!

#12062 MySQLi adapter not available

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 Friday, 25 May 2012 18:00 CDT

Monday, 23 April 2012 08:45 CDT

quillmed
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting ? Yes, searched for MySQLi with no relevant results returned.
Have I searched the tickets before posting? Yes, searched for MySQLi with no relevant results returned.
Have I read the documentation before posting (which pages?)? Yes, searched for MySQLi with no relevant results returned.
Joomla! version: 2.5
Apache version 2.2.17
PHP version 5.2.17
MySQL version 5.0.95-community-log
Architecture x86_64
Operating system linux
Akeeba Backup version: Akeeba Backup Professional 3.4.3 (2012-03-21)

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:
Backup fails because 'Mysqli' adapter is not available. I am using the MySQLi database type in the general Joomla 2.5 configuration settings (I have to as otherwise another component I use will not work).

Here is the log file from the chron job:

Site paths determined by this script:
JPATH_BASE : /home/public_html/administrator
JPATH_COMPONENT_ADMINISTRATOR : /home/public_html/administrator/components/com_akeeba

Database connection error (1): The MySQL adapter 'mysqli' is not available.

Monday, 23 April 2012 12:22 CDT

nicholas
The CLI and the web versions of PHP use different php.ini configuration files and different binaries. It seems that the command line (CLI) version of PHP does not support the mysqli adapter, unlike the web version. The only two workarounds are:
1. ask your host to recompile the CLI PHP binary with mysqli support; or
2. use altbackup.php instead of backup.php in your CRON job

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, 23 April 2012 21:05 CDT

quillmed
Thank you for the reply Nicholas. I will try the altbackup.php approach and let you know if that works.

Tuesday, 24 April 2012 18:34 CDT

quillmed
Recompiling the cli PHP binary worked. I tried using altbackup.php first but it made no difference. For your info: I am running a server which uses Litespeed instead of apache and so, from what I understand, that's why the cli PHP binary is different and why this is therefore not a common problem, but I might have misunderstood something there.
Thanks for all your help! Ticket closed.

Wednesday, 25 April 2012 03:04 CDT

nicholas
The actual server being used is not really relevant. PHP ships in four forms: an Apache module (mod_php), a CGI binary, a FastCGI binary and a CLI binary. A web server will use one of the first three, depending on the configuration. I bet that Litespeed is using the CGI or FastCGI binary. The CLI binary will always be different than whatever is used by your web server. If not anything else, the CLI binary has one major difference to all other binaries: the execution time limit is always infinite. This allows an entire backup to run without crashing due to timeout errors.

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!

Friday, 25 May 2012 18:00 CDT

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!