Akeeba Backup for Joomla!

Thursday, 31 July 2014 02:27 CDT

user77552

Hey guys,

I keep have multiple failed backup attempts from the "Cron job" frontend automatic jobs.

If i manually access the plugin from the Joomla administration i have no problem. I thought it was some SEF/ JoomSEF having messed up a url or similar but cleaned up and fixed that yesterday an am 100% sure that isn't it anymore.

My other site (test site) is running 1 version older than 3.11.3 which has the same cronjob and thats still running flawlessly.

So the error has occurred after i updated to 3.11.3

I've attached the log.

Thursday, 31 July 2014 08:02 CDT

dlb

I think your host is killing the CRON job after 5 minutes. You other site is a little smaller or a little quicker and it is getting done under the time limit.

You need to check with your host to confirm that they are killing the CRON job and ask them to extend the time limit.

Dale L. Brackin
Support Specialist

English: native

Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

????
My time zone is EST (UTC -5) (click here to see my current time in Philadelphia, PA)

Thursday, 31 July 2014 09:44 CDT

user77552

Its on the same host, and honestly its an exact copy from before i upgraded akeeba backup - seems very weird if upgrading that a few other small plugins would result in such a size increase..?

Friday, 01 August 2014 01:29 CDT

nicholas

You just have to read the log.

Problem #1: You are not using PHP CLI as clearly explained in our documentation. You are using PHP FastCGI:
INFO |140731 03:07:17|PHP SAPI :cgi-fcgi

Problem #2: PHP FastCGI has a maximum execution time of 300 seconds (5 minutes)
INFO |140731 03:07:17|Max. exec. time :300

Problem #3: Your backup needs to run longer than that. How do we know? Start of backup:
DEBUG |140731 03:07:17|*** Batching successive steps (nesting level 1)
Last log entry before the backup dies:
DEBUG |140731 03:12:14|Closing SQL dump file.
The elapsed time logged was 297 seconds. Taking into account the time it takes PHP to load and start the application we are at 300 seconds give or take one second. This makes us further suspect that the CRON daemon itself has a CRON job maximum time limit of 5 minutes (300 seconds).

As Dale said, you need to check with your host to confirm that they are killing the CRON job and ask them to extend the time limit.

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!

Support