Support

Akeeba Backup for Joomla!

#16802 Backup timeut

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

Latest post by argiropn on Wednesday, 14 August 2013 01:52 CDT

argiropn
Mandatory information about my setup:

Have I read the related troubleshooter articles above before posting (which pages?)? Yes
Have I searched the tickets before posting? Yes
Have I read the documentation before posting (which pages?)? Yes
Joomla! version: 2.5.11
PHP version: 5.4.16
MySQL version: 5.5.27
Host: (optional, but it helps us help you)
Akeeba Backup version: Akeeba Backup Core 3.7.7 (2013-05-11)

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:
I already tried several value combinations in Minumum/Maximum execution time, execution time bias and in number of rows per batch (Database backup engine) parameters. Unfortunately I didn't kept record of all these combinations. I just remember the last ones:
Min,Max,bias,rows
1,2,25,500
1,2,25,300

I tried also several time the configuration wizard without real success. I mean that some time the backup workds and then starts failing again.

Thanks in advance

nicholas
Akeeba Staff
Manager
Please upgrade to Akeeba Backup 3.7.10 and retry backing up your site. If the error persists, please send me the new log file.

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!

argiropn
My site has been upgraded to Akeeba BackUp 3.7.10, and still the problem exists. I am sending you the new log file.

nicholas
Akeeba Staff
Manager
OK, we're getting somewhere. Go to the Akeeba Backup Configuration page and scroll all the way down. Use these:
Minimum execution time: 0.5 seconds
Maximum execution time: 14 seconds
Runtime bias: 75%

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!

argiropn
i got again the same error. sending you the new log file

nicholas
Akeeba Staff
Manager
There seems to be a plugin on your site which is slowing down every request be several minutes. This is the source of the timeout. Since this is something external to Akeeba Backup I cannot help you in any way except tell you what I'd do if I were in your shoes: try to disable system plugins one by one until I find which one is causing the slow down of the site which leads to backup failure.

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!

argiropn
Dear Nicholas,

I tried your recommendation but unfortunately it made no difference. I also investigate more the problem and I still believe that is related with the akeeba backup engine in combination with server configuration. So let me give you some information about the server environment and the last symptom hopping that you might come back with some positive ideas if not with a solution:

1) The operational platform is Windows Srv 2008 R2 Std SP2
2) For activating the frontend backup is used the wget tool of GnuWin32 (GNU Wget 1.11.4)
3) The actual command looks as follows
D:\GnuWin32\bin\wget --max-redirect=10000 --append-οutput=d:\Backup\Backup_wget.log "http://www.mydomain.com/index.php?option=com_akeeba&view=backup&key=myfekey"
4) The backup script is implemented as vbs and is executed via windows task scheduler under the context of a separate user that is member of the local administrators group
5) In the backup script are executed two wget commands for two different sites. The first always succeeds when the second sometimes fails with the following symptoms:

The attached file is the backup log file and the output file of the corresponding wget is the following:
--2013-08-06 14:25:43-- http://www.mydomain.com/index.php?option=com_akeeba&view=backup&key=myfekey
Resolving www.mydomain.com... 192.168.0.26
Connecting to www.mydomain.com|192.168.0.26|:80... connected.
HTTP request sent, awaiting response... 303 See other
Location: http://www.mydomain.com/index.php?option=com_akeeba&view=backup&task=step&key=myfekey&profile=1 [following]
--2013-08-06 14:25:45-- http://www.mydomain.com/index.php?option=com_akeeba&view=backup&task=step&key=myfekey&profile=1
Reusing existing connection to www.mydomain.com:80.
HTTP request sent, awaiting response... 500 Internal Server Error
2013-08-06 14:26:17 ERROR 500: Internal Server Error.

As you can see there is no any serious delay between the last response and the error 500, just 32 secs.

Regards


nicholas
Akeeba Staff
Manager
As you can see there is no any serious delay between the last response and the error 500, just 32 secs.


And that, sir, cracks the case. 32 seconds is longer than PHP's max_execution_time on your site (30 seconds). So you have a timeout error. You can try these settings in Akeeba Backup:
- Minimum execution time: 1 second
- Maximum execution time: 14 seconds
- Runtime bias: 75%

If this doesn't help it may be because of the performance of the database server or the complexity of the database structure. In this case it's much easier to set max_execution_time=60 or 90 in your php.ini and restart the web server service.

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!

argiropn
Dear Nicolas,

Indeed the problem was the PHP max_execution_time limit. I changed to 60 secs and so far the backup procedure looks just fine. Hopping that it will continue like this I am closing this ticket.

Thank you very much for your valuable help in solving the issue.

Best regards

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

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!