Akeeba Backup for Joomla!

Friday, 23 May 2025 05:37 CDT

Monrim

Hi!

When I'm using Synologys scheduler to run:

php82 /volume1/web/testsite/cli/joomla.php akeeba:backup:take

(attaching the response in a txt file.

it fails du to mysqli object is not fully initialized error. BUT if I do a manual backup it works!! Then I get a successful backup that I can also restore from.

The only change Ive made to settings is to allow for a larger file so I don't get the j01 and so on files.

I've tried to install the backup program in joomla twice in a row and no success what so ever.

This is on a testsite for local purpouses. ATM no external access, just with a VPN connection.

This basically says that PHP can no longer connect to your database server. This is very likely a configuration issue with MySQL. You need to increase the connect_timeout in your MySQL configuration. You may also need to increase the max_connections value as well, in case your database server is too slow closing the connections which requested to be shut down.

For personal experience with Synology NAS devices, they have a slow CPU, very little RAM, and default package (MySQL, PHP, Apache / NginX) configuration to match those restrictions. You will not get a good experience out of it. You will get a lot of timeouts and errors, even when doing simple things like loading the Joomla admin backend. I tried using that as a test server for all of a day before I got frustrated with the endless problems. I've since moved to a self-configured server based on the RK3588 ARM chip with 16GB or RAM and NVMe drives. The Synology NAS is now just a backup storage device.

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!

Thursday, 29 May 2025 15:25 CDT

Monrim

Thank you so much Nicholas!

You solved my problem. I'll just write down what I did for others to see if someone else runs in to this specific problem.

I used SSH to connect to my server. Then I changed directory to MariaDB10 configuration folder with

cd /var/packages/MariaDB10/etc

witch is where Synology at least has the configuration files. Then I did:

sudo -i

I did not have a my.cnf file to start with, but I used vi:

vi my.cnf

In the editor I added:

[mysqld]
max_allowed_packet = 4294967296
max_connections = 500
innodb_buffer_pool_size=4294967296
wait_timeout = 200
interactive_timeout = 200
connect_timeout = 40

Then I saved it and restarted MariaDB10 with the command:

/usr/syno/bin/synopkg restart MariaDB10

Support