Support

Akeeba Backup for Joomla!

#8567 Cron FTP problem

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 nicholas on Saturday, 21 August 2010 00:34 CDT

kkevents
I am using the latest SVN developers release of Pro. I set up a Corn job on multiple sites. The backup completes fine from what I can tell. But upon FTP transport it times out and only FTP uploads a only 10%-50% of the file. The email from Akeeba says the backup completed, but does not address the FTP error. If I do a back end backup the FTP uploads as it should and is fine. I am using backup.php. Should I be using the altbackup.php?

On a second note.... I am using a Synology DS210+ for my FTP backup storage, Is there any way to have something like the windows remote backup run on the Synology server, it is the one thing that is always running. ##text##

nicholas
Akeeba Staff
Manager
If this is the debug log from backup.php, it is not running a backup at all! Can you please check that you really have the very latest SVN release? I uploaded a new version 1-2 days ago, I want to make sure we're on the same page.

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!

kkevents
hmmmm...I must have loaded an old one by mistake. I was on SVN192, I have loaded the new one SVN217 and will retry the cron job. Thanks for the secure format. I will test that too and get back to you. Also for testing how often should I start the cron? My backup takes about 8-10 minuets. If I start one every 5 min. will that cause an issue for the one in progress?

kkevents
OK Here is the new log with SVN217##text## It fails every time now

edit: the altbackup.php also does not work. Here is the cron E-mail
Akeeba Backup Alternate CRON Helper Script version svn217 (2010-08-15) Copyright (C) 2010 Nicholas K. Dionysopoulos
-------------------------------------------------------------------------------
Akeeba Backup is Free Software, distributed under the terms of the GNU General Public License version 3 or, at your option, any later version.
This program comes with ABSOLUTELY NO WARRANTY as per sections 15 & 16 of the license. See http://www.gnu.org/licenses/gpl-3.0.html for details.
-------------------------------------------------------------------------------

Starting a new backup with the following parameters:
Profile ID : 1
Backup Method : curl

[2010-08-17 18:30:02] Beginning backing up Fatal error: Maximum execution time of 30 seconds exceeded in /home7/filmposi/public_html/administrator/components/com_akeeba/altbackup.php on line 135

nicholas
Akeeba Staff
Manager
OK, you have a timeout error. You are accidentally using your host's PHP CGI (Common Gateway Interface) binary which is meant to be normally used by Apache and has a timeout limit of 30 seconds. You must ask your host for the full path to the PHP CLI (Command Line Interface) binary and use that in your CRON job. Normally your host should be able to help you with that, but you will most probably have to escalate your support request until you talk with a "real" system administrator (the first line of most hosts' support is script-reading drones without a single technical bone in them).

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!

kkevents
I tried what the host suggested and it says pending in Akeeba and still fails ##text## It seems like it does not finish now....I will try one thing in my php.ini settings to see if that will work.

kkevents
Here is the latest log using the full path for the cron . One completed as ok in the back end and only FTP a small portion of the file. The current one has been pending for a least an hour. ##text## here are my cron setting for blue host: /ramdisk/bin/php5-cli /home7/filmposi/public_html/administrator/components/com_akeeba/backup.php

nicholas
Akeeba Staff
Manager
It looks like the file VBA.zip on your site's root is throwing off the backup process. If you exclude this file from the backup set, does the backup work? Does the backup from the back-end with SVN217 work with or without excluding VBA.zip?

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!

kkevents
It looks like the JPS archive format might be the problem. I tried a few times with it in the back end and it never finished. Looks like it was just looping. I switched it back to JPA and it finished in the back end and cron command-line. However when I went to view the log file for the command line I see "Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 47402144 bytes) in /home7/filmposi/public_html/libraries/joomla/error/error.php on line 76"
Not sure if that is normal or not....the back end log is fine. Attached is the command line log. It also seemed to FTP correctly too.The backup sizes are equal on my FTP server and the main server.##text## I will keep trying the JPS to see if I can fond anything else

kkevents
After testing again it is the JPS format that hangs up. /home7/filmposi/public_html/components/com_virtuemart/themes/eny-lovely-store/images/administration/dashboard is where is looping##text## here is the latest log

nicholas
Akeeba Staff
Manager
The error you got when you were trying to display the log is expected if the log is too big. Parsing it and colourizing it is a very resource intensive process. That's why we have the download link. The raw file always tells the truth and as per your description I understand that the backup process itself completed successfully.

Now, about the JPS archiver, I will do more thorough testing today trying to replicate the results you got and fix any bugs before releasing 3.1.b1 (most probably the release will be on Sunday, if all goes well).

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 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!