Akeeba Backup for Joomla!

Monday, 15 September 2014 08:11 CDT

scou7564

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've attached the log files from running a backup using command line (cron) and the log from running the backup using the backend. Both of the backups use the same profile, which I've attached the *.json into the zip. I've also attached the screenshots of ALICE from both the command line and backend logs.

I mostly run the Akeeba backups from command line and lately I've been getting the following error:

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

Peak memory usage: 8.91 Mb

Any assistance is greatly appreciated.

Monday, 15 September 2014 08:49 CDT

dlb

This is a known issue is 4.0.0/4.0.1 but should be fixed in 4.0.2. Please double check your Akeeba Backup version. 4.0.2 was released on Saturday.

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)

Monday, 15 September 2014 08:59 CDT

scou7564

Thanks for the reply

I have another website that uses the same hosting specs as the first site and that site has generated the same error as the first site. I had AkeebaBackup 4.0.2 installed on the second site.

I've attached the log files, I'm not sure if I should open a new ticket or keep this ticket going.

Thanks.

Monday, 15 September 2014 09:20 CDT

dlb

Both of the logs in your second post show successful backups.

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)

Monday, 15 September 2014 10:02 CDT

scou7564

Then can you tell me why in my command line backup I got the following error:

Could not rename last JPA part to .JPA extension.

As well, when the backup file was transferred, the file size was twice the size as the original backup file size.

Monday, 15 September 2014 10:39 CDT

dlb

"...you have just crossed over into the Twilight Zone."

How and when was this site upgraded to 4.0.2? You got the rename error last night but not this morning. And even with the error, the file uploaded properly. It might make sense if you used a CRON job and a script to update Backup. But that isn't something that I'd like to bet on.

Which file size is correct?

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)

Monday, 15 September 2014 10:41 CDT

scou7564

This site was updated to 4.0.2 on Friday and cron ran the backup this morning.

Monday, 15 September 2014 14:02 CDT

scou7564

The log file I've attached has the following:

[140914 22:03:48] Could not rename last JPA part to .JPA extension.
[140914 22:03:48] ----- Finished operation 1284 ------
[140914 22:03:48] Failed Smart algorithm on AECoreDomainPack
[140914 22:03:48] Archive is finalized

Monday, 15 September 2014 21:16 CDT

dlb

I suspect that some files are not written to disk.

The safest way to figure this out is as follows:

Disable the System - System Restore Points plugin if it's enabled
Remove the directory administrator/components/com_akeeba/akeeba
Install Akeeba Backup 4.0.2 again, without uninstalling the currently installed version

This will force a refresh of the affected file (it's deleted so Joomla! extensions installer HAS to write it again to disk).

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)

Tuesday, 16 September 2014 07:15 CDT

dlb

There is new news this morning. Nicholas has identified circumstances where the rename problem could still happen under 4.0.2. Please install the reva891924 Dev Release located at https://www.akeebabackup.com/download/developer-releases/akeebapro/reva891924.html.

We would appreciate it if you could let us know if that fixes the problem on your site.

Note that when you have a dev release installed, Joomla! will always tell you there is an update available. It does not look at the dates of the programs involved.

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)

Tuesday, 16 September 2014 09:32 CDT

scou7564

Thank you for the news, I will let you know if this fixes the problem.

Wednesday, 17 September 2014 07:49 CDT

scou7564

Hello

I got the following:

[140916 22:02:32] Could not rename last JPA part to .JPA extension.
[140916 22:02:32] Archive is finalized
[140916 22:02:32] ----- Finished operation 630 ------
[140916 22:02:32] ----- Finished operation 630 ------
[140916 22:02:32] Successful Smart algorithm on AECoreDomainPack
[140916 22:02:32] Failed Smart algorithm on AECoreDomainPack

Wednesday, 17 September 2014 08:00 CDT

dlb

Please check your CRON jobs, it looks like you have two backups running at the same time. Look just above the first red line that you posted, the jpa has already been successfully renamed.

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)

Wednesday, 17 September 2014 08:05 CDT

scou7564

I only have one cron task running.

Wednesday, 17 September 2014 08:31 CDT

dlb

There is something really weird going on. What we're seeing in the log file isn't possible.

Please delete the following files/folders:

cli/akeeba-backup.php
cli/akeeba-altbackup.php
media/com_akeeba
plugins/system/srp
administrator/components/com_akeeba
components/com_akeeba,

then install the dev release again.

Do you have more than one site pointing to the same backup output directory?

Lastly, please delete all of your CRON jobs and create a new one, but this time start the backup five minutes later than what you have in the current CRON job.

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)

Wednesday, 17 September 2014 09:59 CDT

scou7564

Hello

I've deleted the files and folders you listed and re-installed the development version again.

I do not have more than one site pointing to the same backup output directory.

I've also removed all of my cron tasks for this site and created a new cron task to start later than what I originally had.

I will let you know if this fixes the problem.

Thursday, 18 September 2014 16:50 CDT

scou7564

Hello

I got the following:

[140917 23:03:51] Could not rename last JPA part to .JPA extension.
[140917 23:03:51] ----- Finished operation 226 ------
[140917 23:03:51] ----- Finished operation 226 ------
[140917 23:03:51] Successful Smart algorithm on AECoreDomainPack
[140917 23:03:51] Failed Smart algorithm on AECoreDomainPack

Thursday, 18 September 2014 17:03 CDT

dlb

You have something really weird going on. You can see in your log the backup starts on line 6, then another backup starts on line 10. The two of them continue throughout the log file. That is supposed to be impossible.

I'm leaving on vacation in the morning, so I'm going to bow out of this. I'll leave a note for Nicholas and he or Davide will pick it up. You're in good hands.

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, 19 September 2014 00:52 CDT

nicholas

After having read all the conversation and the logs here, I have to first tell you that your issue has nothing to do with the "Can't rename issue" other people have. What you see happens because two backups are running at the exact same time. Since one of them keeps the file open for writing the other one can't rename the file.

Which brings us back to your issue: two backups are running at the same time from inside the same PHP process. I'll put it bluntly: THIS. CAN'T. HAPPEN. We don't fork the process anywhere in our code and we sure as heck are not crazy enough to have two backups run when you only need one, let alone run them with the same backup ID!!! This leaves us with just one possibility: your host's PHP-CLI is broken in a way that I've not seen in 8 years. Unfortunately, all I can tell you is talk to your host and if, despite the mountain of evidence in this thread, deny the issue just switch hosts.

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!

Thursday, 02 October 2014 09:36 CDT

scou7564

Hello

I wanted to write a follow-up note as to what has happened with my problem.

I contacted my web hosting provider and they noticed that something was being done twice. Since this was corrected my cron tasks have been running once.

Thanks for your help.

Thursday, 02 October 2014 10:44 CDT

dlb

You are welcome! I'm glad you got it figured out.

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)

Saturday, 01 November 2014 18:20 CDT

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.

Edited by on 2014-11-01 18:20 CDT

Support