Support

Akeeba Backup for Joomla!

#22175 Bug in the 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 on Saturday, 04 April 2015 17:20 CDT

CDSS100
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:

After installing Akeeba Pro I backup fails with the following error.

AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
(HTML containing script tags)

dlb
Your backup is stopping in on particular spot, it tries to restart several times, but always quits at the same point.

Please go to your Akeeba Backup Configuration page and try setting:

Minimum execution time: 1 second
Maximum execution time: 10 seconds
Runtime bias: 75%

If this still fails please try the conservative settings:

Minimum execution time: 5 second
Maximum execution time: 3 seconds (yes, the maximum is less than the minimum, it's not a typo)
Runtime bias: 50%


Dale L. Brackin
Support Specialist


us.gifEnglish: 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)

CDSS100
Thank you for your response. I have tried both configurations but still get the same error: AJAX Loading Error
HTTP Status: 500 (Internal Server Error)
Internal status: error
XHR ReadyState: 4
Raw server response:
(HTML containing script tags)

ALICE also suggests that disk space might be a problem but I have checked and that doesn't seem to be the case.

Host is LiquidWeb if that helps.

Thanks

dlb
At some point, you need to run the Configuration Wizard to reset your timing numbers back to where they were. What those changes we made do is slow down the backup. That didn't fix the problem, so we don't want it to be slow any more.

Next we want to set a small part size, that will split your backup into multiple parts. Sometimes the size warning means an individual file is too large, not a lack of total disk space. You set the part size through the Configure button on the Archiver Engine line of the Configuration screen. Set it to something small, like 10 mb. If the backup is successful, we'll have to experiment with that size to figure out what the maximum is.

The last thing to try is to repair and optimize the #__mijoshop_address table (where #_ is your table prefix). You would do that through your host panel, usually through phpMySQL or a similar database utility. That is the table where the backup is stopping.


Dale L. Brackin
Support Specialist


us.gifEnglish: 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)

CDSS100
Thanks for your help. I had set the part size down as far as 2MB without solving the problem.

I have run the configuration wizard so we are back to that baseline.

I tried repairing the offending database table but I kept getting the message that repair was not available. I have asked the folks at LiquidWeb to check into it for me and I will let you know what we find out.

If you have any other suggestions, let me know.

Again, thanks for your patience.

dlb
Asking your host was the correct next step. It appears to be record number 6003 or slightly after where the problem occurs.


Dale L. Brackin
Support Specialist


us.gifEnglish: 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)

CDSS100
This is what the guy from Liquid Web said. (apologize for saying the site was hosted with GoDaddy, it's Liquid Web)
Hello,

I have taken this ticket as the previous technician is unavailable. I ran a test backup and it appears that the issue may be with your mysql grants or the backup script itself.

>[Wed Mar 04 15:21:46.631215 2015] [core:error] [pid 517:tid 139780616550144] [client 10.20.4.175:39752] Invalid status line from script 'index.php': 1142 SELECT command denied to , referer: http://store.cdss.org/administrator/index.php?option=com_akeeba&view=backup

This error indicates that the user does not have SELECT privileges on the database however the cdss_store user does have all privileges on the database as you can see below.

>mysql> show grants for cdss_store@localhost;
+-------------------------------------------------------------------------------------------------------------------+
| Grants for cdss_store@localhost |
+-------------------------------------------------------------------------------------------------------------------+
| GRANT USAGE ON *.* TO 'cdss_store'@'localhost' IDENTIFIED BY PASSWORD '*8F31FF7F4BEA0C3E7F9CFD719234EBA5DF8E9760' |
| GRANT ALL PRIVILEGES ON `cdss\_store`.* TO 'cdss_store'@'localhost' |
+-------------------------------------------------------------------------------------------------------------------+
2 rows in set (0.00 sec)

You may need to contact the Akeeba developers to see if there is a way to fix this.

nicholas
Akeeba Staff
Manager
Having us provide a fix would be quite a feat, considering that all our software does is send a SELECT statement through Joomla!'s database class which uses the standard mysql or mysqli PHP extension which talks to the MySQL connector installed by your host on their own server. How exactly do they expect us to fix their server?! That's a typically incompetent and useless reply from GoDaddy. As you may have guessed it's the umpteenth time they have replied something moronic to one of our clients because they don't know how they've set up their own, consistently crappy servers. My long term fix suggestion is moving to a decent host where its staff knows what they are doing, for example Rochen or SiteGround.

As for a short term solution, the most likely problem is the one described in http://stackoverflow.com/questions/14423686/error-1142-select-and-lock-table-commands-denied which describes a server issue. Another possibility is that they apply a limit of SQL commands in a specific amount of time which would explain why MySQL denies connecting all of a sudden. Again, this is a server setup issue which can be easily overcome – at least long enough to get your data out of GoDaddy and move to a decent host.

Please forward my reply to GoDaddy. Also, maybe it's time to take advantage of the 3 months free hosting offer from SiteGround?

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!

CDSS100
Nicholas,

I have to say I am in total agreement. I appreciate very much the trouble you have taken to assist with this issue. I have been using Akeeba a long time and it has never failed me. I don't think Akeeba is the problem in this case.

I also apologize for one error on our part and that is I was led to believe that GoDaddy was our host but it's actually Liquid Web. Sorry for the misunderstanding. Regardless, I still think it is either a server issue or one other possibility we are considering. We took over management of this site from the previous vendor and we are now wondering if they altered MijoShop or anything else to create this problem and will be investigating that possibility.

Please accept my sincerest thanks for you help with this issue and I would consider it resolved from your perspective.

All the best.

nicholas
Akeeba Staff
Manager
Please forward the second paragraph of my previous reply to your host. I am pretty sure the MySQL configuration is amiss on that server. I agree with them that your db user does have SELECT privileges on the table (we've already read about 6000 records before the error occurs). That's why when Dale told me about this ticket I was pretty sure that the problem lies either with a corrupt table or with the server configuration. At the very least they should run a few repair & optimise commands against the offending table and see what MySQL has to say about its status...

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