Akeeba Backup for Joomla!

Tuesday, 26 November 2013 11:42 CST

Peter Reitsma

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:

Since 22-11-2013 the command line backup fails. The normal backup manual started does work.

Edited by Peter Reitsma on 2013-11-26 11:51 CST

Tuesday, 26 November 2013 11:53 CST

Peter Reitsma

Tuesday, 26 November 2013 20:27 CST

dlb

Please go to your Akeeba Backup Configuration page and try setting:

Minimum execution time: 1 second
Maximum execution time: 10 seconds
Runtime bias: 75%

If this still fails please try the conservative settings:

Minimum execution time: 5 second
Maximum execution time: 3 seconds (yes, the maximum is less than the minimum, it's not a typo)
Runtime bias: 50%

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)

Friday, 29 November 2013 06:17 CST

Peter Reitsma

Thank you for the reply. I tried both options but still no luck.

I found this in the log:

[131129 08:01:12] Kettenrad :: Attempting to load from database (cli)

[131129 08:01:12] -- Stored Akeeba Factory (cli) not found - hard reset

I 'll upload the log file again.

Friday, 29 November 2013 09:03 CST

dlb

Those two lines aren't really a problem, note that they are four hours after the backup stops.

I will ask Nicholas to look at this.

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)

Friday, 29 November 2013 09:21 CST

nicholas

The backup abruptly stops 3 minutes and 20 seconds into the process (or 200 seconds). Notice the round number? That's because your host is terminating CRON jobs 200 seconds after they were launched. This amount of time is too low for a full site backup. Please ask your host to increase the CRON time limit. Please note that the CORN time limit is something that only your host can control and has nothing to do with the PHP or Apache timeout settings (they are not even remotely related).

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, 29 November 2013 09:29 CST

Peter Reitsma

Thanks for the excellent support!

I will contact the host to solve this.

Support