Support

Akeeba Backup for Joomla!

#18126 getting error with cron backup, but not with backend backup

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 Thursday, 21 November 2013 03:30 CST

bstanton
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:
Dear Sirs,
Backups performed manually through the site backend are executing without problem, and I can
restore from the backup file without problem. My cpanel offers cron jobs, and I have setup a cron
process to run the same profile and get strange results. First, I receive 2 rather than 1 email
indicating that the cron ran. 1 email shows an error, the other doesn't. The manual backup is
35mb. The cron backup is 70mb and is not functional (ie I get an error when attempting to
reconstruct the site from it. )
Here are the 2 emails:

Cron <language@s02> /usr/local/bin/php /home/language/public_html/cli/akeeba-backup.php --profile=1
Inbox
x

Cron Daemon <[email protected]>
11:01 PM (10 hours ago)

to me
Akeeba Backup CLI 3.8.2 (2013-09-30)
Copyright (C) 2010-2013 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.
-------------------------------------------------------------------------------
You are using PHP 5.3.20 (cli)

Starting a new backup with the following parameters:
Profile ID 1
Description "Command-line backup"

Current memory usage: 2.15 Mb

Unsetting time limit restrictions.

Site paths determined by this script:
JPATH_BASE : /home/language/public_html
JPATH_ADMINISTRATOR : /home/language/public_html/administrator

Last Tick : 2013-11-15 00:00:05 GMT-0600 (CST)
Domain : init
Step :
Substep :
Memory used : 7.41 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:00:05 GMT-0600 (CST)
Domain : installer
Step :
Substep :
Memory used : 7.49 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:00:27 GMT-0600 (CST)
Domain : PackDB
Step :
Substep :
Memory used : 9.97 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:00:40 GMT-0600 (CST)
Domain : PackDB
Step :
Substep :
Memory used : 9.91 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:00:46 GMT-0600 (CST)
Domain : Packing
Step : /home/language/public_html/components/com_kowhosthere/assets/images/countries
Substep :
Memory used : 10.22 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:01:05 GMT-0600 (CST)
Domain : Packing
Step : -
Substep :
Memory used : 10.22 Mb
Warnings : no warnings issued (good)

An error has occurred:
Could not rename last JPA part to .JPA extension.

Peak memory usage: 12.49 Mb

Cron Daemon <[email protected]>
11:01 PM (10 hours ago)

to me

Memory used : 10.01 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:00:40 GMT-0600 (CST)
Domain : PackDB
Step :
Substep :
Memory used : 9.91 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:00:46 GMT-0600 (CST)
Domain : Packing
Step : /home/language/public_html/components/com_kowhosthere/assets/images/countries
Substep :
Memory used : 10.22 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:01:05 GMT-0600 (CST)
Domain : Packing
Step : -
Substep :
Memory used : 10.22 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:01:05 GMT-0600 (CST)
Domain : finale
Step :
Substep :
Memory used : 10.58 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:01:05 GMT-0600 (CST)
Domain : finale
Step :
Substep :
Memory used : 10.58 Mb
Warnings : no warnings issued (good)

Last Tick : 2013-11-15 00:01:05 GMT-0600 (CST)
Domain : finale
Step :
Substep :
Memory used : 10.58 Mb
Warnings : no warnings issued (good)

Backup job finished successfully after approximately 1 minute


Thanks so much for your kind assistance with this great product that has already been a lifesaver several times,
kind regards,
Brian

nicholas
Akeeba Staff
Manager
According to your log file and the email text you copied the backup has run successfully to the very end. You don't have a backup problem at all.

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!

bstanton
Hi Nick,
Thanks for your attention. There is actually some kind of problem though. When I attempt to restore the site from the backup that is created, I get an error (see attached). In addition, in my email, the log shows that somehow the process is running twice (only one cron though). One run shows no error, the other shows the "Could not rename last JPA part to .JPA extension" error. As things stand I must still perform manual backups, as the automated ones clearly aren't working. Any advice you can offer would be greatly appreciated.

kind regards,
Brian

nicholas
Akeeba Staff
Manager
Have you tried using the akeeba_altbackup.php CRON script?

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!