Fatal error: Maximum execution time of 30 seconds exceeded
Permalink
I've been trying to backup the mySQL tables in Concrete5 via the C5 control panel, which I've had no issue in doing in the past (No primary files have changed in the interim period), but now I get a very slow connection and the timeout message below.
My site is hosted by Bluehost and I only have FTP access to the Concrete5 directory on the server, not the entire account (long story, its a shared account, but that's what I have to live with).
These are the messages I get:
Fatal error: Maximum execution time of 30 seconds exceeded in /accountname/public_html/webdirectory/updates/concrete5.6.1.2_updater/concrete/core/libraries/backup.php on line 124
Fatal error: Maximum execution time of 30 seconds exceeded in /accountname/public_html/webdirectory/updates/concrete5.6.1.2_updater/concrete/libraries/3rdparty/adodb/drivers/adodb-mysql.inc.php on line 736
I've looked for a solution but haven't found one for my situation and limited means of access.
My site is hosted by Bluehost and I only have FTP access to the Concrete5 directory on the server, not the entire account (long story, its a shared account, but that's what I have to live with).
These are the messages I get:
Fatal error: Maximum execution time of 30 seconds exceeded in /accountname/public_html/webdirectory/updates/concrete5.6.1.2_updater/concrete/core/libraries/backup.php on line 124
Fatal error: Maximum execution time of 30 seconds exceeded in /accountname/public_html/webdirectory/updates/concrete5.6.1.2_updater/concrete/libraries/3rdparty/adodb/drivers/adodb-mysql.inc.php on line 736
I've looked for a solution but haven't found one for my situation and limited means of access.
https://www.concrete5.org/marketplace/addons/backup-voodoo/
Thanks. I'll certainly be calling Bluehost but this backup add-on might do the trick, as I've been interested in finding something like this for a while.
to be honest I would never want to rely just on C5's basic built-in backup - it's too brittle in my opinion. Ideally you should get access to the db via phpmyadmin but failing that backup voodoo looks like a well thought-out option.
It sounds like your database has either grown to a size too large to be processed in the time allowed or your server resources are maybe thinner then they once were. The built-in backup in C5 is not particularly efficient - for version 5.6 and older there is a backup add-on from John the Fish that might help.
You 'might' have more luck running the backup at different times (server less busy), or you could possibly make the backup smaller by clearing up old page versions via jobs if there are hundreds of them, clearing down the c5 logs - this might make no difference but I've seen one site in the past that had over half a million entries in the logs.