Support

Akeeba Backup for Joomla!

#35869 What could be causing this message?

Posted in ‘Akeeba Backup for Joomla!’
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

psrch

Please look at the bottom of this page (under Support Policy Summary) for our support policy summary, containing important information regarding our working hours and our support policy. Thank you!


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: When I run the configuration wizard, I get the following message: "Could not determine the minimum execution time. This indicates a severe problem communicating with your server. Please try configuring Akeeba Backup manually."

 

I've checked with my server provider, and they tell me there's no PHP setting for "minimum" execution time (which I know). I'm not sure what setting(s) could be causing this. I can in fact use Akeeba Backup to backup files, but the message about "a severe problem communicating with your server" concerns me.

What should I check?

nicholas
Akeeba Staff
Manager

The real root cause is that your server has a protection against the same IP accessing the same URL or script file repeatedly over a short period of time. Typically, this is implemented with an Apache module. On cPanel hosts that's mod_bwlimited. Some hosts may use different approaches but the effect is the same. Since this information is neither publicly available nor detectable in a way we work around this server protection by ensuring there is a minimum amount of time spent on each request during the backup. This is the minimum execution time.

Detecting the minimum execution time works by making three consecutive requests, each trio of requests made after setting the minimum execution time to different values: 0, 0.5 seconds, 2 seconds etc. If the first trio of requests gets blocked it's possible that the server denies further requests, making the detection fail. That's why it tells you to configure Akeeba Backup manually.

Use the Configuration page in Akeeba Backup to set minimum execution time 2 seconds, maximum execution time 7 seconds and execution time bias 75%. If this doesn't work try setting the minimum execution time to 5 seconds instead. Increasing the minimum execution time makes the backup slower but works around the server protection essentially killing off the backup process prematurely.

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!

psrch

Thanks! The backups were working anyway, so that's good. But it's good to know what's going on, so I can really ignore it as long as it's working.

nicholas
Akeeba Staff
Manager

You're welcome!

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!

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: Typically we work Monday to Friday, 9am to 7pm Cyprus timezone (EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets, but we cannot respond to them, outside of our working hours.

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!

Summer vacations: Our support will be closed for replies and new tickets from August 6th to August 21st, 2022 due to summer vacations.